Compound Object Work

About

Compound object works are works that are made up of 2 or more works. These works can be a combination of images, audio, video, and/or books. Compound objects are special in that the works the objects consist of are significant enough that they are able to stand alone in the wild in a system like the Digital Public Library of America. These sub parts have significant metadata which should lead to their inclusion in OAI-PMH. For the sake of user experience, parts of compound objects may not be displayed as stand alone objects in the same collection of a parent compound object.

Compound object works are an ordered aggregation of 1-n pcdmuse:Work s. Each member Work should have an ore:Proxy that has 0-1 iana:next and 0-1 iana:prev properties that point to the next or previous compound part in a sequence. Since member works may stand alone elsewhere in the repository, the member works do not have pcdm:memberOf properties that point at the parent object. Instead, the parent work has a pcdm:hasMember property that points at child works. The parent work also points at ore:Proxy s with ore:proxyFor and ore:proxyIn properties that relate to the compound object parts via iana:first and iana:last properties.

All compound objects’ individual works’ filesets should be available for download.

Book works within a compound object work should have OCR and HOCR.

All audio and video works within a compound object work may have 0-n closed-captioning / subtitle files that should be associated with it in the viewer.

All filesets may have restrictions that prohibit view / access.

Metadata Properties

Descriptive Properties

Descriptive properties are described in our vendor supplied MAP.

Structural Properties

