Difference between revisions of "ViRR Ingestion"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
{{ESciDoc Solutions}} | {{ESciDoc Solutions}} | ||
Line 25: | Line 16: | ||
:* Ingestion of bibliographic data: mapping of [[Talk:ViRR_Metadata#MAB_to_MODS_mapping|MAB to MODS]] | :* Ingestion of bibliographic data: mapping of [[Talk:ViRR_Metadata#MAB_to_MODS_mapping|MAB to MODS]] | ||
== Scenarios == | |||
'''Scenario 1''' <br/> | '''Scenario 1''' <br/> | ||
# The user want to upload one book. | # The user want to upload one book. |
Revision as of 09:23, 11 July 2008
|
Requirements for R1[edit]
- Ingestion of scans (incl. derivation of a basic skeleton of the books)
- Naming convention of the files
- e: einband (always e1-e4, two for the front cover and two for the back cover)
- v: vorgebundene, nichtbedruckte Seiten (always after the front cover)
- d: derivate (content pages)
- n: nachgebundenen Seiten (always after the content pages)
- Basic skeleton already includes three levels:
- multi-volume work, e.g. "Vollständiges corpus gravaminum evangelicorum"
- part (volume) Vollständiges corpus gravaminum evangelicorum. Band 7
- pages
- Naming convention of the files
- Ingestion of bibliographic data: mapping of MAB to MODS
- Ingestion of scans (incl. derivation of a basic skeleton of the books)
Scenarios[edit]
Scenario 1
- The user want to upload one book.
- The book consists of several images (available as tiffs) which first have to be convert into jpgs for the web presentation.
- The newly created jpgs have to be uploaded in a batch method to the system. The correct order of the images (based on the name of the files) has to be kept and saved.
- A MAB file with the bibliographic metadata of the book has to be uploaded to the system.
- The system derives a first skeleton of the ToC of the book from the uploaded data (title, number of pages)