The profile specifies no rules of description for conforming documents.
mets/structMap/@TYPE="logical"
TYPE attribute values are *not* restricted to values in this list; rather, values in this list elicit special behaviors in the METS Navigator application.
Nodes with the value TYPE="ill" will have the string "[Illustration]" appended to the value in the LABEL attribute within the "table of contents"-style navigation box in the METS Navigator display.
Nodes with the value TYPE="plate" will have the string "[Plate]" appended to the value in the LABEL attribute within the "table of contents"-style navigation box in the METS Navigator display.
Nodes with the value TYPE="page" will not be displayed in the "table of contents"-style navigation box.
More information on these div TYPE values is available in the structural_requirements section of this profile.
Conforming METS documents may, but need not, contain one or more <dmdSec> elements. Each <dmdSec> may in turn contain a <dmdRef> or a <dmdWrap>. If a <dmdSec> appears with an ID="dmdSec_fullRecordLink", it must have an <mdRef> child with an xlink:href attribute containing a URL. The METS Navigator application will use this URL to override the "linkBackURL" specified in the application configuration file.
Conforming METS documents may, but need not, contain one or more <amdSec> elements. Each <amdSec> , may contain any or all of <techMD>, <rightsMD>, <sourceMD>, or <digiprovMD>, which may each in turn contain a <dmdRef> or a <dmdWrap>.
Conforming METS documents must contain at least one <fileGrp> element within the <fileSec> element. Each <fileGrp> must represent one size or function of derivative image for delivery by METS Navigator. Each file element within a <fileGrp> must have the following attributes, in addition to any other attributes desired or required for a valid METS instance:
1. ID: This ID will be referenced from the <structMap> to provide the network location of a digital file for delivery in METS Navigator.
2. GROUPID: This ID will be used to connect a file in one <fileGrp> with the corresponding file of a different size in other <fileGrp>s.
3. USE: Each <file> element intended to be displayed by METS Navigator must have a USE attribute. In order to be displayed, this USE attribute must match a value specified in the <div name="digitalImage"><parameter type="list" name="size"><value> list in the METS Navigator configuration file. Other <fileGrp> elements with USE attribute values not indicated in the configuration file may be present; however, these files will be ignored by METS Navigator. All <file> elements within a <fileGrp> must have the same USE attribute.
In a conforming METS document, each <file> element must have a child <FLocat> element with the following attributes, in addition to any other attributes desired or required for a valid METS instance:
1. LOCTYPE: A value valid to the METS schema describing the link type in the xlink:href attribute.
2. xlink:href: A link to the image file of the specified size to be displayed by METS Navigator.
Each page image represented in the METS instance to be displayed by METS Navigator must be present as a <file><FLocat> element within each <fileGrp> with a USE attribute indicated in the application configuration file.
Conforming METS documents must contain a <structMap> section with the attribute TYPE="physical". The data within the <structMap TYPE="physical"> section is used to navigate from one page within the METS Navigator display to the next or previous page in the item.
Inside the containing <div> required by the METS schema, the physical <structMap> must contain one <div> for each page of the item(s) to be displayed, with no further nesting. Each of these <div> elements should have the following attributes, in addition to any other attributes desired or required for a valid METS instance:
1. ORDER: Order attributes should be numbered consecutively from 1 to the last <div> present.
2. TYPE: All <div> elements within the outer containing <div> in the physical <structMap> should have the attribute TYPE="page".
Each <div> element representing a page of the item(s) to be displayed should have one or more child <fptr> elements. One <fptr> element should appear for each of the different-sized images in the <fileSec>, referencing the ID of for the page described in the parent <div> in the FILEID attribute. Other <fptr> children may be present; however, METS Navigator will not use these in its display or functionality.
Conforming METS documents must contain a <structMap> section with the attribute TYPE="logical". The data within the <structMap TYPE="logical"> section is used to build the "table of contents"-style navigation in the METS Navigator interface. The value of the LABEL attribute in the <structMap TYPE="logical"> element will appear in the upper left corner of the METS Navigator interface as a page title.
Inside the containing <div> required by the METS schema, the logical <structMap> must contain <div> elements, nested to represent any desired structure for navigation with the item(s) described by the METS document. <div> elements may be nested to any depth of hierarchy; however, the lowest level of hierarchy for each <div> must be one or more <div>s representing the pages of the item(s) to be displayed, matching each lowest-level <div> in the physical <structMap>.
Each of these <div> elements should have the following attributes, in addition to any other attributes desired or required for a valid METS instance:
1. ORDER: Order attributes should be numbered within the containing <div> consecutively from 1 to the last div present.
2. TYPE: Any value may be entered here; however, some values elicit specific behaviors in the METS Navigator interface. Nodes with the value TYPE="ill" will have the string "[Illustration]" appended to the value in the LABEL attribute within the "table of contents"-style navigation box in the METS Navigator display. Nodes with the value TYPE="plate" will have the string "[Plate]" appended to the value in the LABEL attribute within the "table of contents"-style navigation box in the METS Navigator display. All page images described in the physical <structMap> must also be present in the logical <structMap>, as the lowest level of hierarchy within a <div>, and each of these must contain the attribute TYPE="page". Nodes with this TYPE will not be displayed in the "table of contents"-style navigation box.
3. LABEL: The value in this attribute will appear in the "table of contents"-style navigation box in the METS Navigator display as a hyperlink. When this hyperlink is clicked, the interface will navigate to the first page image within this <div> (the child element <div ORDER="1" type="page">).
A conforming METS document may contain a <structLink> element. This profile, however, establishes no guidelines or expectations for its use.
A conforming METS document may contain a <behaviorSec> element. This profile, however, establishes no guidelines or expectations for its use.
A conforming METS document must be valid to the METS Schema, version 1.4 http://www.loc.gov/standards/mets/version14/mets.xsd or 1.5 http://www.loc.gov/standards/mets/version15/mets.xsd.
A conforming METS document may indicate elements from the METS Schema either with a namespace prefix or by declaring a default namespace. Elements from other namespaces must be indicated with valid namespace prefixes.
METS Navigator currently assumes that each page within an item described by a METS document is represented by one or more image files of different sizes.
Images may be in any still image format (e.g., GIF, JPEG, PNG) transmittable by the Web server in use and appropriate for the target audience.
METS Navigator is a METS-based system developed by the Indiana University Digital Library Program for displaying and navigating sets of page images or other multi-part digital objects. Using the information in the METS <structMap> elements, METS Navigator builds a hierarchical menu that allows users to navigate to specific sections of a document, such as title page, specific chapters, illustrations, etc. METS Navigator also allows simple navigation to the next, previous, first, and last page image or component part of a digital object.
METS Navigator is built using Java and open source Web technologies, including the Apache Struts Web Application Framework, the Castor Java & XML Data Binding libraries, and Ant, and runs under a Web application server such as Apache Tomcat.