gils: Dublin Core mapping to USMARC

Dublin Core mapping to USMARC

Eliot Christian (echristi@usgs.gov)
Fri, 20 Dec 1996 09:10:23 -0500
Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Brodie Nancy: "Dublin Core mapping to GILS"
Previous message: Eliot Christian: "Press Release: GLOBAL LOCATOR SERVICE FOR ENVIRONMENTAL INFORMATION"
Message-Id: <2.2.32.19961220141023.00716a24@130.118.4.2>
Date: Fri, 20 Dec 1996 09:10:23 -0500
To: gils@cni.org
From: Eliot Christian <echristi@usgs.gov>
Subject: Dublin Core mapping to USMARC

The following is copied from a note that appeared on the CIMI (Consortium
for the Computer Interchange of Museum Information) List:

At  2:14 PM 12/19/96 -0500, Rebecca S. Guenther wrote:
>Last week I sent Eric Miller the following to update the Web page that
>OCLC put up with a crosswalk between Dublin Core elements and MARC. Anyone
>who has used that information should use this updated document instead for
>any possible conversions between DC and MARC fields.
>
>Rebecca Guenther
>rgue@loc.gov
>
>---------------------------------------------------------------------
>Dublin Core/USMARC Crosswalk
>
>In some cases, there are two mappings provided. The first is a
>simple mapping and is used if the elements are used without
>qualifiers.  The second is for a more complex description for
>which the elements have qualifiers.  There could be a mixture,
>but if the particular element is unqualified, then the simple
>mapping for that element should be used.  Certain defaults have
>been assumed as to definitions and qualifiers; if this changes
>the list will need to be adjusted.  This list has been made
>consistent with the GILS/MARC mapping where possible. Where
>applicable, subfields are given.
>
>When the list of qualifiers becomes standardized it will be
>necessary to modify this document and add to it as appropriate. 
>Only the most obvious qualifiers have been included now.
>
>USMARC fields are listed with field number, then in parentheses
>field name/subfield name (if both the same no subfield name
>included).  If value of indicator is not provided, use a blank
>(H'20').
>
>1 Title          Label: TITLE
>
>The name given to the resource by the CREATOR or PUBLISHER.
>
>USMARC: 245$a (Title Statement/Title proper) (with 1st
>indicator=0)
>
>2 Author or Creator                       Label: CREATOR
>
>     The person(s) or organization(s) primarily responsible for
>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.
>
>USMARC: 100$a (Main Entry--Personal Name) (with 1st indicator=1)
>Qualifiers:
>If role=corporate: 110$a (Main entry--Corporate Name)
>
>3 Subject and Keywords    Label: SUBJECT
>
>The topic of the resource, or keywords or phrases that describe the
>subject or content of the resource.  The intent of the specification of
>this element is to promote the use of controlled vocabularies and
>keywords.  This element might well include scheme-qualified classification
>data (for example, Library of Congress Classification Numbers or Dewey
>Decimal numbers) or scheme-qualified controlled vocabularies (such as
>MEdical Subject Headings or Art and Architecture Thesaurus descriptors) as
>well.
>
>USMARC: 653$a (Index Term--Uncontrolled)
>Qualifiers:
>If scheme=LCSH: 650$a (Subject added entry--topical term)
>If scheme=LCC: 050$a (Library of Congress Call
>Number/Classification number)
>If scheme=DDC: 082$a (Dewey Decimal Call Number/Classification
>number)
>
>4 Description                     Label: DESCRIPTION
>
>A textual description of the content of the resource, including abstracts
>in the case of document-like objects or content descriptions in the case
>of visual resources.  Future metadata collections might well include
>computational content description (spectral analysis of a visual resource,
>for example) that may not be embeddable in current network systems.  In
>such a case this field might contain a link to such a description rather
>than the description itself.
>
>USMARC: 520$a (Summary, etc. note)
>
>        
>5 Publisher                               Label: PUBLISHER
>
>     The entity responsible for making the resource available in
>its present form, such as a publisher, a university department,
>or a corporate entity.   The intent of specifying this field is
>to identify the entity that provides access to the resource.
>
>USMARC: 260$b (Publication, Distribution, etc. (Imprint)/Name of
>publisher, distributor, etc.)
>     
>6 Other Contributors                              Label: CONTRIBUTORS
>
>     Person(s) or organization(s) in addition to those specified
>in the CREATOR element who have made significant intellectual    
>contributions to the resource but whose contribution is secondary
>to the individuals or entities specifed in the CREATOR element
>(for example, editors, transcribers, illustrators, and
>convenors).
>
>USMARC: 720$a (Added Entry--Uncontrolled Name/Name)
>If role=" " Add data content in role= to 720$e (Added Entry--
>Uncontrolled Name/Relator Term)
>If type=personal: 700$a (Added Entry--Personal Name)
>If type=corporate: 710$a (Added Entry--Corporate Name)
>Add data in "role=" to 700$e or 710$e as appropriate.
>
>7 Date                            Label: DATE
>
>     The date the resource was made available in its present
>form.  The recommended best practice is an 8 digit number in the
>form YYYYMMDD as defined by ANSI X3.30-1985. In this scheme, the
>date element for the day this is written would be 19961203, or
>December 3, 1996.  Many other schema are possible, but if used,
>they should be identified in an unambiguous manner.
>
>USMARC: 260$c (Date of publication, distribution, etc.)
>(Will add additional mappings if different types are specified by
>type=)
>
>     
>8 Resource Type                   Label: TYPE
>
>     The category of the resource, such as home page, novel,
>poem, working paper, technical report, essay, dictionary.  It is
>expected that RESOURCE TYPE will be chosen from an enumerated
>list of types. A preliminary set of such types can be found at
>the following URL:
>     
>     http://www.roads.lut.ac.uk/Metadata/DC-ObjectTypes.html
>
>USMARC: 516$a (Type of Computer File or Data Note)
>
>9 Format                          Label: FORMAT
>   
>     The data representation of the resource, such as text/html,
>ASCII, Postscript file,  executable application, or JPEG image. 
>The intent of specifying this element is to provide information
>necessary to allow people or machines to make decisions about the
>usability of the encoded data (what hardware and software might
>be required to display or execute it, for example).  As with
>RESOURCE TYPE, FORMAT will be assigned from enumerated lists such
>as registered Internet Media Types (MIME types).  In principal,
>formats can include physical media such as books, serials, or
>other non-electronic media. 
>
>USMARC: 538$a (System Details Note)
>      
>10 Resource Identifier                     Label: IDENTIFIER
>
>     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
>International Standard Book Numbers (ISBN) or other formal names
>would also be candidates for this element.
>
>USMARC: 024$a (with 1st indicator=8) (Other Standard
>Identifier/Standard number or code)
>If type=URL: 856$u (Uniform Resource Locator) (with 1st
>indicator=7)
>If type=ISBN: 020$a (International Standard Book Number)
>If type=ISSN: 022$a (International Standard Serial Number)
>If type=URN: 856$u with initial "urn:" (with 1st indicator=7)
>
>11 Source                         Label: SOURCE
>
>     The work, either print or electronic, from which this
>resource is derived, if applicable. For example, an html encoding
>of a Shakespearean sonnet might identify the paper version of the
>sonnet from which the electronic version was transcribed.
>
>USMARC: 786$t (Data Source Entry/Title) (with 1st indicator=0)
>
>12 Language                       Label: LANGUAGE
>
>     Language of the intellectual content of the resource.  The
>default expression of natural languages is according to the ISO
>639 two letter language codes.  
>
>USMARC: 546$a (Language note)
>If scheme=ISO 639-2 or scheme=USMARC: 041$a (Language code)     
>
>     See:
>     http://www.stonehand.com/unicode/standard/iso639.html.
>A three-character language code standard is currently being
>ballotted as: ISO 639-2 (not yet available electronically)
>
>13 Relation                       Label: RELATION 
>
>     Relationship to other resources.  The intent of specifying
>this element is to provide a means to express relationships among
>resources that have formal relationships to others, but exist as
>discrete resources themselves.  For example, images in a
>document,  chapters in a book, or items in a collection.  A
>formal specification of RELATION is currently under development. 
>Users and developers should understand that use of this element
>should be currently considered experimental.
>
>USMARC: 787$n (Nonspecific Relationship Entry/Note) (with 1st
>indicator=0)
>
>14 Coverage                       Label: COVERAGE
>
>     The spatial locations and temporal durations characteristic
>of the resource.    Formal specification of COVERAGE is currently
>under development. Users and developers should understand that
>use of this element should be currently considered experimental.
>
>USMARC: 500$a (General note)
>If spatial: 255$c (Cartographic Mathematical Data/Statement of
>coordinates)
>If temporal: 513$b (Type of Report and Period Covered Note/Period
>covered)
>
>15 RIGHTS MANAGEMENT                      Label: RIGHTS
>   
>     The content of this element is intended to be a link (a URL
>or other suitable URI as appropriate) to a copyright notice, a
>rights-management statement, or perhaps a server that would    
>provide such information in a dynamic way.  The intent of
>specifying this field is to allow providers a means to associate
>terms and conditions or copyright statements with a resource or
>collection of resources.   No assumptions should be made by users
>if such a field is empty or not present.
>
>USMARC: 506$a (Restrictions on Access Note/Terms governing
>access)
Next message: Brodie Nancy: "Dublin Core mapping to GILS"
Previous message: Eliot Christian: "Press Release: GLOBAL LOCATOR SERVICE FOR ENVIRONMENTAL INFORMATION"