| *Institutional context* \\ | |
| Institution type (eg. Library, Archive) \\ | Commercial |
| *Storage and access* \\ | |
| Where are collection masters stored (media, number of copies, backup, preservation system)? \\ | \\ |
| Where is access to the collection provided from? \\ | Commercial web site |
| What technical protocol is used to access files? Local file systems? Windows shares? (SMB/CIFS) \\ | Commercial web site |
| *Workflow* \\ | |
| Describe your existing content workflow. \\ | Images scanned at the newspaper archive in Colindale. \\
Images transferred to Dundee, and imported into DocWorks. \\
Issues zoned and OCRed in DocWorks. \\
Export as METS, ALTO, and JP2. \\
In-DocWorks QC steps. \\
Post-DocWorks QC steps. \\
Validation (including JHOVE). \\
Delivery to the British Library. |
| What tools are part of the existing workflow? \\ | DocWorks, JHOVE |
| What technologies underly the existing workflow? \\ | Ruby on Rails, Perl, Unix shell scripts, MySQL |
| What challenges are present in the existing workflow? (technology, organisational, staffing) \\ | Hardware resources. \\
QC operator time. |
| Does the workflow include manual steps? \\ | Yes |
| Where in this content workflow would the prototype solution be deployed? | Post-DocWorks QC |
| What is the process for changing or enhancing the workflow? What obstacles to change are present? \\ | |
| *Actors* \\ | |
| Who executes the existing workflow? \\ | |
| Who adminsters the existing workflow? \\ | |
| What system rights do the workflow executors have? Can they install software? Can they use the web? \\ | |
| Who is the collection owner or curator? (section/department/team) \\ | |
| Is there a workflow champion, who is it? \\ | |
| Institution type (eg. Library, Archive) \\ | Commercial |
| *Storage and access* \\ | |
| Where are collection masters stored (media, number of copies, backup, preservation system)? \\ | \\ |
| Where is access to the collection provided from? \\ | Commercial web site |
| What technical protocol is used to access files? Local file systems? Windows shares? (SMB/CIFS) \\ | Commercial web site |
| *Workflow* \\ | |
| Describe your existing content workflow. \\ | Images scanned at the newspaper archive in Colindale. \\
Images transferred to Dundee, and imported into DocWorks. \\
Issues zoned and OCRed in DocWorks. \\
Export as METS, ALTO, and JP2. \\
In-DocWorks QC steps. \\
Post-DocWorks QC steps. \\
Validation (including JHOVE). \\
Delivery to the British Library. |
| What tools are part of the existing workflow? \\ | DocWorks, JHOVE |
| What technologies underly the existing workflow? \\ | Ruby on Rails, Perl, Unix shell scripts, MySQL |
| What challenges are present in the existing workflow? (technology, organisational, staffing) \\ | Hardware resources. \\
QC operator time. |
| Does the workflow include manual steps? \\ | Yes |
| Where in this content workflow would the prototype solution be deployed? | Post-DocWorks QC |
| What is the process for changing or enhancing the workflow? What obstacles to change are present? \\ | |
| *Actors* \\ | |
| Who executes the existing workflow? \\ | |
| Who adminsters the existing workflow? \\ | |
| What system rights do the workflow executors have? Can they install software? Can they use the web? \\ | |
| Who is the collection owner or curator? (section/department/team) \\ | |
| Is there a workflow champion, who is it? \\ | |