Rda and marc 21: a discussion Paper

Download 172.18 Kb.

Date	31.07.2017
Size	172.18 Kb.
	#25790

RDA and MARC 21: A Discussion Paper

At the April 2006 JSC meeting, it was agreed that ACOC and CCC would produce a mapping of MARC 21 to RDA. The purpose of the mapping is to enable JSC and the MARC community to identify issues relating to the alignment of RDA and MARC 21 and to highlight certain MARC 21 elements to consider for inclusion in RDA. A reverse mapping, i.e. of RDA elements to MARC, will be undertaken after the initial review of this discussion paper. Further issues are likely to arise from the reverse mapping.

The documents used for the analysis are:
-5JSC/RDA/Part I (9 Dec. 2005)

-5JSC/RDA/ Prospectus/Rev/2 (19 June 2006)

-5JSC/Part A/Chapters 6-7 (20 June 2006)

-5JSC/Editor/RDA/Part B (September 15, 2006)

-MARC 21 Format for Bibliographic Data (1999 edition, last updated Oct. 2005)
After JSC’s review at its October meeting, a MARBI discussion paper will be written, in consultation with LC’s Network Development and MARC Standards Office, for consideration at the January 2007 MARBI meeting.
This paper is comprised of three separate parts:
A. Issues and/or RDA elements that have implications for MARC 21
B. Potential additions to RDA

Mapping of MARC 21 to RDA

A. Issues and/or RDA elements that have implications for MARC 21

Below are a number of items the MARC community may wish to consider. Some of the points were raised in the course of a JSC meeting; in such cases, the minute reference has been added.

i) Terminology - RDA reflects updated terminology for concepts that proliferate through MARC 21. Examples of terms that exist in MARC 21 but are no longer used in RDA are main entry, added entry, entry, uniform title, tracing, heading.
ii) 3.2 Media category, 3.3 Type of carrier, 4.2 Content category – These three new RDA elements replace the existing GMD carried in field 245, subfield $h in MARC 21. The impact of the RDA categorization of content and carrier may also stimulate an analysis and assessment of similar coded data carried in MARC 21 Leader and fixed fields.
iii) Punctuation (M/34.7) – RDA has been designed to establish a clear separation between the presentation and recording of data, with presentation guidelines (including punctuation) contained in appendices. In MARC 21 records formulated according to ISBD principles, punctuation is embedded with the element that is recorded; content designation has not been defined to facilitate the generation of punctuation. This issue needs to be discussed with the MARC community.
iv) Parallel titles (M/33.4.1) - RDA treats titles in another language or script as parallel titles regardless of whether or not they are on the same source as the title proper. This is a change from AACR2 and ISBD. In MARC 21 records formulated according to ISBD principles, the parallel title is recorded in field 245 when it appears on the prescribed source of information. It has been suggested that a code could be defined to identify the source of the parallel title. In addition, consideration could be given to the use of field 246.
v) 2.7 Publication, 2.8 Distribution, 2.9 Manufacture, and 2.10 Production – RDA has defined separate elements for publication, distribution, manufacture and production; each element has separate sub-elements of “name”, “place” and “date”. MARC 21 field 260 currently uses the same subfields for publication and distribution data. Is there a need to distinguish these elements through MARC 21 coding?

vi) 1.6 Transcription (M/76.4) – RDA 1.6 instructs one to transcribe an element as it appears following guidelines for capitalization, numerals, etc. Options have been added to provide some flexibility in this area by allowing elements to be transcribed according to in-house manuals/ published style manuals or by recording the element as it appears when it has been scanned, etc., from a digital source. To facilitate record matching, it may be useful to define a code(s) to identify if either of the options at 1.6 is followed. It had been suggested that authentication codes could potentially serve this purpose.

vii) 6.4.1.2.1c.2 Alternative for recording the source of a reproduction and 6.4.2.2.1.c.2 – Alternative for recording a reproduction – These alternatives, which have not yet been discussed, allow for the recording of elements of the description for reproductions and originals in parallel. The instructions refer to “using encoding to indicate that the element applies to the related resource”. If the alternatives are retained, this will need to be considered by the MARC community.

viii) 3.4 -3.18 Carrier description elements - RDA has defined a number of aspects of the technical description as separate elements, with a greater level of granularity than is given in MARC 21 field 300. Additional fields or subfields may be needed to encode this information.

