SobekCM METS Files: Structure Maps

Overview

The last mandatory section is the structural map, which is wrapped in a structMap tag. This outlines the hierarchical structure of a digital resource and references the files included in the previous section. This section is used to build the table of contents for the resource.

At least one structure map section must exist and it must contain at least one division. So, even if the details of the structure do not exist, the following structure map must be included:

SobekCM Rules

The SobekCM METS file current accomodates up to two different structure maps. If there are page images associated with the digital resource, the page image structure map should have a TYPE attribute of 'physical'. If there are non-page images associated with the digital resource, the structure map for those files should have a TYPE attribute of 'other'.

Additional details on the two possible structure maps below:

1. Page Images ( to drive the page views )
   • JPEG, JPEG2000, TIFF, GIF, TEXT, PRO, and ALTO files are organized into pages in a page-view structure map according to the filename. For example, �00001.jpg� , �00001.jp2�, �00001.txt� files will all be placed together in the same page.
   • Thumbnails for individual page images may exist and should end �thm.jpg�. So, a file named �00001thm.jpg� would be a thumbnail for the page of files named �00001.*�
   • This structure map currently drives the main Table of Contents view accessible in a SobekCM-library on the left side of the screen.
2. Resource files ( all other files types )
   • This represents other content, such as a structure map of PDFs and/or sound files, etc..
   • These files currently appear online under a DOWNLOADS tab, although if a single PDF exists it will appear under a PDF Viewer tab currently.

We are currently in discussion to change this somewhat and allow for more structure maps and to have an option to display the resource files structure map as the main Table of Contents accessible in on the left side of the screen. That would allow a PDF structure map to appear in the left nav bar during the item view.

All files should be contained within page divisions which can be contained within a deep structure of divisions.

Example

Below is an example book with five pages, each with a variety of page types, and several downloads as well: