Talk:ViRR and METS

From MPDLMediaWiki
Jump to navigation Jump to search

METS[edit]

General Information[edit]

  • METS enables the mark up of front, cover, etc.
  • METS is an international standard. It displays the hierarchical structure, the name and the location of the data storage and the metadata of objects. --> METS can be used for descriptive metadata as well as container format.
  • Im Interesse weiterer Projekte (fuer die ggf. eine Foerderung der DFG beantragt werden koennte) ist METS nahezu zwingend. Alternativ zu diesem seitenorientierten Format kaeme TEI als dokumentorientiertes Format in Frage. Das MPI praeferiert eindeutig METS, da es den gegenwaertigen Anforderungen genuegt und einen geringeren Aufwand nach sich zieht. s. auch DFG-Praxisregeln, S. 17. 18.10.2007, S. Amedick

Open Discussion[edit]

  • VIRR needs to handle METS for:
    1. Import
      Therefor a Mapping from VIRR METS to TOC is needed.
    2. Export
      See closed discussion
  • We should define a VIRR METS application profile

Closed Discussion[edit]

  • A METS import and export is needed. Therefore, an Mapping from the eSciDoc Container Format to METS is needed. This has to be written in XSLT (for exemple see the Mapping eSciDoc to DC.
    Mapping for TOC - DFG METS is already implemented.--Friederike 09:02, 11 February 2009 (UTC)
  • In general, an external format (like METS/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. is the eSciDoc native format rich/flexible enough to represent the [structure of the] digital objects as required by MPIeR?
  2. If yes, does this mean we need to provide an offline editor for the eSciDoc native format ourselves?
--> 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.