Difference between revisions of "Workflow:Workflow for ingesting digitized books into a digital archive"

From COPTR
Jump to: navigation, search
(Created page with "Upload file (Toolbox on left) and add a workflow image here or remove Category:COW Workflows ==Workflow Description== <div class="toccolours mw-coll...")
 
Line 1: Line 1:
 
[[File:workflow.png|Upload file (Toolbox on left) and add a workflow image here or remove]]
 
[[File:workflow.png|Upload file (Toolbox on left) and add a workflow image here or remove]]
 
[[Category:COW Workflows]]
 
[[Category:COW Workflows]]
 +
 +
{{Infobox_cheese
 +
|name=Ingest of digitized books
 +
|category=Ingest
 +
|status=Testphase
 +
|tools=
 +
* [[7-Zip]]
 +
* [http://www.docuteam.ch/en/products/it-for-archives/software/ docuteam feeder]
 +
* [https://en.wikipedia.org/wiki/CURL cURL]
 +
* [https://en.wikipedia.org/wiki/Saxon_XSLT Saxon]
 +
* [[DROID]]
 +
* [[FITS_(File_Information_Tool_Set)]]
 +
* [https://en.wikipedia.org/wiki/Clam_AntiVirus Clam AV]
 +
* [[Fedora_Commons]]
 +
|organisation=[http://www.ub.unibe.ch/ Universitätsbibliothek Bern]
 +
}}
  
 
==Workflow Description==
 
==Workflow Description==
Line 27: Line 43:
 
# 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.
 
# 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
 +
# The data producer get's informed, that the ingest finished successfully
  
  
Line 43: Line 60:
 
==Organisation==
 
==Organisation==
 
<!-- Add the name of your organisation here -->
 
<!-- Add the name of your organisation here -->
 
+
[http://www.ub.unibe.ch/ Universitätsbibliothek Bern]
  
 
==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 -->
 +
The University Library of Bern digitizes historical books, maps and journals that are part of the "Bernensia" collection (Media about or from authors from the state and city of Bern). The digital object resulting from this digitization process are unique and therefore of great value for the library. To preserve them for the longterm, these objects have to be ingested into the digital archive of the libray. The main goal of this workflow is to provide an easy interface to the data provider (digitization team), to provide a simple gateway to the digital archive and to collect the as much metadata as is available in an automated way.
  
  
 
==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 -->
 +
A subset of the workflow has been setup and tested as a proof of concept on a prototype system. It will be installed and extended in a productive environment shortly .
  
  
Line 58: Line 77:
  
 
<!-- 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 -->
 +
[[User:ChrisReinhart|ChrisReinhart]] ([[User talk:ChrisReinhart|talk]]) 14:00, 7 April 2017 (UTC)
  
  
 
<!-- Note that your workflow will be marked with a CC3.0 licence -->
 
<!-- Note that your workflow will be marked with a CC3.0 licence -->

Revision as of 14:00, 7 April 2017

Upload file (Toolbox on left) and add a workflow image here or remove


Ingest of digitized books
Category:Ingest
Status:Testphase
Tools:* 7-Zip
Organisation:Universitätsbibliothek Bern

Contents

Workflow Description

Ingest-E-rara-eng.png

  1. The data provider provides his content as an input for the transfer tool (currently in development)
  2. The transfer tool creates a zip-container with the content and calculates a checksum of the container
  3. The zip-container and the checksum are bundled (another zip-container or a plain folder) and build the SIP
  4. The transfer tool moves the SIP to a registered, data provider specific hotfolder, which is connected to the ingest server
  5. As soon as the complete SIP has been transfered to the ingest server, a trigger is raised and the ingest workflow starts
  6. The SIP gets unpacked
  7. 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.
  8. 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)
  9. Based on the OPAC-systemnumber (encoded in the content filename) descriptive metadata is fetched from the library's OPAC over its OAI-PMH interface
  10. The OPAC returns a MARC.XML-file.
  11. The MARC.XML-file is mapped into a EAD.XML-file by a xslt-transformation
  12. The EAD.XML is exported to a designated folder for pickup by the archival information system
  13. Every content file is analysed by DROID for format identification and basic technical metadata is extracted (e.g. filesize)
  14. The output of this analysis is saved into a PREMIS.XML-file (one PREMIS.XML per content object).
  15. Every content file is validated and analysed by FITS and content specific technical metadata is extracted.
  16. The output of this analysis (FITS.XML) is integrated into the existing PREMIS.XML-files.
  17. Each content file is scanned for viruses and malware by Clam AV.
  18. For each content object and for the whole information entity (the book) a PID is fetched from the repository
  19. 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.
  20. The AIPs are ingested into the repository
  21. The data producer get's informed, that the ingest finished successfully


List of Tools


Organisation

Universitätsbibliothek Bern

Purpose, Context and Content

The University Library of Bern digitizes historical books, maps and journals that are part of the "Bernensia" collection (Media about or from authors from the state and city of Bern). The digital object resulting from this digitization process are unique and therefore of great value for the library. To preserve them for the longterm, these objects have to be ingested into the digital archive of the libray. The main goal of this workflow is to provide an easy interface to the data provider (digitization team), to provide a simple gateway to the digital archive and to collect the as much metadata as is available in an automated way.


Evaluation/Review

A subset of the workflow has been setup and tested as a proof of concept on a prototype system. It will be installed and extended in a productive environment shortly .


Further Information

ChrisReinhart (talk) 14:00, 7 April 2017 (UTC)