ViRR and METS

From MPDLMediaWiki
Jump to navigation Jump to search

One requirement of the ViRR Solution is the in- and export of METS data.

General Information[edit]

Interesting METS Profiles

Goobi METS Profile in XML

TOC/METS Mapping[edit]

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 ID=dynamic id This section records all of the descriptive metadata for all items in the METS object (including both structural map divs and descriptive metadata for data files)
mdWrap MIMETYPE="text/xml"
MDTYPE="MODS"
mimetype, mdtype descriptional metadata wrapper
xmldata The TOCs container, mdRecord (escidoc) contains a MODS description of the descriptive MD --- A wrapper element to contain XML encoded metadata
amdSec ID=dynamic id This section records all of the administrative metadata for all items in the METS object
rightsMD ID=dynamic id intellectual property rights metadata
digiprovMD ID=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 ID= Id of the file item
MIMETYPE=image/jpeg
id, mimetype
FLocat LOCTYPE=URL
xlink:href= baseURL + <toc:ptr ID="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 METS document, defining the hierarchical arrangement of a primary source document which has been digitized
div ID=dynamic
DMDID= corresponding dmdSec ID
AMDID= corresponding admSec ID
TYPE=Page (physical structMap)
TYPE=struct. element (logical structMap)
id, dmdid, admid, type The METS standard represents a document structurally as a series of nested div elements
div ID=dynamic
ORDER=<toc:div ID="itemXX" ORDER="X">
ORDERLABEL=<toc:div ID="XX" ORDERLABEL="XX">
TYPE=<toc:div ID="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 METS 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 tp be linked in the structLink element.

Rights and Provenance Information: DV Profile[edit]

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>