ix) 2.13 Resource identifier – Final decisions have not yet been made on how to treat standard identifiers and other resource identifiers. However, RDA may broaden the range of standard identifiers for which it provides instructions beyond those currently provided for in specific MARC 21 fields or in the indicator values in field 024.

3.21 Mode of access – Discussion is not yet complete, but this element is being considered for deletion.
There are a range of issues related to the scope of RDA, and the interdependence between RDA and MARC 21 that would be useful for the two communities to discuss:

RDA refers at various points to the need to indicate the nature of something either through the use of preceding text, or using encoded values. At a later point these will need to be re-evaluated to see if there are implications for MARC 21.

RDA is conducting a review of the appendices, including the one on Initial articles, and new articles have been proposed for inclusion. Any changes which result will be referred to MARC 21 for inclusion in Initial Definite and Indefinite Articles.

RDA refers at 7.6 Designation of roles to the use of standard lists, such as the MARC Code Lists for Relators, Sources, Description Conventions.

xii) MARC 21 (bibliographic ) Leader/18 (Descriptive cataloging form); MARC 21 (authority) 008/10 (Descriptive cataloging rules) – New values will be needed for RDA.

B. Potential additions to RDA

In mapping MARC fields to the RDA elements, a number of fields were identified which were deemed to be potentially in scope for RDA but which did not have an equivalent element in RDA.

For each of these fields we invite JSC to confirm that there is not an equivalent RDA element, and that the field is in scope for RDA.^¹ JSC might also wish to evaluate the MARC-RDA mapping to ensure that no other fields that are potentially in scope have been omitted.

018 Copyright Article-Fee Code

026 Fingerprint Identifier

210 Abbreviated Title

258 Philatelic Issue Data

263 Projected Publication Date

307 Hours, Etc.

343 Planar Coordinate Data

355 Security Classification Control

357 Originator Dissemination Control

365 Trade Price

366 Trade Availability Information

507 Scale Note for Graphic Material

514 Data Quality Note

518 Date/Time and Place of an Event Note

524 Preferred Citation of Described Materials Note

526 Study Program Information Note

536 Funding Information Note*

544 Location of Other Archival Materials Note

550 Issuing Body Note*

552 Entity and Attribute Information Note

563 Binding Information

565 Case File Characteristics Note

567 Methodology Note

581 Publications About Described Materials Note

583 Action Note

585 Exhibitions Note

720 Added Entry – Uncontrolled Name

786 Data Source Entry

787 Nonspecific Relationship Entry

In order to assist in the prioritisation of potential additions to RDA, the occurrences of these fields in MARC records have been analysed (see Appendix 1). Fields which were present in at least one record in every 10,000 records in both data sets are given below.

They have been divided into two lists, one relating to Chapters 1-5, for which proposals follow, and one relating to Chapters 6+ for which proposals have not been prepared at this time.

Chapters 1-5

263 Projected Publication Date

507 Scale Note for Graphic Material

518 Date/Time and Place of an Event Note

524 Preferred Citation of Described Materials Note

536 Funding Information Note*

544 Location of Other Archival Materials Note

550 Issuing Body Note*

581 Publications About Described Materials Note

583 Action Note

585 Exhibitions Note
Chapters 6+

210 Abbreviated Title

720 Added Entry – Uncontrolled Name

787 Nonspecific Relationship Entry*

Proposals for additions to RDA

We invite JSC to consider whether we wish to include data elements corresponding to these fields in RDA, either as part of the initial release in 2008, or at a later time. Some of these had also been previously identified by ACOC as potential additions to RDA in 5JSC/RDA/Part I/ACOC response (i.e. 263, 518, 544, 583, and 585).
In the proposals below suggestions have been made on where the proposed instruction should be placed, and the instruction numbered accordingly. No recommendations on consequential renumbering have been made. The instructions have been framed as notes or as recorded elements as seemed appropriate.

263 Projected Publication Date

(Note: Identified in 5JSC/RDA/Part I/ACOC response, and JSC representatives have generally indicated that they would like to see a proposal.)
MARC field definition and scope:

The projected date of publication used in bibliographic records for works that have not yet been published.

Comment(s)

