ToDo's and comments for each Release:

FIRST PHASE - Publication of the digital collection[edit]

Release one[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?)

pending

Start collecting requirements for the viewing environment DigiLib and set up meeting with user group (Contact@FIZ: Frank Schwichtenberg) (Kristina, Tobias)

pending

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

DONE

- 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)

currently using order in containers struct map

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).

no download functionality available

(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?)