-
Notifications
You must be signed in to change notification settings - Fork 0
/
newspaper-model.html
103 lines (102 loc) · 6.51 KB
/
newspaper-model.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
<title>IIIF Newspaper Model</title>
</head>
<body>
<h1>IIIF Newspaper Model</h1>
<p>This model was designed by the <a href="http://iiif.io/community/groups/newspapers/">IIIF newspapers community group</a>. This document describes the current thinking on modeling Newspapers in IIIF. This model was discussed and documented in the first <a href="http://bit.ly/iiif_ghent_newspaperig">newspaper interest group meeting in Ghent</a>. <em>The goal is not to create yet another newspaper model but to find where there may be issues of differences of definition that will cause problems with interoperability and IIIF.</em></p>
<p>For a description of the IIIF classes please see the Presentation API (http://iiif.io/api/presentation). The minimum set of levels for a IIIF Newspaper is Collection, Issue and Page.</p>
<h2>Newspaper Structure to IIIF</h2>
<table width="200" border="1" cellspacing="2" cellpadding="2" summary="Elements of newpsaper structure mapped to IIIF with notes.">
<caption>
IIIF model and newspaper structure
</caption>
<tbody>
<tr>
<th scope="col">Newspaper Level</th>
<th scope="col">IIIF</th>
<th scope="col">Notes</th>
</tr>
<tr>
<td><a href="#summarytitle">Summary Title / Collection Title / Curated Title / Collection</a></td>
<td>Collection</td>
<td>Locally defined for user access and to address title changes per serials cataloging</td>
</tr>
<tr>
<td><a href="#title">Title</a></td>
<td>Collection</td>
<td>Usually the masthead title</td>
</tr>
<tr>
<td><a href="#volume">Volume</a></td>
<td>Collection</td>
<td>Locally defined as necessary; often more useful for provenance than user interaction and presentation</td>
</tr>
<tr>
<td><a href="#issue">Issue</a></td>
<td>Manifest</td>
<td><strong>navDate</strong> recommended for presentation browsing experience</td>
</tr>
<tr>
<td><a href="#edition">Edition</a></td>
<td>Manifest</td>
<td><strong>navDate</strong> recommended for presentation browsing experience</td>
</tr>
<tr>
<td><a href="#section">Section</a></td>
<td>Range</td>
<td> </td>
</tr>
<tr>
<td><a href="#page">Page</a></td>
<td>Canvas</td>
<td> </td>
</tr>
<tr>
<td><a href="#pagetext">Page Text</a> (OCR)</td>
<td>Annotation List</td>
<td>See: <a href="https://www.w3.org/TR/annotation-model/">W3C Web Annotations</a></td>
</tr>
<tr>
<td><a href="#articles">Article</a></td>
<td>Range</td>
<td> </td>
</tr>
<tr>
<td><a href="#articles">Illustration</a></td>
<td>Range</td>
<td> </td>
</tr>
<tr>
<td><a href="#supplements">Supplement</a></td>
<td>Manifest or Range</td>
<td>Locally defined</td>
</tr>
</tbody>
</table>
<a name="summarytitle" /><h3>Summary Title / Collection Title / Curated Title / Collection</h3>
<p>Local aggregation often used to group like titles for user access and avoid the trappings of succeeding, preceding, and title variants in serials cataloging that can make using digital newspapers disorienting.<br /> Note: not equivalent to a Uniform Title.</p>
<a name="title" /><h3>Title</h3>
<p>A collection of Newspaper issues that are grouped together to form a single publication. Newspapers can change names and publishers but this grouping would link issues into a single publication. Traditionally linked to the $245 in a MARC catalog record.</p>
<a name="volume" /><h3>Volume</h3>
<p>A collection of issues which are gathered together, typically in physical form. This historically has been used for issues that are published in a particular year. Note date based volumes like collections of issues published in a year could be created by a viewer using the <strong>NavDate</strong> for an issue, so a volume designation may not be necessary or only serve provenance purposes.
<br />Note: incorrect volumes may or may not be corrected in metadata. </p>
<a name="issue" /><h3>Issue</h3>
<p>The collection of pages that were published at a particular issuance. Multiple issues of the same Newspaper can be published on the same date. Note: incorrect issues may or may not be corrected in metadata. Some implementations may treat supplements as issues published on the same date as the issue it is associated with.</p>
<a name="edition" /><h3>Edition</h3>
<p>The textual label of the edition on the piece. Editions vary widely by newspaper and region and may include examples such as: "Late Edition," "Morning Edition," "Special Edition," "Weekend Early
<a name="section" /><h3>Section</h3>
<p>A section within a Newspaper Issue for example sports section or supplement included in the Edition," "East Side", and "West Side." Use the <strong>NavDate</strong> for presentation flow and edition order (e.g. from morning to late editions).</p> Newspaper. </p>
<a name="page" /><h3>Page</h3>
<p>A page, insert, foldout or other "piece" of a Newspaper that is digitized as a single image. "Pages" may link to "Page text" or other annotations. </p>
<a name="pagetext" /><h3>Page text</h3>
<p>The text contained within a page usually generated by running optical character recognition software on a newspaper image. This can have coordinates associated with the text to allow a bounding box to be placed on the image where the text appears. Page text can be available at multiple granularities including article, paragraph, line, word and character. The page text may be provided as an Annotation list, or as <strong>seeAlso</strong> link to an ALTO file. Examples are provided below.</p>
<p>The IIIF Text Granularity Working Group is investigating options for consensus on different levels of text for the same annotation.</p>
<h3>Articles and Illustrations</h3>
<a name="articles" /><p>A collection of text areas on a page that are related. Examples include News article, advertising, family notices, cartoons etc. In the current model articles can cross pages but not issues. Articles have text and coordinates which highlight the areas of a page which relate to an article. Articles can have metadata like title, author or type. </p>
<a name="supplements" /><h3>Supplements</h3>
<p>Supplements come in a variety of forms for newspapers. Local practice and a particular instance will determine if supplements should be treated as their own issue and a manifest or a range within an issue.</p>
</body>
</html>