In MARC the date is recorded as a six-digit date recorded in the pattern yyyymm. The format(s) in which this element should be recorded should be consistent with those for the date of publication (see responses to 5JSC/RDA/Part I). No instruction has been provided for a resource that is not published, as this is dependent on the policy of the particular program.

Placement of the instruction

This instruction could either be included in the instruction on recording the date of publication or as a separate element following that instruction. The proposal below treats it as a separate element following that instruction.

2.7.4	Projected date of publication
	Optional element
	Contents
	2.7.4.0 Basic instructions on projected date of publication
2.7.4.0	Basic instructions on projected date of publication
	Contents
	2.7.4.0.1 Scope
	2.7.4.0.2 Sources of information
	2.7.4.0.3 Recording projected date of publication
2.7.4.0.1	Scope
2.7.4.0.1.1	A projected date of publication is the expected date of publication supplied by the publisher to any program which creates resource descriptions for resources that have not yet been published.
2.7.4.0.2	Sources of information
2.7.4.0.2.1	Take the projected date of publication from any source.
2.7.4.0.3	Recording projected date of publication
2.7.4.0.3.1	Record the projected date of publication of the resource, indicating the year, or year and month, in the form yyyy--or yyyymm.
	200904
	2012--
2.7.4.0.3.2	If the projected date of publication changes, revise it as appropriate. When the resource is published, delete the projected date of publication.

507 Scale Note for Graphic Material

MARC field definition and scope:

For visual materials, this field contains the scale of architectural drawings or three-dimensional artifacts. For maps, the scale of an item is contained in this field only in pre-AACR 2 cataloging records. Scale information is contained in field 255 (Mathematical Data Area) in AACR 2 formulated records.

Placement of the instruction

The Scale of Cartographic Content is given at 4.13, and this instruction could precede that instruction.

Comment(s)

Given the level of specificity of the cartographic instruction, it would be difficult for the two instructions to be combined. ^² The instruction would then also need to be treated as a recorded element.

4.13	scale of graphic content
	Optional element
	Contents
	4.13.0 Basic instructions on noting scale of graphic content
4.13.0	Basic instructions on noting scale of graphic content
	Contents
	4.13.0.1 Scope
	4.13.0.2 Sources of information
	4.13.0.3 Noting scale of graphic content
4.13.0.1	Scope
4.13.0.1.1	The scale of graphic content is the proportion or ratio of an image to the image or three-dimensional form which it represents.
4.13.0.2	Sources of information
4.13.0.2.1	Take the scale of graphic content from any source.
4.13.0.3	Noting scale of graphic content
4.13.0.3.1	Make notes on the scale of the graphic content of the resource.
	Scale 1:100
	One centimetre equals one metre
	“Half the scale of the original.”
4.13.0.3.2	If the graphic content is not drawn to scale, and it is considered to be important, record Not drawn to scale.
	Not drawn to scale

518 Date/Time and Place of an Event Note

(Note: Identified in 5JSC/RDA/Part I/ACOC response, with a mixed reaction from JSC representatives.)
MARC field definition and scope:

Textual information on the date/time and/or place of creation, capture, or broadcast associated with an event or the finding of a naturally occurring object.

Comment(s)

There is some overlap between the scope of this field and the RDA instructions on recording the place and date of publication, distribution, manufacture, and production. The instructions for these elements are currently being revised, so it is difficult to prepare a proposal at this time.

Recommendation

It is recommended that the Editor incorporate provision for events such as performance, recording, and broadcast in the revised instructions for notes on these elements.

Examples

Recorded at Paradise Studios, Sydney, Apr. 22-23, 1997

Broadcast on BBC Wales Radio 4, 15 November 1971, 8.30-9.15 p.m.

Recorded in the Coolidge Auditorium of the Library of Congress, Washington, D.C., Sept. 13, 2002

'Dusty: Little by Little' was broadcast in Australia as 26 minute episodes on ABC-TV on the following dates: March 14, 21, 28 & April 4, 11, 18, 25, 2006.

524 Preferred Citation of Described Materials Note

MARC field definition and scope:

The format of the citation of the described materials that is preferred by the custodian.

Comment(s)

In MARC this field is limited to the format preferred by the custodian, however it is recommended that this be expanded as many resources contain information about preferred citations.

Placement of the instruction

As this instruction is related to identification of the resource, it has been placed in Chapter 2 between the instructions on Resource identifiers, and those on Published descriptions.