Suggested structure for a book is described here.

  1@prefix : <https://location-of-future-repository/extra/paths/> .
  2@prefix bibframe: <http://id.loc.gov/ontologies/bibframe/> .
  3@prefix dcterms: <http://purl.org/dc/terms/> .
  4@prefix fedora:  <http://fedora.info/definitions/v4/repository#> .
  5@prefix iana:  <http://www.iana.org/assignments/relation/> .
  6@prefix identifiers: <http://id.loc.gov/vocabulary/identifiers/> .
  7@prefix ore: <http://www.openarchives.org/ore/terms/> .
  8@prefix pcdm: <http://pcdm.org/models#> .
  9@prefix pcdmff: <http://pcdm.org/file-format-types#> .
 10@prefix pcdmuse: <http://pcdm.org/use#> .
 11@prefix pcdmworks: <http://pcdm.org/works#> .
 12@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
 13
 14:sample-rfta-artist-compound-object a pcdmworks:Work ;
 15    dcterms:title "A Dog Left Behind" ;
 16    identifiers:local "rftaart:76" ;
 17    iana:first :proxy-for-sample-rfta-artist-compound-object-part1 ;
 18    iana:last :proxy-for-sample-rfta-artist-compound-object-part2 ;
 19    pcdm:hasMember :sample-rfta-artist-compound-mods, :sample-rfta-artist-compound-object-tn, :rftaartists_3, :rftaartists_53 .
 20
 21:sample-rfta-artist-compound-mods a pcdmworks:Fileset ;
 22    rdfs:label "MODS from Islandora - Fileset" ;
 23    pcdm:memberOf :sample-rfta-artist-compound-object ;
 24    pcdm:hasFile :sample-file-mods-xml .
 25
 26:sample-file-mods-xml a pcdmff:Markup ;
 27    rdfs:label "MODS XML from Islandora" ;
 28    pcdm:fileOf :sample-rfta-artist-compound-mods ;
 29    fedora:hasVersions :path-to-the-actual-mods .
 30
 31:sample-rfta-artist-compound-object-tn a pcdmworks:Fileset ;
 32    rdfs:label "TN for A Dog Left Behind" ;
 33    pcdm:memberOf :sample-rfta-artist-compound-object ;
 34    pcdm:hasFile :sample-rfta-artist-compound-object-file-tn .
 35
 36:sample-rfta-artist-compound-object-file-tn a pcdmff:Document ;
 37    rdfs:label "Representative Thumbnail for A Dog Left Behind" ;
 38    pcdm:fileOf :sample-rfta-artist-compound-tn ;
 39    fedora:hasVersions :path-to-the-actual-cached-tn .
 40
 41:rftaartists_3 a pcdmworks:Work ;
 42    dcterms:title "A Dog Left Behind" ;
 43    identifiers:local "rftaart:3", "RFTA_Braddock_003" ;
 44    pcdm:hasMember :rftaartists_3-original-mods, :rftaartists_3-images .
 45
 46:rftaartists_3-original-mods a pcdmworks:Fileset ;
 47    rdfs:label "MODS from Islandora - Fileset" ;
 48    pcdm:memberOf :rftaartists_3 ;
 49    pcdm:hasFile :og_mods_for_rftaartists_3 .
 50
 51:og_mods_for_rftaartists_3 a pcdmff:Markup ;
 52    rdfs:label "MODS XML from Islandora" ;
 53    pcdm:fileOf :rftaartists_3-original-mods ;
 54    fedora:hasVersions :path-to-the-actual-mods-for_rftaartists_3 .
 55
 56:rftaartists_3-images a pcdmworks:Fileset ;
 57    rdfs:label "Images for A Dog Left Behind" ;
 58    pcdm:memberOf :rftaartists_3 ;
 59    pcdm:hasFile :rftaartists_3-intermediate, :rftaartists_3-preservation .
 60
 61:rftaartists_3-intermediate a pcdmuse:IntermediateFile, pcdmff:Image ;
 62    rdfs:label "Intermediate File for A Dog Left Behind" ;
 63    pcdm:fileOf :rftaartists_3 ;
 64    fedora:hasVersions :path-to-the-intermediate-file-for-rftaartists_3 .
 65
 66:rftaartists_3-preservation a pcdmuse:PreservationFile, pcdmff:Image ;
 67    rdfs:label "Preservation File for A Dog Left Behind" ;
 68    pcdm:fileOf :rftaartists_3 ;
 69    fedora:hasVersions :path-to-the-preservation-file-for-rftaartists_3 .
 70
 71:rftaartists_53 a pcdmworks:Work ;
 72    dcterms:title "Bring Me the Animals" ;
 73    identifiers:local "rftaart:53" ;
 74    pcdm:hasMember :rftaartists_53-original-mods, :rftaartists_53-videos, :rftaartists_53-transcripts, :rftaartists_53-curated-tn .
 75
 76:rftaartists_53-original-mods a pcdmworks:Fileset ;
 77    rdfs:label "MODS from Islandora - Fileset" ;
 78    pcdm:memberOf :rftaartists_53 ;
 79    pcdm:hasFile :og_mods_for_rftaartists_53 .
 80
 81:og_mods_for_rftaartists_53 a pcdmff:Markup ;
 82    rdfs:label "MODS XML from Islandora" ;
 83    pcdm:fileOf :rftaartists_53-original-mods ;
 84    fedora:hasVersions :path-to-the-actual-mods-for_rftaartists_53 .
 85
 86:rftaartists_53-videos a pcdmworks:Fileset ;
 87    rdfs:label "Videos for Bring Me the Animals" ;
 88    pcdm:memberOf :rftaartists_53 ;
 89    pcdm:hasFile :rftaartists_53-intermediate, :rftaartists_53-preservation .
 90
 91:rftaartists_53-intermediate a pcdmuse:IntermediateFile, pcdmff:Video ;
 92    rdfs:label "Intermediate File for Bring Me the Animals" ;
 93    pcdm:fileOf :rftaartists_53 ;
 94    fedora:hasVersions :path-to-the-intermediate-file-for-rftaartists_53 .
 95
 96:rftaartists_53-preservation a pcdmuse:PreservationFile, pcdmff:Video ;
 97    rdfs:label "Preservation File for Bring Me the Animals" ;
 98    pcdm:fileOf :rftaartists_53 ;
 99    fedora:hasVersions :path-to-the-preservation-file-for-rftaartists_53 .
