Difference between revisions of "RDA 2.1"

From AC Wiki
Jump to: navigation, search
m (→‎020 field)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
==RDA 2.1 : 010, 020, 022, 034 Fields==
+
==RDA 2.1: 010, 020, 022, 034 Fields==
−
{| border="0" cellpadding="5" cellspacing="0" align="left"
+
[[Image:rda2-1.png]]<br><br>
−
|-
+
 
−
! colspan="4" style="background: lightblue" | 2.1 - 010, 020, 022, 034 Fields
+
== Numeric Field Validation ==
−
|- align="left" style="background: white"
+
MARC fields that are incorrectly formatted often cause user searches to fail and prevent items in the collection from being included in the system indexes. MARS 2.0 software can validate the structure of numeric data in the following fields:<ul><li>010:  Library of Congress Control Number (LCCN)<li>020:  International Standard Book Number (ISBN)<li>022:  International Standard Serial Number (ISSN)<li>034:  Coded Cartographic Mathematic Data (CCMD)</ul>
−
| || style="background: #CCFFFF;" | &#9744; Yes ||
+
 
 +
Please indicate on Step 2.1 what kind of validation you would like performed on your 010, 020, 022, or 034 fields. Choosing '''Yes, With these modifications''' means that you would like the MARS 2.0 software to perform a modified validation (e.g., validate fields 020 and 022, but not fields 010 or 034).
 +
 
 +
==Default==
 +
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
 +
|- style="background:#CCFFFF; font-size: 110%;"
 +
| Validate 010, 020, 022, 034 fields.
 
|}
 
|}
 
<div style=clear:both></div><br>
 
<div style=clear:both></div><br>
−
===[[Step_2.1|Validate 010, 020, 022, 034 fields]]===
 
−
MARC fields that are incorrectly formatted often cause user searches to fail and
 
−
prevent items in the collection from being included in the system indexes. MARS
 
−
2.0 can clean up spacing, hyphens, prefixes, and suffixes of the 010, 020, 022,
 
−
and 034 fields.
 
  
−
===[[Step_2.2|step 2.2 : leader & fixed field updates]]===
+
== Pre-2001 LCCN ==
−
Bibliographic validation processing provides a variety of updates and corrections
+
LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens):<br>
−
to values in the Leader and Fixed fields (006, 007, 008). These updates mainly
+
<font size="3">  1  2  3    4  5    6
−
consist of changing one value to another based on the type of record format
+
nb#-71-005810-#-/AC-/r86</font>
−
(book, map, etc.).
+
 
 +
#3-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
 +
#2 digits, usually the last 2 digits of the '''year'''
 +
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits
 +
#Blank '''space'''
 +
#Optional variable length '''suffix''' and/or alphabetic identifier
 +
#Optional '''revision date'''
 +
 
 +