2.14	Preferred citation
	Optional element
	Contents
	2.14.0 Basic instructions on preferred citations

2.13.0	Basic instructions on preferred citations
	Contents
	2.14.0.1 Scope
	2.14.0.2 Sources of information
	2.14.0.3 Recording preferred citations
2.14.0.1	Scope
2.14.0.1.1	A preferred citation is a citation in the form preferred by the creator, publisher or custodian, etc., of the resource.
2.14.0.2	Sources of information
2.14.0.2.1	Take information on preferred citations from any available source.
2.14.0.3	Recording preferred citations
2.14.0.3.1	Record the preferred citation for the resource.
	Cite as: Janus Press Archive, Rare Book and Special Collections Division, Library of Congress
	Cite as: W. G. Alma conjuring collection. Photographs
	Preprint. Cite as Michelle L. Kaarst-Brown, Scott Nicholson, Gisela M. von Dran, and Jeffrey M. Stanton, School of Information Studies, Syracuse University, Syracuse, NY 13244 LIBRARY TRENDS, Vol. 53, No. 1, Summer 2004 (“Organizational Development and Leadership,” edited by Keith Russell and Denise Stephens), pp. 33–53
	PROV, VA 672 Premier's Office, VPRS 1163/P1 Inwards Correspondence Files, Unit 744, 1883/291 letter re. remedy for pauperism.
	Fletcher, P.R., (2004) PhD Thesis - How Tertiary Level Physics Students Learn and Conceptualise Quantum Mechanics (School of Physics, University of Sydney)
	To cite this page: http://nla.gov.au/nla.pic-vn3579894

536 Funding Information Note

MARC field definition and scope:

Contract, grant, and/or project numbers when the described material is the result of a funded project. Information concerning the sponsor or funding agency also may be included.

Comment(s)

Although the scope note in MARC indicates that the primary purpose of this field is to record associated numbers, in practice it appears to have been mostly used to record information about sponsoring bodies.

Placement of the instruction

The 536 has been partially mapped to 2.4.3.7. If information on funding agencies is considered to be fully covered by 2.4.3.7, additional examples could be given at that instruction.

Information on associated numbers could be given in a general instruction on ‘other numbers’ placed near 2.13 Resource identifiers.
Alternatively, a separate instruction could be given as below.

2.x	FUNDING INFORMATION
	Optional element
	Contents
	2.X.0 Basic instructions on noting funding information
2.X.0	Basic instructions on noting funding information
	Contents
	2.X.0.1 Scope
	2.X.0.2 Sources of information
	2.X.0.3 Noting funding information
2.X.0.1	Scope
2.X.0.1.1	Funding information is information on the agency which funded the project, etc., which resulted in the creation of the resource.
2.X.0.1.2	Funding information may include contract, grant or project numbers.
2.X.0.2	Sources of information
2.X.0.2.1	Take funding information from any source.
2.X.0.3	Noting funding information
2.X.0.3.1	Make notes on the funding information for the resource
	Supported by contracts between the National Academy of Sciences and the American Academy of Sleep Medicine, the Department of Health and Human Services, the National Sleep Foundation, and the Sleep Research Society. Contract no. N01-OD-4-2139
	"EQUAL is funded by the European Social Fund (ESF)."-- P. 1.
	Performed by University of Alaska Dept. of Civil and Environmental Engineering for Alaska Dept. of Transportation and Public Utilities under contract no. T2-01-01, RES-01-018
	European Commission, Health and Consumer Protection Directorate-General No. SPC.2002356

544 Location of Other Archival Materials Note

(Note: Identified in 5JSC/RDA/Part I/ACOC response, and JSC representatives have generally indicated that they would like to see a proposal.)
MARC field definition and scope:

The name and address of the custodian of materials that, at a previous time, have been part of the same collection or record group as the described materials.

Placement of the instruction

This instruction might be appropriately placed in several locations, and so a specific instruction number has not been proposed:

4.10 Related Content

5.6 Custodial history and immediate source of acquisition

Ch. 6 Related resources.
Comment(s)

Depending on where this instruction is placed, it may require substantial revision. However, the following has been provided to facilitate discussion by JSC.

X.X	location of related archival resources
	Optional element
	Contents
	X.X.0 Basic instructions on noting the location of related archival resources