100
101:rftaartists_53-transcripts a pcdmworks:Fileset ;
102    rdfs:label "Captions and Subtitles for Bring Me the Animals" ;
103    pcdm:memberOf :rftaartists_53 ;
104    pcdm:hasFile :rftaartists_53-transcript-en  .
105
106:rftaartists_53-transcript-en a pcdmuse:Transcript ;
107    rdfs:label "English Caption Files of Bring Me the Animals" ;
108    pcdm:fileOf :rftaartists_53-transcripts ;
109    fedora:hasVersions :path-to-the-actual-english-transcript .
110
111:rftaartists_53-curated-TN a pcdmworks:Fileset ;
112    rdfs:label "Curated Thumbnail for Bring Me the Animals" ;
113    pcdm:memberOf :rftaartists_53 ;
114    pcdm:hasFile :rftaartists_53-curated-tn  .
115
116:rftaartists_53-curated-tn a pcdmuse:ThumbnailImage ;
117    rdfs:label "Curated TN for Bring Me the Animals" ;
118    pcdm:fileOf :rftaartists_53-curated-tn ;
119    fedora:hasVersions :path-to-the-actual-curated-tn .
120
121:proxy-for-sample-rfta-artist-compound-object-part1 a ore:Proxy ;
122    iana:next :proxy-for-sample-rfta-artist-compound-object-part2 ;
123    ore:proxyIn :sample-rfta-artist-compound-object ;
124    ore:proxyFor :rftaartists_3 .
125
126:proxy-for-sample-rfta-artist-compound-object-part2 a ore:Proxy ;
127    iana:prev :proxy-for-sample-rfta-artist-compound-object-part1 ;
128    ore:proxyIn :sample-rfta-artist-compound-object ;
129    ore:proxyFor :rftaartists_53 .
130
131:sample-collection-for-rfta-curated-art a pcdm:Collection ;
132    dcterms:title "Rising from the Ashes: The Chimney Tops 2 Wildfires in Memory and Art" ;
133    pcdm:hasMember :sample-rfta-artist-compound-object .
134
135:sample-collection-for-all-rftaart a pcdm:Collection ;
136    dcterms:title "All RFTA Artists Art" ;
137    pcdm:hasMember :rftaartists_3, :rftaartists_53 .

Technical Properties

Technical properties are identified and listed in our metadata application profile in the files tab.

Viewing Experience

IIIF Viewer

Compound object works should be displayed in a IIIF viewer such as Universal Viewer, Clover IIIF, or Mirador with an individuals behavior at the manifest level. The IIIF viewer should provide pan and zoom from the embedded OpenSeaDragon viewer on image subworks and closed captioning on audio / video sub works. Our current IIIF configuration along with “viewing experience” for compound objects is described in our Compound Objects recipe document.

The pcdmuse:IntermediateFile should always be represented in the viewer with any corresponding files (Transcripts).

A compound object with mixed media should look like this:

An Example of a Compound Object in Clover
An Example of a Compound Object in UV
An Example of a Compound Object in Mirador

Location-based Viewing

Our metadata currently includes cartographic and coordinate information so that the metadata record can be easily intermixed with a location-based viewer. An item should not be playable from this view, but it should pop out into a new window. We also include a URI that points at a Geonames object that includes this same information.

If needed, we can continue to store cartographic and coordinate information in a separate field to make this easy.

Some sample location-based display might be:

Location-based Example 1
Location-based Example 2
Location-based Example 3
Location-based Example 4

If possible, we would also like our location information to be shared as a navPlace extension in our IIIF manifests.

Rights Viewing

While we store our rights as uris (see metadata application profile), we’d like these statements to be actionable and render the appropriate badge and usage information to the user in both the IIIF viewer (when metadata is on) and in our metadata display below.

Example of Compound Rights

File Viewer

Users should be able to easily download the primary filesets.

If a fileset is only a pcdm:PreservationFile it should never be publicly visible.

File Download Example

Interoperability

OAI-PMH

Like other work types, compound works should be represented by an OAI-PMH record based on its metadata application profile. The work should be a record in an OAI set for each corresponding collection to which the work belongs. Unlike other work types, members of compound objects should also be represented in collections in which they have a pcdm:memberOf relationship. Our metadata application profile should have a rule that states which field values should be transformed to OAI-PMH for a given metadata format (simple dublin core, qualified DublinCore, DPLA?)

IIIF Image

All images that are members of a fileset related to a compound object work should be served by a IIIF image service that adheres to at least IIIF Image API 2.1.1 that supports most features described in 5.3 profile description. As part of work type negotiation, we would like to know any features that the IIIF Image service does not support.

IIIF Presentation v3

All compound object works should have a corresponding IIIF presentation v3 manifest that allows the object to be shared and remixed in other projects. For our current system, we have a description of our current presentation 3 mapping in the corresponding recipe.

Bulkrax

Import

Like all work types, images should be importable according to our Metadata Application Profile via Bulkrax import using CSV and XXXXXXX file storage solution.

Export

In addition to import functionality, images should have a variety of export options including the ability to export only filesets related to preservation for easy transfer to Chronopolis. Those filesets should include:

  • RDF about the pcdmworks:Work

  • RDF about the ore:Proxy

Note: all compound parts should be exportable via their own objects.

Restrictions

Like other work types, video works may have restrictions at the work and fileset / file level.