-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathUCBPagedTextObject.profile.xml
333 lines (333 loc) · 23.9 KB
/
UCBPagedTextObject.profile.xml
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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com) by Richard Beaubien (Univ. of California, Berkeley) -->
<METS_Profile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.loc.gov/standards/mets/profile_docs/mets.profile.v1-0.xsd">
<URI LOCTYPE="URL">http://sunsite.berkeley.edu/mets/profiles/UCBTextProfile.xml</URI>
<title>UCB Paged Text Profile</title>
<abstract>This profile represents a specific subset of the Model Paged Text Object Profile. UC Berkeley Library METS objects with associated text content files, or with both image content files and text content files implement this profile. </abstract>
<date>2004-04-27T08:00:00</date>
<contact>
<name>Rick Beaubien</name>
<address>Library Systems Office, Rm. 386 Doe Library, University of California, Berkeley, CA 94720-6000
</address>
<phone>(510) 643-9776</phone>
<email>[email protected]</email>
</contact>
<related_profile RELATIONSHIP="subset of" URI="http://sunsite.berkeley.edu/mets/profiles/ModelTextProfile.xml">Model Paged Text Object Profile
</related_profile>
<extension_schema>
<name>MODS</name>
<URI>http://www.loc.gov/standards/mods/v3/mods-3-0.xsd</URI>
<context>mets/dmdSec/mdWrap/xmlData</context>
</extension_schema>
<extension_schema>
<name>NISOIMG</name>
<URI>http://www.loc.gov/standards/mix/mix.xsd</URI>
<context>mets/amdSec/techMD/mdWrap/xmlData</context>
<note>Used for technical metadata about image content files.</note>
</extension_schema>
<extension_schema>
<name>textmd</name>
<URI>http://dlib.nyu.edu/METS/textmd.xsd</URI>
<context>mets/amdSec/techMD/mdWrap/xmlData</context>
<note>Used for technical metadata about text content files.</note>
</extension_schema>
<extension_schema>
<name>METSRights</name>
<URI>http://www.loc.gov/standards/rights/METSRights.xsd</URI>
<context>mets/amdSec/rightsMD/mdWrap/xmlData</context>
</extension_schema>
<description_rules>
<p>All applications of the MODS schema in conforming METS documents follow the MODS User Guidelines published by Library of Congress' Network Development and MARC Standards Office.</p>
</description_rules>
<controlled_vocabularies>
<vocabulary>
<name>Model Paged Text object Profile <file> USE attribute values</name>
<maintenance_agency>Library Systems Office, The General Library, University of California, Berkeley</maintenance_agency>
<values>
<value>archive image</value>
<value>reference image</value>
<value>thumbnail image</value>
<value>tei transcription</value>
<value>tei translation</value>
<value>ocr</value>
<value>ocr dirty</value>
</values>
<context ID="vc1" RELATEDMAT="fileSec2">
<p>mets/fileSec/fileGrp/@USE</p>
<p>mets/fileSec/fileGrp/file/@USE</p>
</context>
<description>
<p>These are the supported values for <file> and <fileGrp> USE attributes in paged text objects conforming to this profile.</p>
<p>"archive image", "reference image" and "thumbnail image" are appropriate values to describe the USE of image content files. "archive image" designates image masters; "thumbnail image" image thumbnails; and "reference image" any intermediate resolutions intended for reference purposes.</p>
<p>"tei transcription" and "tei translation" are appropriate values to describe associated structured text files encoded according to TEI rules;"tei transcription" designates direct TEI transcriptions of text based materials; "tei translation" designates TEI translations of these materials from their original language.</p>
<p>"ocr" and "ocr dirty" should be used to designate versions of the text produced by ocr technologies. "ocr dirty" would be used to distinguish ocr text that is not suitable for presentation to the user from clean "ocr".</p>
</description>
</vocabulary>
<vocabulary>
<name>Model Paged Text Object <structMap> TYPE attribute values</name>
<maintenance_agency>Library Systems Office, The General Library, University of California, Berkeley</maintenance_agency>
<values>
<value>physical</value>
<value>logical</value>
<value>mixed</value>
</values>
<context ID="vc2" RELATEDMAT="structMap2">
<p>mets/structMap/@TYPE</p>
</context>
<description>
<p>These are the supported values for the <structMap> TYPE attribute in METS documents conforming to this profile.</p>
<p>"physical" designates a purely physical structure. For example, a book divided into page views.</p>
<p>"logical" designates a purely logical structure. For example, a book divided into chapters; or a diary divided into diary entries.</p>
<p>"mixed" designates a mixed structure. For example, a book divided into chapters, divided into page views.</p>
</description>
</vocabulary>
</controlled_vocabularies>
<structural_requirements>
<metsHdr>
<requirement ID="metsHdr1">
<p>Conforming METS documents must contain a metsHdr element.</p>
</requirement>
<requirement ID="metsHdr2">
<p><metsHdr> element must include the CREATEDATE attribute value. It must also include the LASTMODDATE attribute value if this does not coincide with the CREATEDATE</p>
</requirement>
<requirement>
<p><metsHdr> element must include a child <agent> element identifying the person or institution responsible for creating the METS object.</p>
</requirement>
</metsHdr>
<dmdSec>
<requirement ID="dmdSec1">
<p>Conforming METS documents may, but need not, contain a one or more <dmdSec> elements. Each <dmdSec> may in turn contain a <dmdRef> or a <dmdWrap></p>
</requirement>
<requirement ID="dmdSec2">
<p>If a <dmdSec> of a conforming document contains a <dmdWrap> with <xmlData>, the <xmlData> must conform to the MODS schema.</p>
</requirement>
</dmdSec>
<amdSec>
<requirement ID="amdSec1">
<p>Conforming METS documents may but need not contain an <amdSec> element. This <amdSec> may but need not contain one or more <techMD> elements, <sourceMD> elements, <rightsMD> elements and/or <provenanceMD> elements. </p>
</requirement>
<requirement ID="amdSec2">
<p>If one or more <techMD> elements pertaining to image content files are present, they must contain <xmlData> of NISOIMG type conforming to the MIX schema.</p>
</requirement>
<requirement ID="amdSec3">
<p>If one or more <techMD> elements pertaining to text content files are present, they must contain <xmlData> conforming to the textmd schema.</p>
</requirement>
<requirement ID="amdSec4">
<p>If one or more <rightsMD> elements are present, they must contain <xmlData> conforming to the METSRights schema.</p>
</requirement>
<requirement ID="amdSec5">
<p>Any <sourceMD> or <provenanceMD> elements should contain <xmlData> conforming to a METS Editorial Board endorsed schema whenever such a schema exists and covers the requisite concepts.</p>
</requirement>
<requirement ID="amdSec6">
<p>Source metadata pertaining to image content files may be expressed as part of any MIX encoded technical metadata in <techMD> elements rather than in separate <sourceMD> elements. This might occur whenever the available source metadata is minimal and covered by the MIX schema.</p>
</requirement>
</amdSec>
<fileSec>
<requirement ID="fileSec1">
<p>The <fileSec> of a conforming METS document must contain a parent <fileGrp> for each file format/use represented by the content files. For example, the <fileSec> of a typical METS document implementing this profile might contain one <fileGrp> representing TIFF master images, one <fileGrp> representing high resolution JPEG reference images , one <fileGrp> representing medium resolution JPEG reference images, one <fileGrp> representing GIF thumbnail images, and one <fileGrp> representing TEI transcriptions. Each of these <fileGrp> elements may or may not contain subsidiary <fileGrp> elements representing subgroups of the content files.</p>
</requirement>
<requirement ID="fileSec2" RELATEDMAT="vc1">
<p>Each <file> represented in the <fileSec> must have an associated USE attribute. The USE attribute may, however, be expressed at the <fileGrp> level, in which case it is taken to pertain to all <file> elements in the <fileGrp>. It may also, of course, be expressed at the <file> element level. Supported <file>/<fileGrp> USE attribute values appear in the <controlled_vocabularies> section of this document.</p>
</requirement>
<requirement ID="fileSec3">
<p>Any <file> element may reference any number of pertinent top level adminstrative metadata elements within the <amdSec> via its AMDID attribute value. It should only reference ID values at the <techMD>, <rightsMD>, <sourceMD> and/or <digiprovMD> levels of the <amdSec> </p>
</requirement>
</fileSec>
<structMap>
<requirement ID="structMap1">
<p>A conforming METS document must contain only one <structMap>.</p>
</requirement>
<requirement ID="structMap2" RELATEDMAT="vc2">
<p>A conforming <structMap> must contain a TYPE attribute. Supported TYPE values appear in the <controlled_vocabularies> section of this document ("logical","physical", or "mixed").</p>
</requirement>
<requirement ID="structMap3">
<p>Each <div> must include a LABEL attribute value.</p>
</requirement>
<requirement ID="structMap4">
<p>A <div> element may or may not directly contain <fptr> elements. (In other words, a <div> of the <structMap> may or may not have content files directly associated with it). But if a <div> element does not itself directly contain one or more child <fptr> elements or a child <mptr> element, a <div> element somewhere in the hierarchy below it must contain an <fptr> element (and have associated content files) or an <mptr> element, pointing to another METS object. Thus every <div> in the <structMap> of a METS document implementing this profile must have associated content; the content may, however, be referenced at a lower level of the <structMap> hierarchy. As follows from this requirement, <div> elements at the lowest level of any branch of the <structMap> hierarchy must contain one or more <fptr> elements or an <mptr> elements. In other words, <div> elements at the lowest levels must have an associated content file or files. The content, however, may be another METS document (and indicated by an <mptr> element)</p>
</requirement>
<requirement ID="structMap5">
<p>An <fptr> element must either 1) directly point to a <file> element via its FILEID attribute; or 2) contain an <area> element that points to a <file> element; or 3) contain a <seq> element comprising multiple <area>a elements that point to the relevant <file> elements. METS documents implementing this profile must not use the <par> element. <structMap>s of "physical" and "mixed" TYPEs must not use either the <par> or <seq> elements.
</p>
</requirement>
<requirement ID="structMap6">
<p>An <fptr> element could directly contain an <area> element if only a portion of an integral file manifests the parent <div>. This is likely to occur in either of two cases. 1) This would typically be the case when the parent <div> element represented just a segment of the entire document and the <fptr> represented a tei transcription or a tei translation. In this case, the <area> element under the <fptr> would point to the <file> element representing the tei document (via its FILEID attribute) and must at least indicate the starting point of the the relevant section of the referenced tei file via the <area> BEGIN attribute. The BEGIN attribute, in this case, would have a BETYPE of "IDREF". The <area> element might also express the end point of the relevant section of the referenced file via its END attribute, but it need not do so. 2) When a <structMap> represents a logical structure, its individual <div> elements may each be manifested by only a portion of the associated image content files represented by its child <fptr> elements. In this case, an <fptr> element representing an image content file could, but need not, contain a <area> element which specified the shape and coordinates of the relevant section of the image via the <area> element's SHAPE and COORDS attribute values.
</p>
</requirement>
<requirement ID="structMap7">
<p>An <fptr> element would contain a <seq> element if multiple files needed to be"played" in sequence to manifest a division. This might be the case if the <structMap> expressed a logical structure and a <div> in that structure required several files to manifest it. For example, the <div> elements in the <structMap> for a diary might represent diary entries; and some of these entries might span multiple physical pages, and hence require multiple image content files to manifest them. In this case, the <div> representing the spanned diary entry would contain at least one <fptr>element; this <fptr> element would contain a <seq> element which in turn contained a separate <area> element pointing to each <file> element representing a page the diary entry spans. The <area> elements may include SHAPE and COORDS attribute values to identify the relevant sections of the associated image files, but they need not do so.
</p>
</requirement>
<requirement ID="structMap8">
<p>Each <fptr> element that does not contain subsidiary <area> or <seq> elements must point directly to a <file> element in the <fileSec> via its FILEID attributes. Similarly, each <area> element appearing under an <fptr> element or a <seq> element must point to directly to a <file> element via its FILEID attribute.</p>
</requirement>
</structMap>
<structLink>
<requirement ID="structLink1">
<p>A conforming METS document may contain a <structLink> element. This profile, however, establishes no guidelines or expectations for its use.</p>
</requirement>
</structLink>
<behaviorSec>
<requirement ID="behaviorSec1">
<p>A conforming METS document may contain a <behaviorSec> element. This profile, however, establishes no guidelines or expectations for its use.</p>
</requirement>
</behaviorSec>
<multiSection>
<requirement ID="multi1">
<p>Only <file> elements will reference <techMD>, <sourceMD> <rightsMD> and/or <provenanceMD> elements. In other words, documents implementing this profile will express administrative metadata in conjunction with content files only rather than in conjunction with <div> elements in the <structMap>.</p>
</requirement>
<requirement ID="multi2">
<p>Only <div> elements will reference <dmdSec> elements. In other words, documents implementing this profile will express descriptive metadata in conjunction with divisions of the <structMap> and not in conjunction with individual content files (<file> elements).</p>
</requirement>
</multiSection>
</structural_requirements>
<technical_requirements>
<content_files>
<requirement>
<p>If a METS document conforming to this profile has associated image content files, the master (archive) images must be represented and of TIFF format.</p>
</requirement>
<requirement>
<p>At least one version of any image content must be of JPEG or GIF format. In other words, at least one content file format must be natively supported by typical internet browsers.</p>
</requirement>
<requirement>
<p>All "tei translation" and "tei transcription" files must be encoded according to version 1 of the "TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices" maintained by the Digital Library Federation (http://www.diglib.org/standards/tei.htm). </p>
</requirement>
</content_files>
</technical_requirements>
<tool>
<agency>California Digital Library</agency>
<URI>http://ark-dev.cdlib.org:8086/xslt/extract-dc/GenX.qdc2.xslt</URI>
<description>
<p ID="toQDC">Ths XSLT is used to extract an Dublin Core record from the object</p>
</description>
</tool>
<tool>
<agency>California Digital Library</agency>
<URI>http://ark-dev.cdlib.org:8086/xslt/bpc-mets/allMetsBPC.xsl</URI>
<description>
<p ID="generalBPC">This generic METS Best Practice Checker XSLT is from Schematron and outputs errors as XML.</p>
</description>
</tool>
<Appendix NUMBER="1">
<mets:mets xmlns:mets="http://www.loc.gov/METS/" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xlink="http://www.w3.org/TR/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/mets/mets.xsd
http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-0.xsd http://www.loc.gov/mix/ http://www.loc.gov/mix/mix.xsd" OBJID="ark:/13030/kt9s2009hz" TYPE="Text" LABEL="Dictation from Amelia Hartman Saunders : Sacramento : ms., 1887" PROFILE="UCB Paged Text Object Profile">
<mets:metsHdr CREATEDATE="2003-04-10T10:30:00">
<mets:agent ROLE="CREATOR">
<mets:name>Rick Beaubien</mets:name>
</mets:agent>
</mets:metsHdr>
<mets:dmdSec ID="DMD1">
<mets:mdWrap MDTYPE="MODS">
<mets:xmlData>
<mods:mods>
<mods:titleInfo>
<mods:title>Dictation from Amelia Hartman Saunders : ms., Sacramento : 1887</mods:title>
</mods:titleInfo>
<mods:name type="personal">
<mods:namePart>Saunders, Amelia Hartman</mods:namePart>
<mods:namePart type="date">1851-</mods:namePart>
<mods:role>
<mods:roleTerm authority="lcnaf" type="text">author</mods:roleTerm>
</mods:role>
</mods:name>
<mods:typeOfResource manuscript="yes">text</mods:typeOfResource>
<mods:genre authority="rbgenr">Autobiographies</mods:genre>
<mods:originInfo>
<mods:place>
<mods:placeTerm type="text">Sacramento, California</mods:placeTerm>
</mods:place>
<mods:dateCreated>1887</mods:dateCreated>
<mods:dateCreated encoding="w3cdtf" point="start">1887</mods:dateCreated>
</mods:originInfo>
<mods:language>
<mods:languageTerm authority="iso639-2b" type="code">eng</mods:languageTerm>
</mods:language>
<mods:physicalDescription>
<mods:extent>1 folder</mods:extent>
</mods:physicalDescription>
<mods:abstract>From miscellaneous California dictations, statements and some questionnaires concerning social life, customs, economic conditions, recorded and prepared for H.H. Bancroft primarily between 1887 and 1889.</mods:abstract>
<mods:note type="provenance">Forms part of the Hubert Howe Bancroft Collection</mods:note>
<mods:subject authority="lcsh">
<mods:geographic>California--Biography</mods:geographic>
</mods:subject>
<mods:subject>
<mods:geographic>Sacramento (Calif.)--Social life and customs</mods:geographic>
</mods:subject>
<mods:relatedItem type="host">
<mods:titleInfo>
<mods:title>Hubert Howe Bancroft Collection</mods:title>
</mods:titleInfo>
</mods:relatedItem>
<mods:relatedItem type="host">
<mods:titleInfo type="uniform">
<mods:title>Miscellaneous California dictations</mods:title>
</mods:titleInfo>
</mods:relatedItem>
<mods:identifier type="local">BANC C-D 810:386</mods:identifier>
<mods:location>
<mods:physicalLocation>The Bancroft Library. University of California, Berkeley, CA 94720-6000</mods:physicalLocation>
</mods:location>
<mods:accessCondition displayLabel="Access restrictions:">Non-circulating; may be used only in the Bancroft library</mods:accessCondition>
</mods:mods>
</mets:xmlData>
</mets:mdWrap>
</mets:dmdSec>
<mets:fileSec>
<mets:fileGrp VERSDATE="1999-06-17T00:00:00" USE="archive image">
<mets:file ID="FID1" MIMETYPE="image/tiff" SEQ="1" CREATED="1999-06-17T00:00:00" GROUPID="GID1">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/masters/bkm00002773a.tif" LOCTYPE="URL"/>
</mets:file>
<mets:file ID="FID2" MIMETYPE="image/tiff" SEQ="2" CREATED="1999-06-17T00:00:00" GROUPID="GID2">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/masters/bkm00002774a.tif" LOCTYPE="URL"/>
</mets:file>
</mets:fileGrp>
<mets:fileGrp VERSDATE="1999-06-28T00:00:00" USE="thumbnail image">
<mets:file ID="FID3" MIMETYPE="image/gif" SEQ="1" CREATED="1999-06-28T00:00:00" GROUPID="GID1">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/images/bkm00002773a_a.gif" LOCTYPE="URL"/>
</mets:file>
<mets:file ID="FID4" MIMETYPE="image/gif" SEQ="2" CREATED="1999-06-28T00:00:00" GROUPID="GID2">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/images/bkm00002774a_a.gif" LOCTYPE="URL"/>
</mets:file>
</mets:fileGrp>
<mets:fileGrp VERSDATE="1999-06-28T00:00:00" USE="reference image">
<mets:file ID="FID5" MIMETYPE="image/jpeg" SEQ="1" CREATED="1999-06-28T00:00:00" GROUPID="GID1">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/images/bkm00002773a_b.jpg" LOCTYPE="URL"/>
</mets:file>
<mets:file ID="FID6" MIMETYPE="image/jpeg" SEQ="2" CREATED="1999-06-28T00:00:00" GROUPID="GID2">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/images/bkm00002774a_b.jpg" LOCTYPE="URL"/>
</mets:file>
</mets:fileGrp>
<mets:fileGrp VERSDATE="1999-06-28T00:00:00" USE="reference image">
<mets:file ID="FID7" MIMETYPE="image/jpeg" SEQ="1" CREATED="1999-06-28T00:00:00" GROUPID="GID1">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/images/bkm00002773a_c.jpg" LOCTYPE="URL"/>
</mets:file>
<mets:file ID="FID8" MIMETYPE="image/jpeg" SEQ="2" CREATED="1999-06-28T00:00:00" GROUPID="GID2">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/images/bkm00002774a_c.jpg" LOCTYPE="URL"/>
</mets:file>
</mets:fileGrp>
<mets:fileGrp VERSDATE="1999-06-28T00:00:00" USE="tei transcription">
<mets:file ID="FID9" MIMETYPE="text/sgml" SEQ="1" CREATED="1999-06-28T00:00:00" GROUPID="GID3">
<mets:FLocat xlink:href="http://sunsite.berkeley.edu/moa2/tei/bkm00002772_a.sgml" LOCTYPE="URL"/>
</mets:file>
</mets:fileGrp>
</mets:fileSec>
<mets:structMap TYPE="physical">
<mets:div ORDER="1" TYPE="text" LABEL="Dictation from Amelia Hartman Saunders : Sacramento : ms., 1887" DMDID="DMD1">
<mets:fptr FILEID="FID9"/>
<mets:div ORDER="1" TYPE="page" LABEL=" Page [1]">
<mets:fptr FILEID="FID1"/>
<mets:fptr FILEID="FID3"/>
<mets:fptr FILEID="FID5"/>
<mets:fptr FILEID="FID7"/>
</mets:div>
<mets:div ORDER="2" TYPE="page" LABEL=" Page [2]">
<mets:fptr FILEID="FID2"/>
<mets:fptr FILEID="FID4"/>
<mets:fptr FILEID="FID6"/>
<mets:fptr FILEID="FID8"/>
</mets:div>
</mets:div>
</mets:structMap>
</mets:mets>
</Appendix>
</METS_Profile>