Difference between revisions of "ViRR and METS"
Jump to navigation
Jump to search
(added category) |
Kleinfercher (talk | contribs) |
||
| (34 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{ViRR}} | |||
=== | == Format Name == | ||
'''Source:''' escidoc-toc <br/> | |||
'''Target:''' METS | |||
== Mapping == | |||
Mapping from a ViRR TOC to DFG Viewer conform METS. | |||
{|border="2" | {|border="2" | ||
|- bgcolor="# | |- bgcolor="#C1CDCD" | ||
! width=" | ! width="200" |'''[http://www.loc.gov/standards/mets/ METS Element]''' | ||
! width=" | ! width="400" |'''[[ViRR_Application_Profile | TOC Value]]''' | ||
! width="150" |'''Attribute''' | ! width="150" |'''Attribute''' | ||
!width=" | !width="400"|'''Description''' | ||
|- style="height:20px" | |- style="height:20px" | ||
| Line 53: | Line 54: | ||
'''Annotations:''' | '''Annotations:''' | ||
*If structMap TYPE=physical => div TYPE=page. | *If structMap TYPE = physical => div TYPE=page. | ||
*If structMap TYPE=physical and structMap TYPE=logical exists, these two elements have | *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 === | === Rights and Provenance Information: DV Profile === | ||
| Line 62: | Line 63: | ||
|- bgcolor="#ccccff" | |- bgcolor="#ccccff" | ||
! width="150" |'''DV Element''' | ! width="150" |'''DV Element''' | ||
! width=" | ! width="300" |'''Value''' | ||
!width="300"|'''Description''' | !width="300"|'''Description''' | ||
|- style="height:20px" | |- style="height:20px" | ||
| Line 93: | Line 94: | ||
</dv:links> | </dv:links> | ||
==Requirements for [http://www.zvdd.de/ ZVDD]== | |||
# [[Image:Symbol_Remove.png | 15px]] mods:identifier MUST be provided ("zvdd fordert an dieser Stelle einen weltweit eindeutigen Identifier wie z.B. URN, PURL, DOI, Handle oder ARK...") | |||
# [[Image:Symbol_Remove.png | 15px]] 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). | |||
# [[Image:Symbol_Remove.png | 15px]] mets:div TYPE="Monograph", the Type attribute MUST be a value of the [http://dfg-viewer.de/fr/strukturdatenset/ "zvdd-Strukturdatentypologie"]. | |||
# [[Image:Checkmark.png | 15px]] Rights section: owner, logo and homepage elements MUST be provided | |||
# [[Image:Checkmark.png | 15px]] Provenance Information: reference and presentation element MUST be provided | |||
# [[Image:Checkmark.png | 15px]] FileGroups MUST provide the USE attribute | |||
# [[Image:Checkmark.png | 15px]] Min. two FileGroups MUST exist (USE=MIN and USE=DEFAULT) | |||
# [[Image:Checkmark.png | 15px]] mods:part element MUST have an ORDER attribute | |||
# [[Image:Symbol_Remove.png | 15px]] mods:part can contain mods:detail (with TYPE attribute containing zvdd-Strukturdatentyp (MUST)) and mods:number element (numbering Information) | |||
# [[Image:Checkmark.png | 15px]] The physical structMap MUST contain a root div element with attribute TYPE=physSequence | |||
# [[Image:Checkmark.png | 15px]] Every div element in the physical and logical structMap MUST have an identifier | |||
# [[Image:Checkmark.png | 15px]] Every div element in the physical structMap MUST have an ORDER attribute (Integer) | |||
# [[Image:Checkmark.png | 15px]] Every div element in the physical structMap can have an ORDERLABEL attribute | |||
# [[Image:Symbol_Remove.png | 15px]] Every div element in the physical structMap can have a CONTENTIDS attribute (Persistent identifier for every scan, relevant for citation). | |||
# [[Image:Symbol_Remove.png | 15px]] Every div element in logical structMap MUST have an TYPE attribute with value of a "zvdd-Strukturdatentyp" | |||
# [[Image:Symbol_Remove.png | 15px]] Every div element in the logical structMap can have a CONTENTIDS attribute (Persistent identifier for every structural, relevant for citation). | |||
# [[Image:Symbol_Remove.png | 15px]] Multivolumes and Journals can be modelled as well ("Bandübergreifende Navigation im DFG-Viewer wird ermöglicht, indem die Bände und ihre übergeordnete Struktur mittels METS-Pointern untereinander verknüpft werden. Dies geschieht über eine weitere METS-Datei, die nur die Zeitschrift oder das Mehrbändgie Werk beschreibt.") | |||
# [[Image:Checkmark.png | 15px]] FilePointer can only link to files, not to fileGroups | |||
# [[Image:Checkmark.png | 15px]] StructLinks always refer from a logical element to a physical element | |||
==Related Information== | |||
* [[DFG Viewer]] METS Profile: http://dfg-viewer.de/profil-der-metadaten/ | |||
* [[Goobi]] METS Profile: [http://gdz.sub.uni-goettingen.de/uploads/media/GDZ_document_format_2005_12_08.pdf GDZ document format for monographs, multivolumes and periodicals] | |||
: [http://gdz.sub.uni-goettingen.de/uploads/media/GDZ_METS_02.xml Goobi METS Profile in XML] | |||
* [http://gdz.sub.uni-goettingen.de/uploads/media/zvdd-dfgviewer-mets-profil-v2_20081201.pdf zvdd METS requirements] | |||
* General information about [[METS | METS in CoLab]] | |||
[[Category:Virtueller Raum Reichsrecht|METS Profile]] | [[Category:Virtueller Raum Reichsrecht|METS Profile]] | ||
[[Category:Metadata]] | [[Category:Metadata]] | ||
[[Category:ESciDoc Mappings]] | [[Category:ESciDoc Mappings]] | ||
Latest revision as of 09:27, 28 May 2010
|
Format Name[edit]
Source: escidoc-toc
Target: METS
Mapping[edit]
Mapping from a ViRR TOC to DFG Viewer conform METS.
| 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 to be linked in the structLink element.
Rights and Provenance Information: DV Profile[edit]
Elements[edit]
| 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[edit]
<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[edit]
mods:identifier MUST be provided ("zvdd fordert an dieser Stelle einen weltweit eindeutigen Identifier wie z.B. URN, PURL, DOI, Handle oder ARK...")- 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).
- mets:div TYPE="Monograph", the Type attribute MUST be a value of the "zvdd-Strukturdatentypologie".
Rights section: owner, logo and homepage elements MUST be provided- Provenance Information: reference and presentation element MUST be provided
- FileGroups MUST provide the USE attribute
- Min. two FileGroups MUST exist (USE=MIN and USE=DEFAULT)
- mods:part element MUST have an ORDER attribute
- mods:part can contain mods:detail (with TYPE attribute containing zvdd-Strukturdatentyp (MUST)) and mods:number element (numbering Information)
- The physical structMap MUST contain a root div element with attribute TYPE=physSequence
- Every div element in the physical and logical structMap MUST have an identifier
- Every div element in the physical structMap MUST have an ORDER attribute (Integer)
- Every div element in the physical structMap can have an ORDERLABEL attribute
- Every div element in the physical structMap can have a CONTENTIDS attribute (Persistent identifier for every scan, relevant for citation).
- Every div element in logical structMap MUST have an TYPE attribute with value of a "zvdd-Strukturdatentyp"
- Every div element in the logical structMap can have a CONTENTIDS attribute (Persistent identifier for every structural, relevant for citation).
- Multivolumes and Journals can be modelled as well ("Bandübergreifende Navigation im DFG-Viewer wird ermöglicht, indem die Bände und ihre übergeordnete Struktur mittels METS-Pointern untereinander verknüpft werden. Dies geschieht über eine weitere METS-Datei, die nur die Zeitschrift oder das Mehrbändgie Werk beschreibt.")
- FilePointer can only link to files, not to fileGroups
- StructLinks always refer from a logical element to a physical element
Related Information[edit]
- DFG Viewer METS Profile: http://dfg-viewer.de/profil-der-metadaten/
- Goobi METS Profile: GDZ document format for monographs, multivolumes and periodicals
- zvdd METS requirements
- General information about METS in CoLab