Talk:ViRR Scope

From MPDLMediaWiki
Jump to navigation Jump to search

ToDo's and comments for each Release:

FIRST PHASE - Publication of the digital collection[edit]

Release one[edit]

  1. Ingestion
    • scans --> derive from file structure a basic skeleton of toc
    • bibliographic metadata: MAB mapping to MODS
    • structural metadata: eSciDoc container
    • derive basic keywords from bibliographic metadata
  2. Browsing and Display (basic)
    • alphabetical sorted browsing tree (multi-volume works, parts and pages)
    • basic bibliographic metadata (name of book, page)
    • scans in detailed view

Discussion[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:
      1. multi-volume work, e.g. "Vollständiges corpus gravaminum evangelicorum"
      2. part (volume) Vollständiges corpus gravaminum evangelicorum. Band 7
      3. pages
  • Ingestion of bibliographic data: mapping of MAB to MODS
  • 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)

Functional Prototype[edit]

The functional Prototype for R1 should enable the following user goals:

  1. User wants to get an overview on the digital content
  2. User wants to browse within a multivolume work
  3. User wants to browse one volume in detail
  4. User wants to go to certain page within one volume (i.e. logical page)
  5. User wants to view the back cover of a volume
  6. User is not satisfied with selected volume and wants to switch to another volume
  7. User is not satisfied with selected multivolume and wants to switch to another multivolume

Short ToDo Developement[edit]

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

  1. Editing
    • enrich toc sceleton with information on chapters (i.e. bundles)(e.g. page 1-5 = chapter 1)
    • add metadata about the chapters and (multi)volumes

Discussion[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)
    1. GOOBI for METS (expectations of the institute: creation of METS conform XML files)
    2. Docworks: Meta-e cooperation with css (is not interesting if it works with an automatic recognition)
  • Prepare requirements for FIZ for the METS integration

Functional Prototype[edit]

The functional Prototype for R2 should enable the following user goals:

  1. (Multi)Volumes
    • The user wants to enhance the metadata of a multivolume or a volume
  2. Chapters
    • The user wants to define chapters as a sum of separate pages (mark which pages belong together in form of a chapter)
    • The user wants to number serially the defined chapters
    • The user wants to define metadata for each chapter
  3. Pages
    • The user wants to assign an order label to each page
    • The user wants to assign a page label to some pages

Release three[edit]

  1. Browsing (detailed)
    • extension of the alphabetical browsing tree (chapters)
    • systematical browsing tree as alternative entrance to the collection
    • paginator (for lists)
    • paging for images (i.e. "im Buch blaettern")
  2. Display (detailed)
    • integration of digilib functionalities (minimum: zoom in, zoom out)
    • dynamic generation and integration of "identification stamp" ("Herkunftsnachweis") on the images (whole image, selected part of image) --> new Digilib requirement
  3. Search
    • simple search (one search field "any field")
    • advanced search (several special search fields, e.g. one for title, one for author)


Release four[edit]

  1. Functional definition of eSciDoc METS profile
    • needed for import / export
  2. Export
    • image selection
    • downloading of selected images(in separate jpgs)
    • downloading of selected images(in one pdf with a cover page)
    • downloading selected part of an image
    • downloading of METS-xml
  3. Display keywords as list (cf. Index in a book)
  4. Persistent Identifier (PID)


Release ???[edit]

required for DFG

  1. Collection description
  2. URN handling (in the context of an assignment of parts to a multi-volume work)

ToDo (Discussion):

  • Evaluation of the results from JHOVE on the images.

SECOND PHASE - Virtual research environment[edit]

Following is a list of requirements ...detailed release planning will come at a later stage.

  • Ingestion of all 15 available books
  • Workflow for edition process of collection, incl. metadata, images, annotations, external sources (upload, editing, annotating, scientific review etc.)
  • User Management to support workflow
  • Fulltext transcription online (offline client at later stage) - in METS
  • Ingestion/Upload of additional books (digital images + bibliographic metadata) - local resources, BBAW-DTA
  • Adding and editing of bibliographic and descriptive metadata
  • Adding annotations / comments
  • Adding relations
  • Integration of external resources (Deutsches Rechtswoerterbuch/Heidelberg)
  • Creation and maintenance of synonyms
  • Offering metadata to the ZVDD(zentrales Verzeichnis digitalisierter Drucke) and other virtual libraries - OAI interface for the exchange of metadata
  • Sitemap protocol for crawlers
  • Integration of research literature for download (bibliographic lists? articles?)
  • Linking to other digital archives / OPACs /research projects
  • Delivery of one complete dataset for the DNB for long term archiving

ToDo (Discussion):

  • Structural analyzes of the data of the Deutsche Rechtswörterbuch
  • Analyzes of the requirements of the ZVDD
  • Text editor for the creation of transcriptions is needed

Productive environment[edit]

Each phase can be go productive after it is finished!

  • Preparation of productive environment (hardware, support, policies)
  • Offline tool for image processing to improve image quality
  • Fulltext transcription in TEI?
  • Additional functionality for historisch-kritische Editionsarbeit?
  • Concept ViRR for other local/MPG projects (e.g. Policey-Ordnung)

Enhanced Scientific Documentation

Metadata Encoding and Transmission Standard

Virtueller Raum Reichsrecht

Fachinformationszentrum Karlsruhe

Virtueller Raum Reichsrecht

Metadata

Maschinelles Austauschformat für Bibliotheken

Metadata Object Description Schema

Graphical User Interface

Table of Contents

Central European Time

Web Based Server Technology for Viewing and Working with Images

Deutsche Forschungsgemeinschaft

Extensible Markup Language

Portable Document Format

Persistent Identifer or Identification

Uniform Resource Name

JSTOR Harvard Object Validation Environment

Berlin-Brandenburgische Akademie der Wissenschaften

Deutsches Textarchiv

Open Archives Initiative

Deutsche Nationalbibliothek

Zentrales Verzeichnis Digitalisierter Drucke

Text Encoding Initiative

Max-Planck-Gesellschaft

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Talk:ViRR_Scope&oldid=11938"