Difference between revisions of "Talk:ViRR Specification"

From MPDLMediaWiki
Jump to navigation Jump to search
m (Reverted edits by Kristina (Talk); changed back to last version by Andi)
Line 1: Line 1:
ToDo's, comments for each Rélease
== Discussion on data formats ==
meeting on 12th of October


== FIRST PHASE - Publication of the digital collection ==
In general, an external format (like METS/eBinds/eSciDoc) can be used in three different ways:
# importing digital objects in eSciDoc's native format
# importing from METS format - might be very problematic from Natasa's point of view, e.g. because METS is very broad and only a specific import for ViRR METS can be done
# supporting METS as native format in eSciDoc -> this would require a lot of redesign in the basic services. According to Malte there are related requirements coming from the GBV
# exporting to METS -> export is probably not very problematic


=== Release one ===
Questions:
# from where does the concrete METS requirement come from? Does the MPIeR have concrete needs or is it more a "best practice" & assumption?
# is the eSciDoc native format rich/flexible enough to represent the [structure of the] digital objects as required by MPIeR?
# If yes, does this mean we need to provide an offline editor for the eSciDoc native format ourselves?


# Ingestion
Result: This question is the mayor decision in the project and will influence the required/chosen implementation essentially. The decision needs to be taken until January 2008! We decided to prepare an detailed evaluation together with FIZ
#* scans --> derive from file structure a first skeleton of toc (name of book, sequence of pages)
#* bibliographic metadata (currently in MAB) - either entered manually or ingested
#* derive basic keywords from title of book (to be checked with institute)
# Display (basic)
#* thumbnail lists
#* basic bibliographic metadata (name of book, page)
#* scans
# Browsing (basic)
#* browsing tree (books and pages), sorted alphabetically by title
 
ToDos:
*  ingestion of bibliografic data: either mapping MAB to eSciDoc XML or to Dublin Core, or enter data manually (evaluation by inga?)
* relation to eSciDoc METS profile (first draft based on Ingas mapping ebinds<=>METS)?
 
''Already some input from Inga: Generic Mapping MAB=> eSciDoc is not of great help, as MAB is poor in bibliografic information, in addition, each MAB user uses his own adapted MAB and using MAB means running into severe character set problems. If a mapping is needed, mapping to DC might be sufficient. In addition, instead of mapping, manual data entry should be considered, especially when dealing only with 2 books. In any case, new "eSciDoc VIRR profile" might be needed, as genre types and current PubMan Metadata won't cover the VIrr material. ''
* improve quality of image files (based on TIFFs) => for improved thumbnails + additional resolution for web presentation => check concrete requs with Institute ("schwarze Ränder" on TIFFs would have to be done by institute). Check requirements for resolution needed by digilib
* functional prototype for Display and browsing
* start collecting requirements for the viewing environment [[Digilib#Requirements_for_Solutions|DigiLib]] and set up meeting with user group (Contact@FIZ: Frank Schwichtenberg) (Kristina, Tobias)
 
=== Release two ===
 
# Editing
#* enrich toc sceleton with information on chapters (i.e. bundles)(e.g. page 1-5 = chapter 1)
#* add metadata about the chapters, e.g. keywords
#* editing via simple edit mask or already with METS editor (selection of Editor depends on eSciDoc METS profile)
 
'''TO DO:'''
* prepare first draft eSciDoc METS profile (based on bibliografic data needed, descriptive data needed)
* decide on recommended METS editor
* prepare requirements for FIZ for the METS integration
 
=== Release three ===
 
# Display (detailled)
#* 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
# Browsing (detailled)
#* extension of the alphabetical browsing tree (chapters)
#* chronological navigation  on book and/or chapter level?(depends on descriptive Metadata! )
#* paginator (for lists)
#* paging for images (i.e. "im Buch blaettern")
# Search
#* simple search (one search field "any field")
#* advanced search (several special search fields, e.g. one for title, one for author)
 
=== Release four ===
 
# Functional definition of eSciDoc METS profile
#* needed for import / export
# Export
#* image selection
#* downloading/printing of selected images(in separate jpgs)
#* downloading/printing of selected images(in one pdf with a cover page)
#* downloading/printing selected part of an image
#* downloading of METS-xml
# Display keywords as list (cf. Index in a book)
# Persistent Identifier (PID)
 
== SECOND PHASE - Virtual research environment ==
Following is a list of requirements to be met...detailled release planning at a later stage.
 
* 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 ressources, BBAW-DTA
* Adding and editing of bibliografic and descriptive metadata
* Adding annotations
* Adding relations
* Adding comments
* Integration of external ressources (Deutsches Rechtswoerterbuch/Heidelberg)
* Creation and maintenance of synonyms
* Offering metadata to the ZVDD and other virtual libraries - OAI interface
* Sitemap protocol for crawlers
* Integration of research literature for download (bibliografic lists? articles?)
* Linking to other digital archives / OPACs /research projects
 
 
'''TO DO:'''
* 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
 
== THIRD PHASE - Productive environment ==
* 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)

Revision as of 12:46, 30 January 2008

Discussion on data formats[edit]

meeting on 12th of October

In general, an external format (like METS/eBinds/eSciDoc) can be used in three different ways:

  1. importing digital objects in eSciDoc's native format
  2. importing from METS format - might be very problematic from Natasa's point of view, e.g. because METS is very broad and only a specific import for ViRR METS can be done
  3. supporting METS as native format in eSciDoc -> this would require a lot of redesign in the basic services. According to Malte there are related requirements coming from the GBV
  4. exporting to METS -> export is probably not very problematic

Questions:

  1. from where does the concrete METS requirement come from? Does the MPIeR have concrete needs or is it more a "best practice" & assumption?
  2. is the eSciDoc native format rich/flexible enough to represent the [structure of the] digital objects as required by MPIeR?
  3. If yes, does this mean we need to provide an offline editor for the eSciDoc native format ourselves?

Result: This question is the mayor decision in the project and will influence the required/chosen implementation essentially. The decision needs to be taken until January 2008! We decided to prepare an detailed evaluation together with FIZ

Metadata Encoding and Transmission Standard

Enhanced Scientific Documentation

Virtueller Raum Reichsrecht

Gemeinsamer Bibliotheksverbund

Max-Planck-Institut für europäische Rechtsgeschichte

Fachinformationszentrum Karlsruhe

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