Difference between revisions of "ViRR and METS"

From MPDLMediaWiki
Jump to navigation Jump to search
m (→‎Support of Goobi: formatting)
(→‎Support of DFG Viewer: Add TOC-METS transformation)
Line 4: Line 4:


== Support of DFG Viewer ==
== Support of DFG Viewer ==
Requirements from [[DFG Viewer]]:
The TOC-METS mapping according to the minimal requirements for dfg-viewer (http://dfg-viewer.de/fileadmin/groups/dfgviewer/DFG-Viewer_Beispiel__minimal_.xml)
* Transformation of eSciDoc container format to METS: transformation (XSLT) will be delivered by the framework. We need to ensure that this METS profile is
 
* Structural Elements: The DFG Viewer provides a standardized [http://dfg-viewer.de/profil-der-strukturdaten/list of structural elements] which can be used for the markup of different parts within the digitized books (e.g. chapter, cover). This list also contains a mapping to the vocabulary used by the [http://www.zvdd.de/ ZVDD], which is similar to the one from the DFG Viewer, but not so detailed. So its easy ti fulfill the requirement from the DFG to deliver all the metadata to the ZVDD. <br/>
{|border="2"
:--> Has to be part of the specification!
|- bgcolor="#ccccff"
! width="150" |'''METS Element'''
! width="150" |'''TOC Value'''
! width="150" |'''Attribute'''
!width="300"|'''Description''' 
|- style="height:20px"
 
|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" <br/>'''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<br/> '''USE'''=MIN or<br/> '''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 <br/> '''MIMETYPE'''=image/jpeg||id, mimetype||
|-
|FLocat ||'''LOCTYPE'''=URL <br/> '''xlink:href'''= baseURL + <toc:ptr ID="itemXXPtr" xlink:href="/ir/item/escidoc:XX"> ||loctype, xlink:href||File Location
|-
|structMap ||'''TYPE'''=physical (files)or <br/> '''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 <br/> '''DMDID'''= corresponding dmdSec ID <br/> '''AMDID'''= corresponding admSec ID <br/> '''TYPE'''=Page (physical structMap) <br/> '''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 <br/> '''ORDER'''=<toc:div ID="itemXX" ''ORDER''="X"> <br/>'''ORDERLABEL'''=<toc:div ID="XX" ORDERLABEL="XX"> <br/> '''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 <br/> 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.


== Support of Goobi ==
== Support of Goobi ==

Revision as of 08:19, 29 October 2008

eSciDoc Solutions

PubMan:
Overview · Functionalities
Interfaces · Support

Faces:
Overview · Functionalities
Scope · Support

ViRR:
Overview · Functionalities
Scope · Support

imeji
Digitization Lifecycle

edit


One requirement of the ViRR Solution is the usage of METS. The METS profile should cover the profile for the DFG Viewer and for Goobi (GDZ).

Support of DFG Viewer[edit]

The TOC-METS mapping according to the minimal requirements for dfg-viewer (http://dfg-viewer.de/fileadmin/groups/dfgviewer/DFG-Viewer_Beispiel__minimal_.xml)

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.

Support of Goobi[edit]

Goobi is a project of the GDZ (Göttinger Digitalisierungszentrum).

Göttinger Digitalisierungszentrum

Deutsche Forschungsgemeinschaft

Table of Contents

Metadata Encoding and Transmission Standard

Identifier

Metadata Object Description Schema

Metadata

Extensible Markup Language

Uniform Resource Locator

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=ViRR_and_METS&oldid=22867"