 The
Library of Congress >> Standards |
|
 |
|
 |
|
| |
|
|
|
|
METS_Profile:
@xsi:schemaLocation=" //www.loc.gov/METS_Profile/ //www.loc.gov/standards/mets/profile_docs/mets.profile.v1-2.xsd http://purl.org/dc/elements/1.1/ http://dublincore.org/schemas/xmls/qdc/2006/01/06/dc.xsd http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/2006/01/06/dcterms.xsd //www.loc.gov/METS/ //www.loc.gov/standards/mets/mets.xsd http://cosimo.stanford.edu/sdr/metsrights/ http://cosimo.stanford.edu/sdr/metsrights.xsd"
title:
CDL 7train Profile - CONTENTdm Simple and Complex Objects abstract:
The California Digital Library (CDL) - http://www.cdlib.org - has created and uses this profile to ingest and manage METS objects produced via the CONTENTdm software application (see http://contentdm.com/). CDL has designed a transformation process to produce METS instances from CONTENTdm's Standard XML export. This profile was designed to accommodate objects produced as part of the Local History Digital Resources Project, a project supported by the U.S. Institute of Museum and Library Services under the provisions of the Library Service and Technology Act (LSTA), administered by the California State Librarian. This profile may be used by other organizations that also use CONTENTdm and wish to submit objects to the CDL. The objects described by this profile are primarily imaged objects, including imaged text objects. In the case of imaged text objects, the objects may also contain associated text transcriptions, formatted as raw ASCII text. The principle goal of this documentation is to describe the salient features of the profile and how it is used for the management of objects in CDL's systems. date:
2006-05-01T13:46:00 related_profile:
No related profiles extension_schema:
name:
Qualified Dublin Core: Elements context:
Used as the primary schema for descriptive metadata in the METS:dmdSec element. extension_schema:
name:
Qualified Dublin Core: Terms context:
Used for some elements of descriptive metadata in the METS:dmdSec element. description_rules:
All applications of the Dublin Core schema in conforming METS documents follow the Guidelines for Implementing Dublin Core in XML published by the Dublin Core Metadata Initiative. controlled_vocabularies:
vocabulary:
name:
7train Profile <fileGrp> and <file> USE attribute values context:
@ID="vc1"
@RELATEDMAT="fileSec4"
mets/fileSec/fileGrp/@USE mets/fileSec/fileGrp/file/@USE Each <file> represented in the <fileSec> must have an associated USE attribute. The USE attribute may be expressed directly at the <file> element level. Alternately, however, the USE attribute may be expressed in conjunction with the <fileGrp> that is the immediate parent of a <file> element; in this case it is taken to pertain to all <file> elements in the <fileGrp>. The value must conform to the list given in the controlled vocabularies sections above.description:
These are the supported values for <file> and <fileGrp> USE attributes in METS documents conforming to this profile. "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" reduced size images or thumbnails; and "reference image" any intermediate resolutions intended for reference or display purposes. "transcription" is an appropriate value to describe text files transcribed from imaged documents. This content must be formatted as raw, unstructured ASCII text. A given segment of the source material could be represented by more than one content file of a particular USE; for example, multiple reference images of different resolutions. vocabulary:
name:
7train Profile <mets> TYPE attribute values context:
@ID="vc2"
@RELATEDMAT="metsRoot3"
The root <mets>element must include a TYPE attribute value. This value must conform to the list given in the controlled vocabularies section above. description:
These are the supported values for the mets root element TYPE attribute in METS documents conforming to this profile. "image" and "facsimile text" are appropriate values to denote the type of object the METS describes. "image" designates an object that is composed of graphical materials; "facsimile text" designates an object that is a text represented by graphical materials (e.g. scanned documents). structural_requirements:
metsRootElement:
requirement:
@ID="metsRoot1"
The root <mets> element must include an OBJID attribute value that contains a valid ARK and that uniquely identifies the object. requirement:
@ID="metsRoot3"
@RELATEDMAT="vc2"
The root <mets>element must include a TYPE attribute value. This value must conform to the list given in the controlled vocabularies section above. [email protected]metsHdr:
requirement:
@ID="metsHdr2"
The <metsHdr> element must include a CREATEDATE attribute value. It should, but is not required to, include a LASTMODDATE attribute value when this differs from the CREATEDATE value. requirement:
@ID="metsHdr3"
The <metsHdr> element must include a child <agent> element identifying the person or institution responsible for creating the METS object. requirement:
@ID="metsHdr4"
The <metsHdr> element must include a child <altRecordID> element that contains the identifier used by the institution submitting this object to CDL, but only when that value is not a valid ARK. If an institution uses the ARK identifier scheme for their identifiers, the altRecordID may be omitted. dmdSec:
requirement:
@ID="dmdSec1"
METS documents must contain a one or more <dmdSec> elements. Each <dmdSec> may in turn contain a <mdRef> or a <mdWrap>. requirement:
@ID="dmdSec2"
The primary descriptive metadata section - which will appear sequentially as the first <dmdSec> - must use <mdWrap> to encompass a record that conforms to Dublin Core schema specifications. This record will describe the complete object, rather than a component part. Other descriptive metadata sections may appear; it is recommended, though not required, that they conform to a descriptive metadata schema endorsed by the METS Editorial Board. requirement:
@ID="dmdSec3"
The primary <dmdSec> element must have an ID attribute with the value "DC". The <mdWrap> element must have a MIMETYPE, LABEL and MDTYPE attribute value, with the LABEL and MDTYPE attribute value being "DC". amdSec:
requirement:
@ID="amdSec1"
METS documents may but need not contain oand and only one <amdSec> element. This <amdSec> may but need not contain one or more <techMD> elements, <sourceMD> elements, <rightsMD> elements and/or <digiprovMD> elements. requirement:
@ID="amdSec2"
It is recommended, though not required, that <rightsMD>, <techMD>, <sourceMD> and <digiprovMD> sections employ a schema endorsed by the METS Editorial Board, such as METSRights. fileSec:
requirement:
@ID="fileSec2"
The <fileSec> of a conforming METS document must contain a parent <fileGrp> for each file format/use represented by the content files. Each of these <fileGrp> elements may but need not contain subsidiary <fileGrp> elements representing subgroups of the content files. requirement:
@ID="fileSec3"
Each <file> represented in the <fileSec> must have an ID attribute value that is unique within the METS instance for use in linking from the <structMap>. requirement:
@ID="fileSec4"
@RELATEDMAT="vc1"
Each <file> represented in the <fileSec> must have an associated USE attribute. The USE attribute may be expressed directly at the <file> element level. Alternately, however, the USE attribute may be expressed in conjunction with the <fileGrp> that is the immediate parent of a <file> element; in this case it is taken to pertain to all <file> elements in the <fileGrp>. The value must conform to the list given in the controlled vocabularies sections above. mets/fileSec/fileGrp/@USE mets/fileSec/fileGrp/file/@USErequirement:
@ID="fileSec5"
If a <fileGrp> contains more than one <file> element, it is recommended, but not required that each <file> have an associated GROUPID attribute. In cases where there is only one <file> contained in a <fileGrp>, the GROUPID attribute is not necessary. requirement:
@ID="fileSec6"
If a raw ASCII text transcription file exists for a scanned document, it must be included within the <fileSec> using <file><FContent><xmlData> and must have the element <transcription> as the wrapping element for the content. structMap:
requirement:
@ID="structMap2"
It is recommended that each <div> element have an associated ID attribute . requirement:
@ID="structMap3"
A <structMap> must have a top-level <div> element that represents the object as a whole. requirement:
@ID="structMap4"
A <div> element may but need not directly contain one and only one <fptr> elements. (In other words, a <div> may or may not have content files directly associated with it.) If a <div> does not directly govern an <fptr> element, then it must contain at least 1 descendant <div> element with associated content. requirement:
@ID="structMap5"
A <div> can have at most one content file directly associated with it - and hence at most one child <fptr> element. If multiple manifestations of the same content are available (for example, a thumbnail image and two service images of different resolutions), each of these manifestations must be represented by a discrete <div> element. requirement:
@ID="structMap6"
A <div> element cannot directly contain both a <div> element and an <fptr> element as immediate children. A <div> element may have one or more <div> elements as immediate children; or it may have a single <fptr> element as an immediate child element. requirement:
@ID="structMap7"
Each <div> that does not directly contain a <fptr> element must include a LABEL attribute value. requirement:
@ID="structMap8"
If a <div> directly contains a <fptr>, it must have an associated TYPE attribute and must not have associated LABEL or ORDER attributes. technical_requirements:
content_files:
requirement:
@ID="content1"
Image content files referenced from or included in conforming METS documents must be of one of the following types: GIF, JPG, JP2, PNG or TIFF. Please consult the CDL Guidelines for Digital Images (http://www.cdlib.org/inside/diglib/guidelines/bpgimages/) for more information about profiles, resolution, encoding, and other format issues. requirement:
@ID="content2"
Text transcriptions, if they appear, must be raw, unstructured ASCII text. tool:
agency:
California Digital Library description:
This XSL-based transformation package converts CONTENTdm XML exports into METS objects conforming to this profile. |
 Top
of Page |
||||
| |
|
|||
|
|
|||
|
||||