Extending NYPL Core Ontology for Digital Assets
The NYPL Core Ontology may be extended through the PCDM model to accommodate digital files, both born digital resources and digitized surrogates of physical resources.
Digitized surrogates may be associated with an NYPL resource (Collection, Component, or Item) through a Capture -- the physical constituent part represented by the file, for instance, a page of a book or the back of a photograph:
Born digital files may be associated with an NYPL resource (Collection, Component, or Item) directly:
A Capture is a physical constituent part of an NYPL resource (Collection, Component, or Item), such as a page of a book, the front of a postcard, or a reel of an audio recording. Captures have metadata properties that relate to the physical rather than intellectual nature and structure of a resource.
A File is a sequence of binary data. The metadata typically includes at least basic technical metadata (size, content type, modification date, etc.), but can also include properties related to preservation, digitization process, provenance, etc. Files must be contained by exactly one Collection, Component, Item, or Object.
Namespaces
dcterms | |
nypl | |
pcdm | |
skos | |
xsd |
Classes
Capture | ||
---|---|---|
Equivalent class | nypl:Capture | |
Description | A physical constituent part of an NYPL resource. | |
Refines | pcdm:Object |
File | ||
---|---|---|
Equivalent class | pcdm:File | |
Description | A sequence of binary data. | |
Refines |
Properties of Capture
DC flag | ||
---|---|---|
Equivalent property | nypl:dcflag | |
Identifier | Placeholder property whether or not a capture is available in Digital Collections. | |
Range | xsd:boolean | |
Domain | Capture |
Image ID | ||
---|---|---|
Equivalent property | dcterms:identifier | |
Identifier | The image id of the Capture | |
Range | urn:example:imageid | |
Domain | Capture |
Label | ||
---|---|---|
Equivalent property | dcterms:title | |
Description | A label for the capture. This might represent the content of the capture (ex. “Plate XI”) or the relationship of the capture to the resource as a whole (ex. “Page 4”, “Front”, “Reel 1”) | |
Range | xsd:literal | |
Domain | Capture |
Member of | ||
---|---|---|
Equivalent property | pcdm:memberOf | |
Description | Links from a core resource to a containing core resource. | |
Range | pcdm:Object, pcdm:Collection | |
Domain | Item, Component, Collection, Capture |
Sequence | ||
---|---|---|
Equivalent property | nypl:sequenceNumber | |
Description | The MMS sequence number of the capture. (We will eventually need to use ore:proxy resources to implement sequence, but for now we can store existing sequence numbers here.) | |
Range | xsd:literal | |
Domain | Capture |
UUID | ||
---|---|---|
Equivalent property | dcterms:identifier | |
Identifier | The UUID of the capture | |
Range | urn:example:uuid | |
Domain | Capture |
Properties of File
(We will add more properties, including those defined in PCDM, as the need arises)
Filename | ||
---|---|---|
Equivalent property | rdfs:label | |
Description | The repository filename of the file. | |
Range | xsd:string | |
Domain | File |
Ordering Resources
to-do