Examples of LCCN Structure A (the character # represents a single space):<br>
 +
<font size="3">  ###95156543# Displayed as: 95-156543
 +
###94014580#/AC/r95 Displayed as: 94-14580/AC/r95
 +
###79310919#//r86 Displayed as: 79-310919//r86
 +
nb#71005810# Displayed as: nb71-5810</font>
 +
 
 +
== Post-2000 LCCN ==
 +
LCCN Structure B (2001 and later) numbers are formatted according the following 3 divisions (separated by hyphens):<br>
 +
<font size="3">  1  2    3
 +
##-2005-256543</font>
 +
 
 +
#2-character '''prefix''' with '''lowercase letters''' and/or '''blanks'''
 +
#4-digit '''year'''
 +
#6-digit '''serial number''', with zeroes padded to the left to make 6 digits
 +
 
 +
Examples of LCCN Structure B (the character # represents a single space):<br>
 +
<font size="3">  ##2005256543 Displayed as: 2005-256543
 +
##2010014580 Displayed as: 2010-14580
 +
nb2005005810 Displayed as: nb2005-5810</font>
 +
 
 +
According to the Library of Congress, Structure A LCCNs will not be changed to Structure B. This minimizes the impact of the LCCN change for local systems. Since LCCN structures A and B will continue to exist in authority and bibliographic records, MARS 2.0 programs provide for validation of both old and new LCCN formats. No provision is necessary, therefore, for the conversion of Structure A to the new Structure B formats, or vice versa.
 +
 
 +
=== LCCN structure A corrections ===
 +
If the LCCN in the 010 $a is identified as a Structure A LCCN and does '''not''' have a valid structure, MARS 2.0 programs make the following format corrections (all changes are subsequently checked for validity):
 +
*If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number:
 +
<font size="3">  Original:  95-156543 Corrected to: ###95156543#</font>
 +
 
 +
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 2 blanks (##) between the alphabetic character and the number to make a valid 3-character prefix:
 +
<font size="3">  Original:  n95-156543 Corrected to: n##95156543#</font>
 +
 
 +
*If the first 2 characters of the LCCN are alphabetic and the third character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic characters and the number to make a valid 3-character prefix:
 +
<font size="3">  Original:  nb95-156543 Corrected to: nb#95156543#</font>
 +
 
 +
*If a hyphen appears in the 010 $a, MARS 2.0 programs count the number of digits before the hyphen. If one digit is before the hyphen, a 0 (zero) is inserted before the first digit in the LCCN (following the prefix). If 2 digits are before the hyphen, no zeroes are inserted at the beginning of the LCCN:
 +
<font size="3">  Original:  nb#9-156543 Corrected to: nb#09156543#
 +
Original:  nb#95-156543 Corrected to: nb#95156543#</font>
 +
 
 +
*MARS 2.0 programs also count the number of digits following the hyphen. If there are fewer than 6 digits, zeroes are added following the first 2 digits (##-) of the LCCN to make 6 digits (for a total of 8 digits). The hyphen is deleted from the LCCN:
 +
<font size="3">  Original:  nb#95-6543 Corrected to: nb#95006543#
 +
Original:  nb#95-56543 Corrected to: nb#95056543#</font>
 +
 
 +
*If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs:
 +
<font size="3">  Original:  nb#95-516543//r86 Corrected to: nb#95156543#</font>
 +
 
 +
*If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit:
 +
<font size="3">  Original:  nb#95-516543 Corrected to: nb#95156543#</font>
 +
 
 +
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.
 +
 
 +
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 4 characters in the prefix or there are 9 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in step 5 for more information about this report.
 +
 
 +
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 +
<font size="3">  #a# -> a##
 +
##a -> a##
 +
#bc -> bc#
 +
# -> ###
 +
## -> ###</font>
 +
 
 +
=== LCCN structure B corrections ===
 +
If the LCCN in the 010 $a is identified as a Structure B LCCN and does not have a valid structure, MARS 2.0 programs attempt to correct it by making these conversions (all changes are subsequently checked for validity):
 +
*If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number:
 +
<font size="3">  Original:  2005-256543 Corrected to: ##2005256543</font>
 +
 
 +
*If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic character and the number to make a valid 2-character prefix:
 +
<font size="3">  Original:  n2005-256543 Corrected to: n#2005256543
 +
Original:  nb2005-256543 Corrected to: nb2005256543</font>
 +
 
 +
*If a hyphen or blank space appears in the 010 $a, MARS 2.0 programs count the number of digits following the hypen. If there are fewer than 6 digits, zeroes are added following the first 4 digits (####-) of the LCCN to make 6 digits (for a total of 10 digits). The hyphen is deleted from the LCCN:
 +
<font size="3">  Original:  nb2005-6543 Corrected to: nb2005006543</font>
 +
 
 +
*If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.
 +
 
 +
*If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 3 characters in the prefix or there are 11 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in Step 5 for more information about this report.
 +
 
 +
*The following invalid LCCN prefixes are corrected to the valid format (# = blank):
 +
<font size="3">  #a -> a#
 +
#bc -> bc
 +
# -> ##</font>
 +
 
 +
== 020 field ==
 +
Some automated systems do not index an ISBN if the format is invalid. An ISBN in field 020 $a should be 10 digits or 13 digits. If the ISBN in 020 $a does not have the valid structure, MARS 2.0 programs attempt to correct the ISBN structure by performing the following conversions:
 +
*If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN:
 +
<font size="3">  Original:  873671008 Corrected to: 0873671008</font>
 +
 
 +
*All hyphens are deleted:
 +
<font size="3">  Original:  1-873671-008 Corrected to: 1873671008</font>
 +
 
 +
*A lowercase x is converted to uppercase:
 +
<font size="3">  Original:  187367100x Corrected to: 187367100X</font>
 +
 
 +
*If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are '''978''' or '''979'''.
 +
 
 +
*As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)
 +
 
 +
*As an optional service, MARS 2.0 programs will convert ISBN-10 to ISBN-13 (includes check-sum value for both 10 and 13 length ISBNs):
 +
<font size="3">  Original:  1873671008 Corrected to: 9781873671000</font>
 +
 
 +
*If MARS 2.0 programs cannot correct the format of the ISBN in the 020 $a (e.g., there are 11 digits), the 020 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.
 +
 
 +
=== Historical fact ===
 +
The structure of the ISBN has changed over the past thirty years. Prior to 1977, the 020 field was not repeatable and multiple ISBNs and related information were placed in repeated subfields. Older bibliographic records may still have multiple ISBNs in a single 020 field rather than in multiple 020 fields. January 1, 2007 marked the final date for fully adopting ISBN-13. Between 2005 and 2008, publishers were encouraged to supply both an ISBN-10 and an ISBN-13 for the same manifestation, based on guidelines issued by the International ISBN Agency (IIA). The Library of Congress began accommodating ISBN-13 on October 1, 2004. At the beginning of 2007 is when publishers were expected to supply only ISBN-13.
 +
 +
=== Ordering 020 fields ===
 +
LC will accept both an ISBN-13 and an ISBN-10 for the same manifestation. These numbers are shown by publishers according to guidelines issued by the IIA, which call for grouping the pairs of ISBNs by manifestation. In printed products the ISBN-13 appears first, and each number is preceded by a print constant as in the following example:<br>
 +
<font size="3">  ISBN-13:  978-1-873671-00-0
 +
ISBN-10:  1-873671-008</font>
 +
 
 +
=== Repeating 020 subfields ===
 +
MARS 2.0 Update processing validates an 020 field for correct subfield repeatability. If the 020 field contains multiple $a, each $a is placed in a separate 020 field:<br>
 +
<font size="3">  020 $a 11111111 $a 22222222
 +
Corrected to:
 +
020 $a 11111111
 +
020 $a 22222222</font>
 +
 
 +
=== Binding information in 020 fields ===
 +
Prior to 1978, binding information was placed in a $b. Older bibliographic records may have binding information in a $b rather than as a parenthetical qualifier in the $a.
 +
 
 +
If the 020 field contains a $b and an 020 $a exists:
 +
*$b delimiter and subfield code are deleted
 +
*020 $b data is enclosed in parentheses
 +
*A blank is inserted at the end of the immediately preceding 020 $a data
 +
*020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data
 +
<font size="3">  Original:  020 $a 1873671008 $b pbk. Corrected to:  020 $a 1873671008 (pbk.)</font>
 +
 
 +
=== 020 with missing $a ===
 +
If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c:<br>
 +
<font size="3">  020 $b pbk.
 +
Corrected to:
 +
020 $c pbk.</font>
  
−
===[[Step_2.3|step 2.3 : field updates &deletes]]===
+
=== 020 with multiple $c ===
−
Changes to the MARC 21 communications format have made many fields
+
If the 020 field contains multiple $c, each $c is placed in a separate 020 field:<br>
−
obsolete. If one field has been replaced by another, the update changes the tag
+
<font size="3">  020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)
−
number. If the field has been made obsolete without being replaced, the field
+
Corrected to:
−
is simply deleted from the bib record. There are 22 fields that are changed to
+
020 $c 4.95 (lib. bdg.)
−
another field. Currently, 16 fields are removed from the bib record in this step.
+
020 $c 3.60 (pbk.)</font>
  
−
===[[Step_2.4|step 2.4 : subfield updates & deletes]]===
+
=== 020 with multiple $a and $c ===
−
Many subfields are no longer valid within certain fields and so the subfield
+
MARS 2.0 programs correctly handle 020 fields with multiple $a and $c:<br>
−
marker is changed from one (invalid) to another (valid). There are also a number
+
<font size="3">  020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.
−
of subfields which no longer have any corresponding use in the bib record and
+
Corrected to:
−
these are removed as part of the bibliographic validation processing. Relator
+
020 $a 11111111 $c 4.95
−
term entries are included in this step. There are 15 subfields changed to another
+
020 $a 22222222 $c 3.60
−
subfield, with 24 fields that have obsolete subfields removed altogether.
+
020 $c 8.97 (pbk.)</font>
  
−
===[[Step_2.5|step 2.5 : indicator updates]]===
+
== 022 Field ==
−
In order to bring the indicators (both 1st & 2nd) in line with current MARC 21
+
MARS 2.0 Update processing can validated the format of the ISSN in field 022 $a. Some automated systems do not index an ISSN if the format is invalid. A valid ISSN in field 022 $a has the following structure: 4 digits, hyphen, 4 digits (or digits and an X):<br>
−
standards, many fields in this step have their indicators changed from one value
+
<font size="3">  1234-1234
−
(invalid) to a specific value (valid). There are 32 fields with the 1st indicator
+
1234-123X</font>
−
updated and 26 fields with the 2nd indicator updated.
+
  
−
===[[Step_2.6|step 2.6 : field conversions & additions]]===
+
If the ISSN in field 022 $a does not have the valid structure, MARS 2.0 programs attempt to correct it by making these conversions:
−
A number of MARC update conversions are more complex than simply changing
+
*If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits:
−
a field tag or subfield code to the current value. Some fields, such as the 007,
+
<font size="3">  Original:  123<u>4</u>5678 Corrected to:  123<u>4-5</u>678</font>
−
often need to be added to a record.
+
  
−
Step 2.6 adds missing format data, missing subfield data, and makes complex
+
*Converts a lowercase '''x''' to uppercase:
−
field conversions. There are 12 fields in this step that are affected.
+
<font size="3">  Original:  1234-567<u>x</u> Corrected to:  1234-567<u>X</u></font>
  
−
===[[Step_2.7|step 2.7 : initial article & filing indicators]]===
+
*If MARS 2.0 programs cannot correct the format of the ISSN in the 022 $a (e.g., there are 9 digits), the 022 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.
−
MARS 2.0 supports the standard practice of omitting most initial articles even if
+
−
a nonfiling character indicator has been defined for the field. Initial articles are
+
−
retained, and the filing indicator correctly set, for the 245 and 440 fields.
+
  
−
You can also choose to have corporate heading fields checked for initial articles. This applies to the $t in the X10 fields.
+
== 034 Field ==
 +
MARS 2.0 Update processing can validate field 034 CMD (Coded Mathematical Data) for correct format. If the 034 field first indicator has value 2 and the 034 field contains multiple $a, MARS 2.0 Update processing:
 +
*Places each $a in a separate 034 field
 +
*Changes each 034 field first indicator to value 1
 +
<font size="3">  034 2_$a a $b 100000 $a a $b 120000
 +
Corrected to:
 +
034 1_$a a $b 100000
 +
034 1_$a a $b 120000</font>
  
−
There is also an extensive list of each initial article with its associated filing
+
=== Historical fact ===
−
indicator, sorted by language.
+
First indicator value '''2''' became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.
  
−
==LINKS==
+
==links==
−
<center><font size="4">[[RDA_2.1|2.1]] - [[RDA_2.2|2.2]] - [[RDA_2.3|2.3]] - [[RDA_2.4|2.4]]
+
<center><font size="4">[[RDA_2.1|2.1]] - [[RDA_2.2|2.2]] - [[RDA_2.3|2.3]] - [[RDA_2.4|2.4]] - [[RDA_2.5|2.5]] - [[RDA_2.6|2.6]] - [[RDA_2.7|2.7]]
 
<hr>
 
<hr>
 
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]]</font></center>
 
[[RDA_1.0|1.0]] - [[RDA_2.0|2.0]] - [[RDA_3.0|3.0]] - [[RDA_4.0|4.0]] - [[RDA_5.0|5.0]] - [[RDA_6.0|6.0]]</font></center>
 
[[category:RDA Profile Guide]]
 
[[category:RDA Profile Guide]]

Latest revision as of 07:50, 18 August 2017

RDA 2.1: 010, 020, 022, 034 Fields

Rda2-1.png

Numeric Field Validation

MARC fields that are incorrectly formatted often cause user searches to fail and prevent items in the collection from being included in the system indexes. MARS 2.0 software can validate the structure of numeric data in the following fields:
  • 010: Library of Congress Control Number (LCCN)
  • 020: International Standard Book Number (ISBN)
  • 022: International Standard Serial Number (ISSN)
  • 034: Coded Cartographic Mathematic Data (CCMD)

Please indicate on Step 2.1 what kind of validation you would like performed on your 010, 020, 022, or 034 fields. Choosing Yes, With these modifications means that you would like the MARS 2.0 software to perform a modified validation (e.g., validate fields 020 and 022, but not fields 010 or 034).

Default

Validate 010, 020, 022, 034 fields.

Pre-2001 LCCN

LCCN Structure A (2000 and earlier) numbers are formatted according to the following 6 divisions (separated by hyphens):

	   1   2   3    4  5    6
	nb#-71-005810-#-/AC-/r86
  1. 3-character prefix with lowercase letters and/or blanks
  2. 2 digits, usually the last 2 digits of the year
  3. 6-digit serial number, with zeroes padded to the left to make 6 digits
  4. Blank space
  5. Optional variable length suffix and/or alphabetic identifier
  6. Optional revision date

Examples of LCCN Structure A (the character # represents a single space):

	  ###95156543#			Displayed as:	95-156543
	###94014580#/AC/r95		Displayed as:	94-14580/AC/r95
	###79310919#//r86		Displayed as:	79-310919//r86
	nb#71005810#			Displayed as:	nb71-5810

Post-2000 LCCN

LCCN Structure B (2001 and later) numbers are formatted according the following 3 divisions (separated by hyphens):

	   1   2     3
	##-2005-256543
  1. 2-character prefix with lowercase letters and/or blanks
  2. 4-digit year
  3. 6-digit serial number, with zeroes padded to the left to make 6 digits

Examples of LCCN Structure B (the character # represents a single space):

	  ##2005256543			Displayed as:	2005-256543
	##2010014580			Displayed as:	2010-14580
	nb2005005810			Displayed as:	nb2005-5810

According to the Library of Congress, Structure A LCCNs will not be changed to Structure B. This minimizes the impact of the LCCN change for local systems. Since LCCN structures A and B will continue to exist in authority and bibliographic records, MARS 2.0 programs provide for validation of both old and new LCCN formats. No provision is necessary, therefore, for the conversion of Structure A to the new Structure B formats, or vice versa.

LCCN structure A corrections

If the LCCN in the 010 $a is identified as a Structure A LCCN and does not have a valid structure, MARS 2.0 programs make the following format corrections (all changes are subsequently checked for validity):

  • If the first character of the LCCN is a number (no prefix is present), the programs insert 3 blanks (###) before the number: 
	  Original:  95-156543			Corrected to:	###95156543#
  • If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 2 blanks (##) between the alphabetic character and the number to make a valid 3-character prefix: 
	  Original:  n95-156543			Corrected to:	n##95156543#
  • If the first 2 characters of the LCCN are alphabetic and the third character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic characters and the number to make a valid 3-character prefix: 
	  Original:  nb95-156543			Corrected to:	nb#95156543#
  • If a hyphen appears in the 010 $a, MARS 2.0 programs count the number of digits before the hyphen. If one digit is before the hyphen, a 0 (zero) is inserted before the first digit in the LCCN (following the prefix). If 2 digits are before the hyphen, no zeroes are inserted at the beginning of the LCCN: 
	  Original:  nb#9-156543			Corrected to:	nb#09156543#
	Original:  nb#95-156543			Corrected to:	nb#95156543#
  • MARS 2.0 programs also count the number of digits following the hyphen. If there are fewer than 6 digits, zeroes are added following the first 2 digits (##-) of the LCCN to make 6 digits (for a total of 8 digits). The hyphen is deleted from the LCCN: 
	  Original:  nb#95-6543			Corrected to:	nb#95006543#
	Original:  nb#95-56543			Corrected to:	nb#95056543#
  • If the LCCN contains a suffix, the suffix is removed in accordance with the revised LC standard for Structure A LCCNs: 
	  Original:  nb#95-516543//r86		Corrected to:	nb#95156543#
  • If the LCCN does not end with a blank, MARS 2.0 programs insert a blank following the last digit: 
	  Original:  nb#95-516543			Corrected to:	nb#95156543#
  • If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.
  • If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 4 characters in the prefix or there are 9 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in step 5 for more information about this report.
  • The following invalid LCCN prefixes are corrected to the valid format (# = blank): 
	  #a#		->		a##
	##a		->		a##
	#bc		->		bc#
	#		->		###
	##		->		###

LCCN structure B corrections

If the LCCN in the 010 $a is identified as a Structure B LCCN and does not have a valid structure, MARS 2.0 programs attempt to correct it by making these conversions (all changes are subsequently checked for validity):

  • If the first character of the LCCN is a number (no prefix is present), the programs insert 2 blanks before the number: 
	  Original:  2005-256543		Corrected to:	##2005256543
  • If the first character of the LCCN is an alphabetic character and the second character is a number, MARS 2.0 programs insert 1 blank (#) between the alphabetic character and the number to make a valid 2-character prefix: 
	  Original:  n2005-256543		Corrected to:	n#2005256543
	Original:  nb2005-256543	Corrected to:	nb2005256543
  • If a hyphen or blank space appears in the 010 $a, MARS 2.0 programs count the number of digits following the hypen. If there are fewer than 6 digits, zeroes are added following the first 4 digits (####-) of the LCCN to make 6 digits (for a total of 10 digits). The hyphen is deleted from the LCCN: 
	  Original:  nb2005-6543		Corrected to:	nb2005006543
  • If the 010 field data has been modified, the 010 field length is recalculated and the 010 directory entry is updated. The record length is recalculated and updated in the record leader.
  • If MARS 2.0 programs cannot correct the format of the LCCN in the 010 $a (e.g., there are 3 characters in the prefix or there are 11 digits), the 010 $a code is changed to $z and a report can be generated. See report R50 in Step 5 for more information about this report.
  • The following invalid LCCN prefixes are corrected to the valid format (# = blank): 
	  #a		->		a#
	#bc		->		bc
	#		->		##

020 field

Some automated systems do not index an ISBN if the format is invalid. An ISBN in field 020 $a should be 10 digits or 13 digits. If the ISBN in 020 $a does not have the valid structure, MARS 2.0 programs attempt to correct the ISBN structure by performing the following conversions:

  • If there are 9 digits in the ISBN, a 0 (zero) is inserted before the first digit in the ISBN: 
	  Original:  873671008		Corrected to:	0873671008
  • All hyphens are deleted: 
	  Original:  1-873671-008		Corrected to:	1873671008
  • A lowercase x is converted to uppercase: 
	  Original:  187367100x		Corrected to:	187367100X
  • If ISBN is 13 digits, MARS 2.0 programs will verify that the first 3 digits are 978 or 979.
  • As an optional service, MARS 2.0 programs will correct the order of the ISBN (i.e. pairs of 13/10 and 13/10)
  • As an optional service, MARS 2.0 programs will convert ISBN-10 to ISBN-13 (includes check-sum value for both 10 and 13 length ISBNs): 
	  Original:  1873671008		Corrected to:	9781873671000
  • If MARS 2.0 programs cannot correct the format of the ISBN in the 020 $a (e.g., there are 11 digits), the 020 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.

Historical fact

The structure of the ISBN has changed over the past thirty years. Prior to 1977, the 020 field was not repeatable and multiple ISBNs and related information were placed in repeated subfields. Older bibliographic records may still have multiple ISBNs in a single 020 field rather than in multiple 020 fields. January 1, 2007 marked the final date for fully adopting ISBN-13. Between 2005 and 2008, publishers were encouraged to supply both an ISBN-10 and an ISBN-13 for the same manifestation, based on guidelines issued by the International ISBN Agency (IIA). The Library of Congress began accommodating ISBN-13 on October 1, 2004. At the beginning of 2007 is when publishers were expected to supply only ISBN-13.

Ordering 020 fields

LC will accept both an ISBN-13 and an ISBN-10 for the same manifestation. These numbers are shown by publishers according to guidelines issued by the IIA, which call for grouping the pairs of ISBNs by manifestation. In printed products the ISBN-13 appears first, and each number is preceded by a print constant as in the following example:

	  ISBN-13:  978-1-873671-00-0
	ISBN-10:  1-873671-008

Repeating 020 subfields

MARS 2.0 Update processing validates an 020 field for correct subfield repeatability. If the 020 field contains multiple $a, each $a is placed in a separate 020 field:

	  020 $a 11111111 $a 22222222
		Corrected to:
	020 $a 11111111
	020 $a 22222222

Binding information in 020 fields

Prior to 1978, binding information was placed in a $b. Older bibliographic records may have binding information in a $b rather than as a parenthetical qualifier in the $a.

If the 020 field contains a $b and an 020 $a exists:

  • $b delimiter and subfield code are deleted
  • 020 $b data is enclosed in parentheses
  • A blank is inserted at the end of the immediately preceding 020 $a data
  • 020 $b data, enclosed in parentheses, is moved after the blank at the end of the 020 $a data 
	  Original:  020 $a 1873671008 $b pbk.	Corrected to:  020 $a 1873671008 (pbk.)

020 with missing $a

If the 020 field contains a $b and no 020 $a exists, the $b code will be changed to $c:

	  020 $b pbk.
		Corrected to:
	020 $c pbk.

020 with multiple $c

If the 020 field contains multiple $c, each $c is placed in a separate 020 field:

	  020 $c 4.95 (lib. bdg.) $c 3.60 (pbk.)
		Corrected to:
	020 $c 4.95 (lib. bdg.)
	020 $c 3.60 (pbk.)

020 with multiple $a and $c

MARS 2.0 programs correctly handle 020 fields with multiple $a and $c:

	  020 $a 11111111 $c 4.95 $a 22222222 $c 3.60 $c 8.97 $b pbk.
		Corrected to:
	020 $a 11111111 $c 4.95
	020 $a 22222222 $c 3.60
	020 $c 8.97 (pbk.)

022 Field

MARS 2.0 Update processing can validated the format of the ISSN in field 022 $a. Some automated systems do not index an ISSN if the format is invalid. A valid ISSN in field 022 $a has the following structure: 4 digits, hyphen, 4 digits (or digits and an X):

	  1234-1234
	1234-123X

If the ISSN in field 022 $a does not have the valid structure, MARS 2.0 programs attempt to correct it by making these conversions:

  • If the ISSN has no hyphen, adds a hyphen between the fourth and fifth digits: 
	  Original:  12345678			Corrected to:  1234-5678
  • Converts a lowercase x to uppercase: 
	  Original:  1234-567x			Corrected to:  1234-567X
  • If MARS 2.0 programs cannot correct the format of the ISSN in the 022 $a (e.g., there are 9 digits), the 022 $a code is changed to $z and a report is generated. See report R50 in Step 5 for more information about this report.

034 Field

MARS 2.0 Update processing can validate field 034 CMD (Coded Mathematical Data) for correct format. If the 034 field first indicator has value 2 and the 034 field contains multiple $a, MARS 2.0 Update processing:

  • Places each $a in a separate 034 field
  • Changes each 034 field first indicator to value 1 
	  034 2_$a a $b 100000 $a a $b 120000
		Corrected to:
	034 1_$a a $b 100000
	034 1_$a a $b 120000

Historical fact

First indicator value 2 became obsolete when field 034 was made repeatable in 1982. Older bibliographic records may still have first indicator value 2.

links

2.1 - 2.2 - 2.3 - 2.4 - 2.5 - 2.6 - 2.7
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
Retrieved from "https://ac.bslw.com/community/wiki/index.php?title=RDA_2.1&oldid=2756"