X.X.0	Basic instructions on noting the location of related archival resources
	Contents
	X.X.0.1 Scope
	X.X.0.2 Sources of information
	X.X.0.3 Noting the location of related archival resources
X.X.0.1	Scope
X.X.0.1.1	Related archival resources are resources which are related to the resource being described by having been previously part of the same collection.
X.X.0.2	Sources of information
X.X.0.2.1	Take information on the location of related archival resources from any available source.
X.X.0.3	Noting location of related archival resources
X.X.0.3.1	Make notes on the location of related archival resources, including the name and address of the custodian of those resources.
X.X.0.3.2	Related material: Interview with Alan Hopgood, National Library of Australia Oral History Collections ORAL TRC 5355 Refer to the related resources specifically, or in general terms, as appropriate.
	Sound recordings transferred to Library of Congress Motion Picture, Broadcasting and Recorded Sound Division Related material: Interview with Alan Hopgood, National Library of Australia Oral History Collections ORAL TRC 5355

550 Issuing Body Note

MARC field definition and scope:

This field contains a note referring to current and former issuing bodies, including notes containing editing, compiling or translating information that involves an issuing body. Notes denoting the item is an official organ of a society, etc., are included in this field.

Comment(s)

The 550 is partially mapped to 2.4.3.7 Other persons, families, and corporate bodies associated with the resource and 2.4.3.9 Change in statement of responsibility.

This field is also used to justify access points for related corporate bodies when the body is not named elsewhere on the resource, and to record that a resource is an official publication of a body.
In RDA, justifications for access points are not necessary, although they may be helpful to include. The instruction at 7.4 Additional access points for publishers, producers, etc., might also be expanded to encompass this relationship.
Placement of the instruction

The remaining things recorded in this field would seem to fit with the Chapter 2 ‘Identification of the Resource’, and might best be covered by the addition of appropriate examples at 2.4.3.7 Other persons, families, and corporate bodies associated with the resource.

Examples

"The official national magazine of the Australian Institute of Landscape Architects."

Endorsed by Canadian Society of Exercise Physiology and Canadian Society for Clinical Nutrition.

Issued by the National Research Council Canada.

"Jointly hosted by: George Mason University, School of Public Policy, Center for Science and Technology Policy; and: Harvard University, Kennedy School of Government, Belfer Center for Science and International Affairs."

581 Publications About Described Materials Note

MARC field definition and scope:

This field contains a note giving the citation or information about a publication that is based on the use, study or analysis of the materials described in the record. … This field can also be used to record citations to published sources, such as exhibition or collection catalogs, that contain photocopies or reproductions of items.

Comment(s)

An informal review of the use of this field indicated

This field has often been used incorrectly to record citations or references to published descriptions or reviews of an item which should be given in a MARC 510 Citation/references note.

Although the scope note indicates that it should be used to record citations to exhibition catalogues, in many cases these citations are given as part of the MARC field 585 Exhibition note.

This field has rarely been used to record information about publications based on the ‘use, study or analysis of the materials described’.

Most uses of this field appear to be associated with recording citations to published sources where an unpublished resource has been reproduced.

Recommendation

JSC discuss whether an element based on the scope of this MARC field should be added to RDA. If it is decided to limit the scope to citations to published sources where an unpublished resource has been reproduced, consider whether a new element should be provided, or whether 6.4.2 Reproduction could be expanded to cover this situation.

Examples
Published in: American women : a Library of Congress guide for the study of women's history and culture in the United States / edited by Sheridan Harvey ... [et al.]. Washington : Library of Congress, 2001, p. [2]

A selection of photographs published in: Tour of duty: winning hearts and minds in East Timor / by Matthew Sleeth. Victoria : Hardie Grant Publishing, 2002

Published in: North coasting : the story of the Northern Rivers of New South Wales from the Clarence to the Tweed / photographed and written by Lee Pearce. Coolgardie, N.S.W. : Pearce Cormack Publishing, 2004, p. 102

583 Action Note

(Note: Identified in 5JSC/RDA/Part I/ACOC response, with a mixed reaction from JSC representatives.)
MARC field definition and scope:

Contains information about processing, reference, and preservation actions.

Comment(s)

