Archived copy.
This page was recovered from the Internet Archive snapshot of
/pages/viewpage.action?pageId=8356655 taken on 2016-03-31.
The original wiki at wiki.opf-labs.org is being decommissioned.
Workflow "web based email"
| Storage and access |
|
| Collection storage / preservation of masters | Given that the issue is about collecting web based emails we haven't received the material yet. |
| Collection access | |
| Access protocol | |
| Workflow |
|
| Workflow overview | As we haven’t received the material yet, this is a description of the general workshop setup. The current workflow is driven by a locally developed Java program. The workflow, among other things, move files, generates identifier (UUID), identify file types, and register the material in the repository system. |
| Tools used in workflow | Canto Cumulus , eRez |
| Workflow technologies | Java SE, Spring |
| Workflow challenges | The main challenges in the execution of the workflow are the stability of the individual component. |
| Automation | The process is fully automated and manually processes are only used in case of errors. |
| Location of Solution in workflow | In the beginning of the workflow were the material is collected. |
| Workflow change process | A change to the workflow requires an editing of a Spring XML file which in practice is done by a developer. |
| Actors |
|
| Workflow execution actor | The execution is automatically started by the arrival of new material, when it is placed in a special folder. |
| Workflow administration actor | The IT department. |
| Workflow executor rights | Admin rights. |
| Collection owner/curator | The manuscript department. |
| Workflow champions | Claus Jensen, The Royal Library. |
| Dataset/Issue/Solution links |
