Video Work
About
Video works are works where the primary fileset is derived from a video file. The file should be served to a IIIF viewer on the Work page by a IIIF Presentation 3 manifest.
The video work MAY have a pcdmuse:IntermediateFile and a pcdmuse:PreservationFile that represents the
video. In the case that there is only one file, the primary fileset should have a file that is both a
pcdmuse:IntermediateFile and a pcdmuse:PreservationFile. That way, the pcdmuse:IntermediateFile
will always be served to the viewer on the work page. In the case where there are 2 separate files, the one with a type
of pcdmuse:IntermediateFile has had additional processing done to it beyond what would happen through standard
programmatic derivative generation and thus MAY need to live in its own fileset. The representative thumbnail should
always be derived from the file with a rdf:type of pcdmuse:IntermediateFile. In the case that there is
only one fileset, that fileset should have a file with two rdf:types: pcdmuse:PreservationFile and
pcdmuse:IntermediateFile. The pcdmuse:IntermediateFile should always served to the viewer on the work page.
Video works should have caption or transcript files and may have them in multiple languages.
Video works may have hierarchical structure described by metadata properties that should be converted into IIIF Presentation v3 structures and ranges.
A video work may have other filesets of any mime type available to the user for download.
All filesets may have restrictions that prohibit view / access.
Metadata Properties
Descriptive Properties
Descriptive properties are described in our vendor supplied MAP.
Structural Properties
The suggested structure of an video work is described below.
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 ebucore: <http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#> .
5@prefix fedora: <http://fedora.info/definitions/v4/repository#> .
6@prefix identifiers: <http://id.loc.gov/vocabulary/identifiers/> .
7@prefix pcdm: <http://pcdm.org/models#> .
8@prefix pcdmff: <http://pcdm.org/file-format-types#> .
9@prefix pcdmuse: <http://pcdm.org/use#> .
10@prefix pcdmworks: <http://pcdm.org/works#> .
11@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
12
13:sample-video a pcdmworks:Work ;
14 dcterms:title "Interview with Julia Rodriguez, 2021-03-03" ;
15 identifiers:local "2021_03_03_Rodriguez_Julia", "rfta:165" ;
16 pcdm:hasMember :sample-video-original-mods, :sample-video-fileset, :sample-video-release, :sample-video-transcript .
17
18:sample-video-original-mods a pcdmworks:Fileset ;
19 rdfs:label "MODS from Islandora - Fileset" ;
20 pcdm:memberOf :sample-video ;
21 pcdm:hasFile :sample-file-mods-xml .
22
23:sample-file-mods-xml a pcdmff:Markup ;
24 rdfs:label "MODS" ;
25 pcdm:fileOf :sample-video-original-mods ;
26 fedora:hasVersions :path-to-the-actual-mods .
27
28:sample-video-fileset a pcdmworks:Fileset ;
29 rdfs:label "Video Files" ;
30 pcdm:memberOf :sample-video ;
31 pcdm:hasFile :sample-file-intermediate, :sample-file-preservation .
32
33:sample-file-preservation a pcdmuse:PreservationFile, pcdmff:Video ;
34 rdfs:label "Preservation File for Interview with Julia Rodriguez, 2021-03-03" ;
35 pcdm:fileOf :sample-audio-fileset ;
36 bibframe:duration 2836.032 ;
37 ebucore:width 1920;
38 ebucore:height 1080;
39 fedora:hasVersions :path-to-the-preservation-file-for-sample-file-preservation .
40
41:sample-file-intermediate a pcdmuse:IntermediateFile, pcdmff:Video ;
42 rdfs:label "Intermediate File for Interview with Julia Rodriguez, 2021-03-03" ;
43 pcdm:fileOf :sample-audio-fileset ;
44 bibframe:duration 2851.691 ;
45 ebucore:width 1920;
46 ebucore:height 1080;
47 fedora:hasVersions :path-to-the-intermediate-file-for-sample-file-intermediate .
48
49:sample-video-release a pcdmworks:Fileset ;
50 rdfs:label "Release File" ;
51 pcdm:memberOf :sample-video ;
52 pcdm:hasFile :sample-release-file .
53
54:sample-release-file a pcdmff:Document ;
55 rdfs:label "Release File" ;
56 pcdm:fileOf :sample-video-release ;
57 fedora:hasVersions :path-to-the-actual-release-file .
58
59:sample-video-transcript a pcdmworks:Fileset ;
60 rdfs:label "Transcripts for Interview with Julia Rodriguez, 2021-03-03" ;
61 pcdm:memberOf :sample-video ;
62 pcdm:hasFile :sample-english-transcript, :sample-spanish-transcript .
63
64:sample-english-transcript a pcdmuse:Transcript ;
65 rdfs:label "English Web/VTT Interview with Julia Rodriguez, 2021-03-03" ;
66 pcdm:fileOf :sample-video-transcript ;
67 dcterms:language "en" ;
68 fedora:hasVersions :path-to-the-actual-transcript .
69
70:sample-spanish-transcript a pcdmuse:Transcript ;
71 rdfs:label "Spanish Web/VTT Interview with Julia Rodriguez, 2021-03-03" ;
72 pcdm:fileOf :sample-video-transcript ;
73 dcterms:language "es" ;
74 fedora:hasVersions :path-to-the-actual-spanish-transcript .
Technical Properties
Technical properties are identified and listed in our metadata application profile in the files tab.
Viewing Experience
IIIF Viewer
Video works should be rendered to the user in a IIIF presentation viewer like IIIF React Media Player, Universal Viewer, Clover IIIF, or Mirador. Our current IIIF configuration along with “viewing experience” for images is described in our Video IIIF Recipe document.
In the case where a Video work has a pcdmuse:PreservationFile and pcdmuse:IntermediateFile file, the
pcdmuse:IntermediateFile should be displayed in the viewer to users by default on the work page. A work may have both
types of files when the intermediate is not derived programmatically from the preservation file.
While we expect to use a IIIF viewer for display, it is important to note that we have closed captioning files and
structural metadata that should be transformed into IIIF structures and ranges. Currently, we use our own internal viewer
for displaying this, but we should adopt a community viewer. As of the time of this writing, only the
IIIF React Media Player supports this as part of its
<StructuredNavigation /> component. To keep things simple, we are okay with using this viewer for all audio and
video works. A sample of this viewer can be seen here and below:
Our current viewer with structures and ranges can be seen here:
In addition to structures and ranges, most of our audio and video works have caption files and transcripts in 1 or more
languages. It is critical that the viewer display our different caption files and that these are stored in the
corresponding IIIF manifest as an annotation with a motivation of supplementing in the annotations property in
line with the IIIF presentation v3 specification and W3C Web Annotations specification. If helpful, see our Video IIIF
Recipe documentation for how this should be implemented.
Minimally, the caption file should be displayed as captions but may also be present as a navigable transcript like in Clover IIIF:
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:
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.
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.
Interoperability
OAI-PMH
Like other work types, video works should be represented by an OAI-PMH record based on its metadata application profile. The work should be a record of an OAI set for each corresponding collection to which the object belongs. Our metadata application profile should have a rule that states which field values should be remixed to OAI-PMH for a given metadata format (simple dublin core, dcterms).
IIIF Presentation v3
All video 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.
For video works, our expectations are that structures and ranges be stored in the structures property with accompanying ranges that target the video canvas. Also, all caption files should be annotations in the annotations property with the motivation of supplementing.
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:
pcdmuse:PreservationFilepcdmff:Documentpcdmuse:Transcript
Restrictions
Like other work types, video works may have restrictions at the work and fileset / file level.