The 583 Action note as currently scoped in MARC might seem to group a wide variety of unrelated activities. In Libraries Australia, this field has been used primarily to record selection for archiving of an online resource. So, although it is a copy-specific field, some of the information provided in this field (e.g. digitisation intentions) is useful to agencies beyond the particular agency that holds the copy.

In MARC, this field is further defined in Preservation & Digitization Actions: Terminology for MARC 21 Field 583 http://www.loc.gov/marc/bibliographic/pda.pdf (2004), which could be considered a content standard for the preservation and digitisation activities recorded in this element.
Placement of this instruction

The wide variety of activities covered by this instruction has made it difficult to suggest a specific location for this instruction. Placement at 3.24, following Carrier details of the item being described, has been suggested.

Recommendation

That JSC discuss:

Whether this field is in scope for RDA
Whether a general instruction which covers all the actions in MARC 583 should be provided in RDA, or whether separate instructions which relate to the separate activities would be more useful. The possibility of adding this element to RDA as a placeholder for future expansion is one possibility.

3.24	actions
	Optional element
	Contents
	3.24.0 Basic instructions on noting actions

3.24.0	Basic instructions on noting actions
	Contents
	3.24.0.1 Scope
	3.24.0.2 Sources of information
	3.24.0.3 Noting actions
3.24.0.1	Scope
3.24.0.1.1	Actions are processes associated with the evaluation, acquisition, exhibition, loan, transfer, preservation, etc., of a copy of the described resource.
3.24.0.1.2	Information on actions may include information on associated authorizations, conditions, methods, agents, agencies, statuses etc., and on the part of the described material to which the action applies.
3.24.0.2	Sources of information
3.24.0.2.1	Take information on actions from any available source.
3.24.0.3	Noting actions
3.24.0.3.1	Make notes describing the action performed.
	Selected for archiving
	Rebound 11 May 2007
	Stabilised and shrink-wrapped, State Library of New South Wales, 2003.
	Permanent loan to Yale University, 2003-

585 Exhibitions Note

(Note: Identified in 5JSC/RDA/Part I/ACOC response, and JSC representatives have generally indicated that they would like to see a proposal.)
MARC field definition and scope:

A copy-specific field that contains a citation to an exhibition where the described materials have been shown.

Placement of the instruction

This instruction might be appropriately placed in Chapter 4, following the instruction on Awards.

4.20	Exhibitions
	Optional element
	Contents
	4.20.0 Basic instructions on noting exhibitions

4.20.0	Basic instructions on noting exhibitions
	Contents
	4.20.0.1 Scope
	4.20.0.2 Sources of information
	4.20.0.3 Noting exhibitions
4.20.0.1	Scope
4.20.0.1.1	Exhibitions are events where the whole resource, or part(s) of an aggregate resource, have been presented or displayed.
4.20.0.1.2	Exhibitions include online exhibitions.
4.20.0.2	Sources of information
4.20.0.2.1	Take information on exhibitions from any available source.
4. 20.0.3	Noting exhibitions
4.20.0.3.1	Make notes indicating the name, location and duration of exhibitions where the resource has been presented or displayed.
	Exhibited: "In a New Light 2", National Library of Australia, 2 December 2004 - 28 March 2005
	Exhibited in: Enduring Outrage: Editorial Cartoons by Herblock, Library of Congress, 2006-2007
	Exhibited: 'Cook & Omai: The Cult of the South Seas', National Library of Australia, 17 February – 27 May 2001, and online at http://www.nla.gov.au/exhibitions/omai/

Appendix 1. MARC Utilisation

