Difference between revisions of "Talk:ViRR Scope"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
== Release one == | == Release one == | ||
=== | === ToDos Development === | ||
* Rework / clarification of the container format in eSciDoc (dev. Team) as basis for the [[Metadata Encoding and Transmission Standard|METS]] profile | * Rework / clarification of the container format in eSciDoc (dev. Team) as basis for the [[Metadata Encoding and Transmission Standard|METS]] profile | ||
| Line 49: | Line 49: | ||
:* Prepare requirements for FIZ for the METS integration | :* Prepare requirements for FIZ for the METS integration | ||
=== | === ToDos Development === | ||
* Prepare requirements for FIZ for the METS integration | * Prepare requirements for FIZ for the METS integration | ||
Revision as of 07:17, 6 May 2008
ToDo's and comments for each Release:
FIRST PHASE - Publication of the digital collection[edit]
Release one[edit]
ToDos Development[edit]
- Rework / clarification of the container format in eSciDoc (dev. Team) as basis for the METS profile
- Relation between the eSciDoc container format and the METS profile for ViRR (first draft based on Ingas mapping ebinds <=> METS?)
- Start collecting requirements for the viewing environment DigiLib and set up meeting with user group (Contact@FIZ: Frank Schwichtenberg) (Kristina, Tobias)
- ingest two multi-volumes
- ingest two books into multi-vol1
- ingest one book into multi-vol2
- create Context VIRR
- create User VIRR_user who has Depositor, MD-Editor, Moderator role for context VIRR
- create ContentModel "MultiVolume"
- create 2 containers with content model "MultiVolume"
- each container has 2 metadata records (MAB format, MODS format)
- create ContentModel "ScannedBook" (or find better name)
- create 3 containers with content model "ScannedBook" (or find better name)
- each container has 2 metadata records (MAB format, MODS format)
- add "ScannedBook" containers to "MultiVolume" containers
- create ContentModel "ScannedBookPage" (or find better name)
- create Items with "ScannedBookPage"
- each created item has a metadata record in MODS format+extra metadata (to check respective MODS metadata to put the Page sequence)
- each created item should have 2 components
- component: content-category="original", visibility="public"
- component: content-category="thumbnail", visibility="public"
- submit, release the 5 containers and all Items
- for all users (no AA included) implement "browsing" GUI (simple tree for books) where top-level nodes are containers and second-level nodes are Items
- workaround needed: for sorting by page number on the browsing interface already (not certain if we can simply take the order as it is stated in the container's struct map for start).
- In respect to a possible requirement to see one page after another one may use content-relations to link pages. E.g. <container> <firstPage> <item1> and <item1> <nextPage> <item2> and <item2> <nextPage> <item3> etc. Because if one can get the order form a list (or TOC) of the container that information is not (directly) available when displaying a single page-item but there should certainly be a "next"-button. Frank 15:10, 12 March 2008 (CET)
- workaround needed: for sorting by page number on the browsing interface already (not certain if we can simply take the order as it is stated in the container's struct map for start).
- for all users (no AA included) implement "view-container/item" GUIs (for containers it displays the container metadata, for items it displays the item metadata and the image thumbnail as image on GUI) (link to component "original" should be provided for download).
- (optionally, to decide when most of these things are done)-> to display the original image (or a working version of the original image via Digilib server?)
Release two[edit]
ToDos Service Management[edit]
- Editing via simple edit mask or already with METS editor (selection of Editor depends on eSciDoc METS profile)?
- Prepare a first draft of the eSciDoc METS profile (based on bibliographic data needed, descriptive data needed), based on the basic METS metadata required by the DFG viewer
- Decide on recommended METS online xml editor for the acquisition of structural data (which can also be used offline if possible)
- Prepare requirements for FIZ for the METS integration
ToDos Development[edit]
- Prepare requirements for FIZ for the METS integration