Institutional context |
|
Institution type (eg. Library, Archive) |
Library & archive |
Storage and access |
|
Where are collection masters stored (media, number of copies, backup, preservation system)? |
Temporary/working storage: networked Satabeast RAID storage with automated tape backup Final storage: All nodes of the Library's Digital Library System |
Where is access to the collection provided from? |
Access to master files on temporary/working storage is restricted to staff logins via Library workstations Access to low resolution access copies to the public will be delivered online via British Library Sounds |
What technical protocol is used to access files? Local file systems? Windows shares? (SMB/CIFS) |
Master files: Windows shares Access files: http |
Workflow |
|
Describe your existing content workflow. |
|
What tools are part of the existing workflow |
|
What technologies underly the existing workflow? |
Java |
What challenges are present in the existing workflow? (technology, organisational, staffing) |
Time and complexity |
Does the workflow include manual steps? |
Yes |
Where in this content workflow would the prototype solution be deployed? | To replace steps 5-10 |
What is the process for changing or enhancing the workflow? What obstacles to change are present? |
Written workflow documents and diagrams will require re-writing to incorporate improvements. Python to be installed. xslt to be defined for transforming outputs. No other changes should be necessary. |
Actors |
|
Who executes the existing workflow? |
Production Co-ordinator, Sound & Vision Technical Services |
Who adminsters the existing workflow? |
Production Co-ordinator, Sound & Vision Technical Services |
What system rights do the workflow executors have? Can they install software? Can they use the web? |
Full admin rights |
Who is the collection owner or curator? (section/department/team) |
British Library Sound & Vision, Unlocking & Integration AV Content |
Is there a workflow champion, who is it? |
Adam Tovell |
Labels:
None