Newspaper Work

About

Newspaper works are perhaps our most complex worktype. Unlike books and compound objects, newspapers have a hierarchical structure that starts with a title, breaks down into volumes, and further down into issues. The date of publication and access to OCR data via METS / ALTO are critical to the viewing experience.

For newspaper works, the title, volume, and issue should all be represented as an ore:Aggregation. While we believe it is reasonable to treat both titles and volumes as pcdm:Collection s, our research shows that experts believe these should be pcdmworks:Work s or pcdm:Object s. We are open to either and feel we should do what is easiest. An issue should be a pcdmworks:Work and pages within the issue should be pcdm:Object s. The METS file should be associated with the issue and the ALTO files should be associated with the page. Since pages have a specific order, they should be represented by ore:Proxy s.

For IIIF, The title and volume should be represented by a IIIF collection. The issue should be a manifest with each page serving as a canvas. The IIIF cookbook suggests that Alto should be represented by a seeAlso property on the ‘ canvas. It also suggests the content of the METS / ALTO should be represented by a list of annotations in the annotations property on each canvas with targets to the specific regions on the canvas and a motivation of supplementing.

Any files in a fileset that are not admin only or restricted should be available for download.

All files / 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_newspaper_collection a pcdm:Collection ;
15        dcterms:title "Student Newspapers" ;
16        pcdm:hasMember :sample_newspaper_title .
17
18:sample_newspaper_title a pcdmworks:Work ;
19        dcterms:title "Daily Beacon" ;
20        pcdm:hasMember :sample_newspaper_volume .
21
22:sample_newspaper_volume a pcdmworks:Work ;
23        dcterms:title "Daily Beacon: Volume 1" ;
24        pcdm:hasMember :sample_newspaper_issue .
25
26:sample_newspaper_issue a pcdmworks:Work ;
27        dcterms:title "Daily Beacon: Volume 1, Issue 1" ;
28        pcdm:hasMember :sample_newspaper_page_1, :sample_newspaper_page_2 ;
29        pcdm:hasFile :sample_newspaper_issue_mets .
30
31:sample_newspaper_issue_mets a pcdmff:Markup ;
32        rdfs:label "METS" ;
33        fedora:hasVersions :path-to-mets .
34
35:sample_newspaper_page_1 a pcdm:Object ;
36        rdfs:label "Daily Beacon: Volume, 1, Issue 1 - page 1" ;
37        pcdm:hasMember :sample_newspaper_page_1_fileset .
38
39:sample_newspaper_page_2 a pcdm:Object ;
40        rdfs:label "Daily Beacon: Volume, 1, Issue 1 - page 1" ;
41        pcdm:hasMember :sample_newspaper_page_2_fileset .
42
43:sample_newspaper_page_1_fileset a pcdmworks:Fileset ;
44        rdfs:label "Images and Derivatives" ;
45        pcdm:hasFile :sample_newspaper_page_1_intermediate, :sample_newspaper_page_1_preservation, :sample_newspaper_page_1_alto .
46
47:sample_newspaper_page_1_intermediate a pcdmuse:IntermediateFile, pcdmff:Image ;
48        rdfs:label "Intermediate File for Daily Beacon: Volume, 1, Issue 1 - page 1" ;
49        fedora:hasVersions :path-to-sample_newspaper_page_1_intermediate .
50
51:sample_newspaper_page_1_preservation a pcdmuse:PreservationFile, pcdmff:Image ;
52        rdfs:label "Preservation File for Daily Beacon: Volume, 1, Issue 1 - page 1" ;
53        fedora:hasVersions :path-to-sample_newspaper_page_1_preservation .
54
55:sample_newspaper_page_1_alto a pcdmuse:ExtractedText ;
56        rdfs:label "Alto XML for Daily Beacon: Volume, 1, Issue 1 - page 1" ;
57        fedora:hasVersions :path-to-sample_newspaper_page_1_intermediate .
58
59:sample_newspaper_page_2_fileset a pcdmworks:Fileset ;
60        rdfs:label "Images and Derivatives" ;
61        pcdm:hasFile :sample_newspaper_page_2_intermediate, :sample_newspaper_page_2_preservation, :sample_newspaper_page_2_alto .
62
63:sample_newspaper_page_2_intermediate a pcdmuse:IntermediateFile, pcdmff:Image ;
64        rdfs:label "Intermediate File for Daily Beacon: Volume, 1, Issue 1 - page 2" ;
65        fedora:hasVersions :path-to-sample_newspaper_page_2_intermediate .
66
67:sample_newspaper_page_2_preservation a pcdmuse:PreservationFile, pcdmff:Image ;
68        rdfs:label "Preservation File for Daily Beacon: Volume, 1, Issue 1 - page 2" ;
69        fedora:hasVersions :path-to-sample_newspaper_page_2_preservation .
70
71:sample_newspaper_page_2_alto a pcdmuse:ExtractedText ;
72        rdfs:label "Alto XML for Daily Beacon: Volume, 1, Issue 1 - page 2" ;
73        fedora:hasVersions :path-to-sample_newspaper_page_2_intermediate .
74
75:proxy-for-sample_newspaper_page_1 a ore:Proxy ;
76    iana:next :proxy-for-sample_newspaper_page_2 ;
77    ore:proxyIn :sample_newspaper_issue ;
78    ore:proxyFor :sample_newspaper_page2 .
79
80:proxy-for-sample_newspaper_page_2 a ore:Proxy ;
81    iana:prev :proxy-for-sample_newspaper_page_1 ;
82    ore:proxyIn :sample_newspaper_issue ;
83    ore:proxyFor :sample_newspaper_page2 .

Technical Properties

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

Viewing Experience

IIIF Viewer

All newspaper issues should be displayed in a IIIF viewer like Universal Viewer with a behavior of paged on the manifest. The viewer should provide pan and zoom and ideally annotations on the correct portion of the canvas derived from the METS / ALTO.

One of the important features of Newspapers is the publication date which can allow the user to navigate issues by the date they were published. To achieve this, the navDate property should be added both to the items in a collection and also in the issue manifest. This allows viewers to present date-based navigation for Newspaper collections.

The pcdmuse:IntermediateFile should always be represented in the viewer.

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.

Interoperability

OAI-PMH

Like other work types, newspaper issues should be represented by an OAI-PMH record based on our metadata application profile. The work should be a record in an OAI set for each corresponding collection to which the work belongs. The title and volume should both be an OAI-PMH set with records for each issue.

Page works should not be represented by an OAI-PMH record.

IIIF Image

All pages 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 newspapers should have a corresponding IIIF presentation v3 manifest that allows the object to be shared and remixed in other projects. This includes title, volume, and issue.

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 be:

  • pcdmuse:PreservationFile

Analytics

Restrictions

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

For UTK Only

Migration Notes