Editing Workflow:Workflow for ingesting digitized books into a digital archive
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | + | [[File:workflow.png|Upload file (Toolbox on left) and add a workflow image here or remove]] | |
| − | + | [[Category:COW Workflows]] | |
| − | | | + | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Workflow Description== | ==Workflow Description== | ||
<div class="toccolours mw-collapsible mw-collapsed" data-expandtext="Show Diagram" data-collapsetext="Hide Diagram" > | <div class="toccolours mw-collapsible mw-collapsed" data-expandtext="Show Diagram" data-collapsetext="Hide Diagram" > | ||
| Line 13: | Line 7: | ||
</div> | </div> | ||
| − | # The data provider provides | + | # The data provider provides his content as an input for the transfer tool (currently in development) |
| − | # The transfer tool creates a zip-container with the content and calculates a checksum of the container | + | # The transfer tool creates a zip-container with the content and calculates a checksum of the container |
| − | # The zip-container and the checksum are bundled (another zip-container or a plain folder) and | + | # The zip-container and the checksum are bundled (another zip-container or a plain folder) and build the SIP |
| − | # The transfer tool moves the SIP to a registered, data provider specific hotfolder, which is connected to the ingest server | + | # The transfer tool moves the SIP to a registered, data provider specific hotfolder, which is connected to the ingest server |
| − | # As soon as the complete SIP has been transfered to the ingest server, a trigger is raised and the ingest workflow starts | + | # As soon as the complete SIP has been transfered to the ingest server, a trigger is raised and the ingest workflow starts |
| − | # The SIP gets unpacked | + | # The SIP gets unpacked |
| − | # The zip container | + | # The included zip container is validated according to the provided checksum. If this fixity check fails, the data provider is asked to reingest his data. |
| − | # The content and the structure of the content are validated against the submission agreement, that was signed with the data provider (this step is currently in development) | + | # The content and the structure of the content are validated against the submission agreement, that was signed with the data provider (this step is currently in development) |
| − | # Based on | + | # Based on the OPAC-systemnumber (encoded in the content filename) descriptive metadata is fetched from the library's OPAC over its OAI-PMH interface |
# The OPAC returns a MARC.XML-file. | # The OPAC returns a MARC.XML-file. | ||
| − | # The MARC.XML-file is mapped | + | # The MARC.XML-file is mapped into a EAD.XML-file by a xslt-transformation |
# The EAD.XML is exported to a designated folder for pickup by the archival information system | # The EAD.XML is exported to a designated folder for pickup by the archival information system | ||
| − | # Every content file is analysed by DROID for format identification and basic technical metadata is extracted (e.g. filesize) | + | # Every content file is analysed by DROID for format identification and basic technical metadata is extracted (e.g. filesize) |
| − | # The output of this analysis is | + | # The output of this analysis is saved into a PREMIS.XML-file (one PREMIS.XML per content object). |
# Every content file is validated and analysed by FITS and content specific technical metadata is extracted. | # Every content file is validated and analysed by FITS and content specific technical metadata is extracted. | ||
# The output of this analysis (FITS.XML) is integrated into the existing PREMIS.XML-files. | # The output of this analysis (FITS.XML) is integrated into the existing PREMIS.XML-files. | ||
# Each content file is scanned for viruses and malware by Clam AV. | # Each content file is scanned for viruses and malware by Clam AV. | ||
| − | # For each content object and for the whole information entity (the book) a PID is fetched from the repository | + | # For each content object and for the whole information entity (the book) a PID is fetched from the repository |
| − | # For each content object and for the whole information entity an AIP is generated. This process includes the generation of RDF | + | # For each content object and for the whole information entity an AIP is generated. This process includes the generation of RDF-tipples, that contain the relationships between the objects. |
| − | # The AIPs are ingested into the repository | + | # The AIPs are ingested into the repository |
| − | |||
| − | + | ||
| + | ==List of Tools== | ||
| + | <!-- List the tools in your workflow in a bulleted list (begin each line with an asterisk). Link to tool entries in COPTR where possible --> | ||
* [[7-Zip]] - Pack and unpack content / SIPs | * [[7-Zip]] - Pack and unpack content / SIPs | ||
* [http://www.docuteam.ch/en/products/it-for-archives/software/ docuteam feeder] - Workflow- and Ingestframework | * [http://www.docuteam.ch/en/products/it-for-archives/software/ docuteam feeder] - Workflow- and Ingestframework | ||
| Line 44: | Line 39: | ||
* [https://en.wikipedia.org/wiki/Clam_AntiVirus Clam AV] - Virus check | * [https://en.wikipedia.org/wiki/Clam_AntiVirus Clam AV] - Virus check | ||
* [[Fedora_Commons]] - Digital Repository | * [[Fedora_Commons]] - Digital Repository | ||
| + | |||
| + | |||
| + | ==Organisation== | ||
| + | <!-- Add the name of your organisation here --> | ||
| + | |||
==Purpose, Context and Content== | ==Purpose, Context and Content== | ||
<!-- Describe what your workflow is for, what the organisational context of the workflow is, and what content it is designed to work with --> | <!-- Describe what your workflow is for, what the organisational context of the workflow is, and what content it is designed to work with --> | ||
| − | |||
==Evaluation/Review== | ==Evaluation/Review== | ||
<!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate --> | <!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate --> | ||
| − | |||
| Line 60: | Line 58: | ||
<!-- Add four tildes below ("~~~~") to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address --> | <!-- Add four tildes below ("~~~~") to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address --> | ||
| − | |||
<!-- Note that your workflow will be marked with a CC3.0 licence --> | <!-- Note that your workflow will be marked with a CC3.0 licence --> | ||