Content Models

Our repository uses an 'atomistic' content model, namely one in which each digital object is spread across several fedora objects. This makes each fedora object very small and flexible. Using this approach does require greater use of fedora's resource index (so hone your Sparql skills).

amherst:objectCModel

This is a “core” object in fedora. These objects are indexable by Solr, and they contain the following datastreams:

  • MODS
  • TN
  • ICON
  • SMALL_SIZE

Content Model

Service Definition

Service Deployment

amherst:imageCModel

This is a content model for a “simple” image-based object. There are no required datastreams per se. These objects may have relationships to objects with the following content models:

  • amherst:vraCModel
  • amherst:masterCModel
  • amherst:jp2CModel
  • amherst:jpegCModel

Content Model

amherst:manuscriptCModel

This is a content model for manuscripts. These objects typically also have an amherst:objectCModel model. Like amherst:imageCModel there are no required datastreams.

Content Model

amherst:pageCModel

This is a content model for manuscript pages. These objects typically also have an amherst:imageCModel model. There are no required datastream. Each of these objects should be related to the corresponding manuscript with an isPartOf relationship. These objects also use the http://acdc.amherst.edu/relationships# namespace to describe isPrecedingPageOf and isFollowingPageOf. Like amherst:imageCModel, there are no required datastreams.

Content Model

amherst:masterCModel

This is a content model for the original (archival) image stored in the repository. It contains the following datastream:

  • OBJ

This object should have an isPartOf relationship to the core digital object.

Content Model

amherst:vraCModel

This is a content model for the VRA Core metadata for a particular object. Objects with this content model should define an isMetadataFor relationship to the core amherst:imageCModel. They contain the following datastreams:

  • VRA

Content Model

amherst:exifCModel

If EXIF metadata is available, then it should be in a separate object, stored with an amherst:exifCModel model, related to the original image through an isMetadataFor and isDerivationOf relationship. The metadata itself will be available in the only required datastream:

  • EXIF

Content Model

amherst:jp2CModel

This is a content model for a JPEG 2000 image. The JP2 image is stored in the only required datastream:

  • JP2

This item should also contain an isPartOf relationship to the core object and an isDerivationOf the archival image.

Content Model

Service Definition

Service Deployment

amherst:jpegCModel

This is the content model for a simple JPEG image. The digital object will contain the following datastreams:

  • FULL_SIZE
  • MEDIUM_SIZE

Each of these digital objects should be related to the archival image through an isDerivationOf relationship. They should be related to the core digital object through an isPartOf relationship.

Content Model

Service Definition

Service Deployment

amherst:collectionCModel

This is the content model for a collection object. It will typically only have a RELS-EXT datastream.

Content Model

amherst:personalCModel

This is the content model for a personal collection. It, too, will typically only have a RELS-EXT datastream.

Content Model

content_models.txt · Last modified: 2013/02/21 17:47 by acoburn@amherst.edu
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International