ViRR and METS

From MPDLMediaWiki
Jump to: navigation, search
Virr Medium Multivolume 31 Static.gif Virtueller Raum Reichsrecht
Overview
Functionalities
Support
Copyright and Disclaimer
Scope
Metadata:
Application Profile · Content Models
Metadata Display · ViRR Metadata
Action Matrix
Transformations:
virr 2 mets · mab 2 mods
mods 2 oai dc · mods 2 marc21
Specification
Intern:
Meetings · GUI · Miscellaneous
Development · Planning · Feedback
Related Projects:
Judicial Journals · Late Scholasticism
Digitization Lifecycle
edit

Format Name

Source: escidoc-toc
Target: METSMetadata Encoding and Transmission Standard

Mapping

Mapping from a ViRRVirtueller Raum Reichsrecht TOCTable of Contents to DFGDeutsche Forschungsgemeinschaft Viewer conform METSMetadata Encoding and Transmission Standard.

METS Element TOC Value Attribute Description
mets xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/mets/mets.xsd" xsi:schemaLocation schemaLocation
dmdSec IDIdentifier=dynamic id This section records all of the descriptive metadata for all items in the METSMetadata Encoding and Transmission Standard object (including both structural map divs and descriptive metadata for data files)
mdWrap MIMETYPE="text/xml"
MDTYPE="MODSMetadata Object Description Schema"
mimetype, mdtype descriptional metadata wrapper
xmldata The TOCs container, mdRecord (escidoc) contains a MODSMetadata Object Description Schema description of the descriptive MDMetadata --- A wrapper element to contain XMLExtensible Markup Language encoded metadata
amdSec IDIdentifier=dynamic id This section records all of the administrative metadata for all items in the METSMetadata Encoding and Transmission Standard object
rightsMD IDIdentifier=dynamic id intellectual property rights metadata
digiprovMD IDIdentifier=dynamic id The digiprovMD element provides a wrapper around a generic metadata section, which should contain information regarding the ultimate origin of a digital object and the derivation of its current elements
fileSec --- --- The content file section records information regarding all of the data files which comprise the digital library object
fileGrp USE=DEFAULT or
USE=MIN or
USE=MAX
use This element allows for the grouping of content files into sets (Thumbnail, Web and Full resolution)
file IDIdentifier= Id of the file item
MIMETYPE=image/jpeg
id, mimetype
FLocat LOCTYPE=URLUniform Resource Locator
xlink:href= baseURL + <toc:ptr IDIdentifier="itemXXPtr" xlink:href="/ir/item/escidoc:XX">
loctype, xlink:href File Location
structMap TYPE=physical (files)or
TYPE=logical (struct elem.)
type The structural map is the heart of a METSMetadata Encoding and Transmission Standard document, defining the hierarchical arrangement of a primary source document which has been digitized
div IDIdentifier=dynamic
DMDID= corresponding dmdSec IDIdentifier
AMDID= corresponding admSec IDIdentifier
TYPE=Page (physical structMap)
TYPE=struct. element (logical structMap)
id, dmdid, admid, type The METSMetadata Encoding and Transmission Standard standard represents a document structurally as a series of nested div elements
div IDIdentifier=dynamic
ORDER=<toc:div IDIdentifier="itemXX" ORDER="X">
ORDERLABEL=<toc:div IDIdentifier="XX" ORDERLABEL="XX">
TYPE=<toc:div IDIdentifier="XX" ... TYPE="XX">
id, order sub div
fptr FILEID=id of the item in the fileSec fileid File Pointer
structLink --- --- The Structural Map Linking section allows for the specification of hyperlinks between different components of a METSMetadata Encoding and Transmission Standard structure delineated in a structural map
smLink --- xlink:from=id in logical structMap
xlink:to=id in physical structMap
An element linking two elements in the structural map
Annotations:
  • If structMap TYPE = physical => div TYPE=page.
  • If structMap TYPE = physical and structMap TYPE=logical exists, these two elements have to be linked in the structLink element.

Rights and Provenance Information: DV Profile

Elements

DV Element Value Description
rights --- surrounding element for rights informations
owner Max Planck Institute for european legal history the items rights owner
ownerLogo http://www.mpier.uni-frankfurt.de/images/minerva_logo.gif logo of the owner
ownerSiteURL http://www.mpier.uni-frankfurt.de the owners homepage
links --- surrounding element for rights informations
reference --- the items metadata on the owners homepage
presentation --- the items scan view on the owners homepage

Structure

<dv:rights xmlns:dv="http://dfg-viewer.de/">
      <dv:owner></dv:owner>
      <dv:ownerLogo></dv:ownerLogo>
      <dv:ownerSiteURL></dv:ownerSiteURL>
</dv:rights>
<dv:links xmlns:dv="http://dfg-viewer.de/">
      <dv:reference></dv:reference>
      <dv:presentation></dv:presentation>
</dv:links>

Requirements for ZVDD

  1. Symbol Remove.png mods:identifier MUST be provided ("zvdd fordert an dieser Stelle einen weltweit eindeutigen Identifier wie z.B. URNUniform Resource Name, PURLPersistent Uniform Resource Locators, DOIDigital Object Identifier, Handle oder ARK...")
  2. Symbol Remove.png References to superordinated works have to be expressed by the element relatedItem with attribute=host, followed by an recordInfo element with an recordIdentifier element (no persistent identifier required).
  3. Symbol Remove.png mets:div TYPE="Monograph", the Type attribute MUST be a value of the "zvdd-Strukturdatentypologie".
  4. Checkmark.png Rights section: owner, logo and homepage elements MUST be provided
  5. Checkmark.png Provenance Information: reference and presentation element MUST be provided
  6. Checkmark.png FileGroups MUST provide the USE attribute
  7. Checkmark.png Min. two FileGroups MUST exist (USE=MIN and USE=DEFAULT)
  8. Checkmark.png mods:part element MUST have an ORDER attribute
  9. Symbol Remove.png mods:part can contain mods:detail (with TYPE attribute containing zvdd-Strukturdatentyp (MUST)) and mods:number element (numbering Information)
  10. Checkmark.png The physical structMap MUST contain a root div element with attribute TYPE=physSequence
  11. Checkmark.png Every div element in the physical and logical structMap MUST have an identifier
  12. Checkmark.png Every div element in the physical structMap MUST have an ORDER attribute (Integer)
  13. Checkmark.png Every div element in the physical structMap can have an ORDERLABEL attribute
  14. Symbol Remove.png Every div element in the physical structMap can have a CONTENTIDS attribute (Persistent identifier for every scan, relevant for citation).
  15. Symbol Remove.png Every div element in logical structMap MUST have an TYPE attribute with value of a "zvdd-Strukturdatentyp"
  16. Symbol Remove.png Every div element in the logical structMap can have a CONTENTIDS attribute (Persistent identifier for every structural, relevant for citation).
  17. Symbol Remove.png Multivolumes and Journals can be modelled as well ("Bandübergreifende Navigation im DFGDeutsche Forschungsgemeinschaft-Viewer wird ermöglicht, indem die Bände und ihre übergeordnete Struktur mittels METSMetadata Encoding and Transmission Standard-Pointern untereinander verknüpft werden. Dies geschieht über eine weitere METSMetadata Encoding and Transmission Standard-Datei, die nur die Zeitschrift oder das Mehrbändgie Werk beschreibt.")
  18. Checkmark.png FilePointer can only link to files, not to fileGroups
  19. Checkmark.png StructLinks always refer from a logical element to a physical element

Related Information

Goobi METS Profile in XML