Child pages
  • Multi-volume content model
Skip to end of metadata
Go to start of metadata

Status

This content model is implemented, but not yet utilized in the repository.

content model object in Fedora: cmodel:pagedmultivolume

This content model will be used for collections where we expect to have objects with multiple volumes for a single metadata record. Collections may contain multi-volume as well as single-volume (paged) objects. To simplify the interaction, the same PURL format identifiers must function in logically similar ways for each type of object.

Each paged item that represents a volume within the pagedmultivolume object must have a relationship in its RELS-EXT datastream with the isPartOf relationship as well as a locally defined sequence number indicating the order of the volume. A disseminator may be written for the pagedmultivolume object to retrieve all children and their sequence number. This will be implemented the same was it is for the volume content model.


pagedmultivolume.docx

Metadata

*Descriptive metadata will be present only for objects in the second row of the chart.

PURLs

  • Objects in the second row of the chart will all support the following purl format identifiers
    • thumbnail - displays a thumbnail image of the first page (or the first page of the first volume)
    • default view - displays a pageturner interface (sometimes with inter-volume navigation)
    • mets - displays the METADATA datastream for the item

Identifiers

Typically the item right below the collection level item will be given a unique identifier, and each item below that will be a derivative identifier generated by appending a hyphen and sequence number. As always, these identifiers are not guaranteed to have any meaning, but such a pattern may be used when assigning identifiers.

Service Definitions

The content model is associated with the sdef:multipart service deployment. When implemented (as by sdep:multipart ) the following three disseminations are provided:

  • getParts (returns each part and its sequence number in sparql)
  • getPartsAsHTML (returns an HTML rendering of the above result)
  • getPartCount (returns a sparql result set containing the number of parts)

When the specification is written, we will add a disseminator to generate a METS file suitable for METS navigator, although this may be attached a different service definition/deployment pair.

Outstanding questions

  • Will any additional fields be required in the METS Navigator file for paged items that are an element within a volume? (Such as a reference to the volume level METS Navigator file, title information, etc.)
  • No labels