In order to assist in the prioritisation of additions to RDA, the occurrences of these fields in MARC records have been analysed. Data on occurrences in LC and OCLC records was provided by MARC Content Designation Utilization Project, (http://www.mcdu.unt.edu/?p=30) a project funded by the U.S. Federal Institute of Museum and Library Services (IMLS). Data on occurrences in the Libraries Australia database was provided by Libraries Australia.
Fields which were present in at least one record in every 10,000 records in both data sets are highlighted below. The frequency of occurrences may be affected by when the tag became available for use.
Note that a higher percentage of occurrences will be found for some of these fields in records of specific types, e.g.

321 occurs in 0.18% of the general sample, but in 4.76% of LC records for continuing resources.
507 occurs in 0.18% of the general sample, but in 28.12% of LC records for cartographic materials.
585 occurs in 0.01% of the general sample, but in 1.39% of LC records for graphic materials.

Some care therefore needs to be taken in using this occurrence data as an indicator of tag value.

	Records Where Field is Used at Least Once
MARC tag	Number (LC & OCLC)*	% (LC & OCLC)*	Number (LA incl. NLA)	% (LA incl.
018 Copyright Article-Fee Code	10,470	0.02%	13	0.00%
026 Fingerprint Identifier	Not in data
210 Abbreviated Title	272,484	0.49%	244,926	1.88%
258 Philatelic Issue Data^³	Not in data
263 Projected Publication Date	219,428	0.39%	226,688	1.74%
307 Hours, Etc.	1,524	0.00%	2	0.00%
343 Planar Coordinate Data	4	0.00%	1	0.00%
355 Security Classification Control	Not in data
357 Originator Dissemination Control	Not in data
365 Trade Price	Not in data
366 Trade Availability Information	Not in data
507 Scale Note for Graphic Material	103,775	0.18%	13,592	0.11%
514 Data Quality Note	116	0.00%	0	0.00%
518 Date/Time and Place of an Event Note	682,209	1.21%	102,704	0.79%
524 Preferred Citation of Described Materials Note	73,949	0.13%	3,745	0.03%
526 Study Program Information Note	922	0.00%	25	0.00%
536 Funding Information Note*	175,937	0.31%	4,474	0.34%
544 Location of Other Archival Materials Note	10,418	0.02%	4,288	0.33%
550 Issuing Body Note*	272,652	0.49%	146,576	1.13%
552 Entity and Attribute Information Note	7	0.00%	4	0.00%
556 Information about Documentation Note*	1,680	0.00%	1,727	0.01%
563 Binding Information	1,304	0.00%	7	0.00%
565 Case File Characteristics Note	1,827	0.00%	4	0.00%
567 Methodology Note	816	0.00%	0	0.00%
581 Publications About Described Materials Note	7,307	0.01%	4,058	0.03%
583 Action Note	136,104	0.24%	4,880	0.04%
585 Exhibitions Note	2,927	0.01%	8,430	0.07%
720 Added Entry – Uncontrolled Name	47,004	0.08%	20,325	0.16%
786 Data Source Entry	7,596	0.01%	0	0.00%

C. Mapping of MARC 21 to RDA

The following table maps the data elements contained in MARC 21 to the corresponding elements in Part A of RDA. The table is a “work in progress”. Final decisions are still pending on some areas of Part A. The Editor’s draft of Part B to provide preliminary mappings of data elements in access point fields. Some mappings are prefaced by ‘prev’. This means that they have been mapped to elements formerly existing in 5JSC/RDA/Part I.

Scope
The table excludes the Leader and fixed fields. Indicators have been omitted unless there is a corresponding RDA element. Control subfields have also been excluded.
“Out of scope” indicates that the element is not within the scope of RDA as a descriptive content standard.
“Not in RDA” indicates that the element is potentially within the scope of RDA but has no corresponding RDA element. These elements are potential candidates for inclusion in RDA as outlined under Potential additions to RDA.
Many MARC 21 fields do not map cleanly to the RDA elements. In general a partial mapping has been given wherever possible.
Questions for JSC
We welcome JSC’s review of the mapping and request JSC’s consideration of the following specific questions:
015 National bibliography number – the mapping has treated this field in the same manner as field 010 and 016, i.e., “Out of scope” since they have been considered numbers identifying the bibliographic record and not the resource. Does JSC agree or can number carried in field 015 identify the resource and mapped to 2.13?
026 Fingerprint identifier – should this be considered a resource identifier and mapped to 2.13?

1 An asterisk indicates that the field has been partially mapped.

2 For further information on recording scale statements for architectural drawings, see A guide to the description of architectural drawings. http://www.getty.edu/research/conducting_research/standards/fda/

3 258 Philatelic Issue Data was defined to support the chapter in Rules for Archival Description for the description of philatelic material.

*Partially mapped.

Directory: archivedsite -> workspace
workspace -> Identifying corporate Bodies
workspace -> Examples Group 2 Chapter 9
workspace -> To: Joint Steering Committee for Development of rda from: Judith A. Kuhagen, Secretary, jsc subject

Download 172.18 Kb.

Share with your friends: