JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-GENERAL Archives


DC-GENERAL Archives

DC-GENERAL Archives


DC-GENERAL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-GENERAL Home

DC-GENERAL Home

DC-GENERAL  December 1996

DC-GENERAL December 1996

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Dublin Core/MARC crosswalk

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

Rebecca S. Guenther

Date:

Thu, 19 Dec 1996 14:14:43 -0500 (EST)

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (234 lines)

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
[log in to unmask]

---------------------------------------------------------------------
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)






Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

February 2024
May 2022
April 2022
March 2022
March 2020
February 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager