Dublin Core and MARC
(Historical Document)
Note: This document includes material from the following sources:
University of Minnesota CORC Corner
(http://www.lib.umn.edu/ts/drafts/Cat/CORC/) (Document no longer available 8/1/01.);
Guidelines for Use of Dublin Core in University of Chicago Library Projects
(http://www.lib.uchicago.edu/TechInfo/TechSvcs/dcguidelines.html) (Document no longer available 5/15/02.);
User Guide for Simple Dublin Core
(http://purl.org/dc/documents/working_drafts/wd-type-current.htm) (Note 8/26/03: This url now redirects the user to "Using Dublin Core", Creator: Diane Hillmann.)
General
The University Libraries' CORC project supports the use of CORC Dublin Core (DC) metadata as a distinct format with its own content standard. This standard is based in part on emerging DC guidelines and standards documents, many of which are early drafts and subject to revision. Creators of OSU CORC/DC records will not be expected to adhere to AACR2, LCRIs, SCM:SH, and national authority file standards, nor to achieve the degree of consistency which is intended through the use of these rule sets and data standards. Likewise, in terms of detail, CORC records may not conform to OSUL cataloging standards for OSCAR. This document is intended to provide the minimum standards that will be accepted locally, for CORC records.
Currently CORC/DC records will be accessed primarily via keyword searching in CORC. One goal of the local project is to explore and evaluate different modes of creating, accessing, and importing CORC/DC records. These records will require review and editing to be successfully integrated into OSCAR, a more rule and standards governed environment.
The number given following each CORC/DC field name below is the MARC field or subfield to which CORC assigns the data. Note that in some cases, the DC-to-MARC translation imposed by the CORC software limits the use and form of DC fields in ways not inherent in the DC format. For example, only one DC Creator field should be used since the MARC translation is a 1XX field. Although DC would permit multiple Creator fields, MARC allows only one.
CORC-supplied data drawn from online resources by the MANTIS toolkit will be reviewed for accuracy, clarity, and readability. CORC-supplied data and tagging may be edited, added to, or deleted. Elements defined by the OSUL CORC project as mandatory for the description of online resources are: Title, ID-URL, and one SubjLCSH. Creator, DescrNote or DescrSummary, and DatePublished are required elements, if applicable. In addition, MARC fields 910 and 949 must be added to the OSUL MARC record, before records can be added to FELIX. It is recommended that collection managers use 952 field to provide notes to the catalogers about the record or resource. All other fields are optional. Participants may go beyond the specified contents if their training and experience enables them to do so, and if the resource access and description will benefit. However, project participants will not be expected to provide CORC/DC record content beyond the four fields specified in this standard.
General note about names: Enter the name of a given person or body in only one name field (Contributor, Contrib..., Creator..., SubjName...) on a record. Use SubjName only for names which do not appear in one of the other fields.
CORC/DC fields (in alphabetical order)
Note: Double starred fields (**) are mandatory for OSUL CORC project. Single starred fields (*) are required (if applicable).
Contributor. A person or organization not specified in a Creator element who has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organization specified in the Creator element (for example editor, transcriber, illustrator). Important Note: Although the generic contributor field (MARC 720, i.e. the uncontrolled name field) may be useful in the CORC database, it will be stripped from the OSCAR record. Prefer the 700, 711, and 710 fields.
|
Contributor (720) Personal or corporate name, uncontrolled. Use as many names as are appropriate in Contributor fields. Enter the name as found in the resource. A comma may be used to invert personal names; or, the name may be entered as found if the inverted form is uncertain. Order the elements of a hierarchical corporate name from larger to smaller, separated by periods if this order is clear; otherwise enter as found. Multiple forms of the same name, separated by semicolons, are entered in a single Contributor field. Examples:
ContribCorp (710)
ContribPersonal (700) |
Coverage. The spatial or temporal characteristics of the intellectual content of the resource ...
|
CoverageGeo (691 $z) Geographic area represented in the resource. Use any expression which clearly specifies the area covered by the resource as stated in the resource, e.g.
CoverageTime (691 $y)
For more precise coding of single and ranged times and dates, see the discussion paper at: http://www.w3.org/TR/NOTE-datetime |
*Creator. The person or organization primarily responsible for creating the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources.
If the source object is an original web page, Creator may be omitted. Use judgement to decide whether the creator is likely to be significant (e.g. for a bibliography) or irrelevant (e.g. for a "portal page") from a user or searcher's point of view. The form of names in the Creator field is controlled. Use the Contributor field for names in uncontrolled form.
|
CreatorCorp (110) Corporate name with primary responsibility for the resource, controlled form. Use this field only when the corporate body would be considered the main entry for the resource under AACR2. Cf. ContribCorp CreatorPersonal (100) Personal name with primary responsibility for the resource, controlled form. Use this field only when the person would be considered the main entry for the resource under AACR2. Cf. ContribPersonal. |
*Date. A date associated with the creation or availability of the resource. Such a date is not to be confused with one belonging to the Coverage element, which would be associated with the resource only insofar as the intellectual content is somehow about that date. Recommended best practice is defined in a profile of ISO 8601 (http://www.w3.org/TR/NOTE-datetime) that includes (among others) dates of the forms YYYY and YYY-MM-DD.
|
*Date Published (260 $c) Use capture date as supplied by CORC. You may add a date of creation and date of latest revision separated by semicolons if they are present in the resource, with text to indicate the meaning of each date. Use the format YYYY-MM-DD to record dates. If you are cataloging a resource that is not online, use the date published from the resource. Examples:
|
|
DescrEd/Vers (250) Use only for resources with a clearly stated edition or version designation.
*DescrNote (500)
DescrPhysical (300)
*DescrSummary (520) |
Format. The data format of the resource, used to identify the software and possibly hardware that might be needed to display or operate the resource.
|
Format-MIME Accept the default. For a list of internet media format types and subtypes, see http://www.isi.edu/in-notes/iana/assignments/media-types/media-types |
Identifier. A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers, such as ISBNs or other formal names are candidates for this element.
|
**ID-URL (856 $u) Use the URL for the most direct and appropriate entry point to the resource being described. CORC/DC records for parts of a website and/or for the website as a whole may be created to bring out different views or aspects of a resource. If a PURL is known, use that. If more than one URL/PURL for the resource are being added (e.g., for mirror sites or URL plus PURL), use separate ID-URL fields for each one. |
Language. The language of the intellectual content of the resource. Where practical, the content of this field should coincide with RFC 1766: Tags for the identification of languages, see http://www.cis.ohio-state.edu/htbin/rfc/rfc1766.html Omit this element for non-textual objects; include it consistently for textual ones. Use "en" for English. If there is more than one language, use multiple occurrences of the field, DC.Language.
Publisher. The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity.
|
Publisher (260 $b) Use the name of the provider of an online resource only when the name of the resource provider is not given in a Creator…, Contributor, or Contrib… field. |
Rights. A rights-management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource. If a statement of copyright applies to the object, include the copyright statement in this field.
Relation. An identifier of a second resource and its relation to the present resource. This element permits links between related resources and resource descriptions to be indicated. Examples include an edition of a work (IsVersionOf), a translation of a work (IsBasedOn), a chapter of a book (IsPartOf), and a mechanical transformation of a dataset into an image (IsFormatOf). For a fuller discussion of the Resource field, see Diane Hillman's "A User's Guide to Simple Dublin Core" at http://purl.org/dc/documents/working_drafts/wd-guide-current.htm (Note 8/26/03: This url now redirects the user to "Using Dublin Core", Creator: Diane Hillmann).
Precede the identifier of the second resource with a qualifier from the list below:
| Qualifier | Description |
|---|---|
| IsPartOf | Part/Whole relations are those in which one resource is a physical or logical part of another. |
| HasPart | |
| IsVersionOf | Version relations are those in which one resource is an historical state or edition, of another resource by the same creator |
| HasVersion | |
| IsFormatOf | Format transformation relations are those in which one resource has been derived from another by a reproduction or reformatting technology which is not fundamentally an interpretation but intended to be a representation |
| HasFormat | |
| References | Reference relations are those in which the author of one resource cites, acknowledges, disputes, or otherwise make claims about another resource. |
| IsReferencedBy | |
| IsBasedOn | Creative relations are those in which one resource is a performance, production, derivation, adaptation or interpretation of another resource. |
| IsBasisFor | |
| Requires | Dependency relations are those in which one resource requires another resource for its functioning, delivery, or content and cannot be used without the related resource being present. |
| IsRequiredBy | |
Source. Information about a second resource from which the present resource is derived. While it is generally recommended that elements contain information about the present resource only, this element may contain a date, creator, format, identifier, or other metadata for the second resource when it is considered important for the discovery of the present resource. Recommended best practice is to use the Relation element instead.
Subject. The topic of the resource. Typically, the subject will be expressed as keywords or phrases that describe the subject or content of the resource. The use of controlled vocabularies and formal classification schemes is encouraged.
|
SubjClassDDC (092) Use CORC-supplied DDC numbers only if you can verify that they match the content of the resource. Check the full hierarchy of the class number, not just the immediate caption. Preliminary checking indicates that more often than not, the CORC-supplied DDC numbers are inaccurate. If you cannot verify that the DDC numbers are appropriate, delete them. If you have been trained in assigning DDC numbers, you may add them.
SubjClassLCC (090)
SubjGeoLCSH (651)
SubjNameCorp (610)
SubjNamePers (600)
SubjKeyw (653)
**SubjLCSH (650 0)
SubjMeSH (650 2) |
**Title. The name given to the resource by the Creator or Publisher.
|
**Title (245) Select the title for an online resource from the screen displayed in response to the URL. If the CORC-supplied title differs from the displayed title, change its CORC/DC tag to Title-Alternative, and add a display-based Title field. In selecting the title, bear in mind the need for meaning and clarity when the Title is used in CORC index displays. If there is no title, or if the display title conveys no useful information (e.g. "Report"), create a title for the resource, putting supplied wording in brackets (e.g., "Report [of the OSUL E-Resources Task Force]", "Welcome to the U! [University of Minnesota]"). Use only one Title field per record.
Title-Alternative (246) |
Type. The category of the resource, such as home page, novel, poem, working paper, technical report, essay, dictionary.
Generally accept the default value. Currently approved terms for use with Type are:
|
text image sound dataset software interactive event physical object Use multiple Type fields when a resource has significant components of more than one type. For definitions and further information, see http://purl.org/dc/documents/working_drafts/wd-type-current.htm (Note 8/26/03: This url now redirects the user to "Using Dublin Core", Creator: Diane Hillmann). |
OSUL MARC fields
MANDATORY: The MARC 910 and 949 fields must be added to the MARC version of the CORC record in order to input records into FELIX.
OPTIONAL (and temporary): 952 local note
910 (User Option Data)
|
In this field enter "CORC" and one of the following OCLC holding symbols for OSU: hea
(Health Sciences), ard (Ohio Agricultural Research & Development Center), osu (Ohio
State University Libraries), e.g. 910 CORC hea tc 910 CORC ard tc 910 CORC osu tc |
949 (Local Processing Information. Two occurrences of this field required: 949 with second indicator 0 (for the bibliographic record), and 949 with second indicator 1 (for item record).
| 949 | 0 | Bibliographic record $l bib location (3 letter library location) $m material type (e.g. "m"=computer file) $x suppression (e.g. "z"=disloc/nocent, remove from central display) |
| Values to be used for the 949 _0 field are: bib location, www; materal type, m; and suppression code, z. Example: |
| 949 | 0 | $l www $m m $x z |
| 949 | 1 | Item (Note: only the subfields applicable to CORC defined below) $l item location (For OSUL CORC, use www) $j Icode1 - use 0 for monographs, msets, or serials $s Status code - use "g" for "Use online" $t Itype - use "016" Internet resource $x Icode2 - suppression code (use "z" disloc/nocent - item record will display locally, remove from central |
| Values to be used for the 949 _1 field are: item location, www; Icode1, 0; Status, g; Itype, 016; and Icode2, -. Example: |
| 949 | 1 | $l www $j 0 $s g $t 016 $x - |
952 (Local note): This field can be used by collection managers to provide notes about the record or resource to cataloger(s) who will be completing the record. Note: This field is not retained in OSCAR.
Drafted 1999-09-13
Current revision 1999-11-18
Previous revision 1999-10-20