MARC Report 250: Cataloging Check Changes

This page is produced by an automated comparison of the current cataloging checks (250) with those of the previous version (249).

Message strings have been normalized to prevent slight differences in spacing, punctuation, etc., from being considered a change; but therehas been no attempt to otherwise edit this comparison.

Message Ids for each change listed below are available as comments in the markup; you may access this data by viewing or downloading thesource of this page.


Back To Top

Added checks

040: Language validation not supported     (RDA Only)
040 (cataloging source) subfield $b (Language of cataloging) is present in this record, but does not contain the code for a language supported by our RDA validation checks. The program will validate RDA strings against the default values, which are in English. If this record is intended for use in a catalog that uses one of our supported languages, then you may need to replace this record with one that is cataloged in that language.

040: Language validation not enabled     (RDA Only)
040 (cataloging source) subfield $b (Language of cataloging) is present in this record, and matches one of the language codes supported by our RDA validation checks, but that language has not been enabled in your options. The program will validate RDA strings against the default values, which are in English. To validate RDA strings in the language of cataloging, go to 'Options|RDA|Language support' and enable the language code on the form that appears.

040: Language validation not possible     (RDA Only)
040 (cataloging source) subfield $b (Language of cataloging) is present in this record, and matches one of the language codes supported by our RDA validation checks, but this validation requires unicode (UTF-8) and the record is encoded as MARC-8. The program will validate RDA strings against the default values, which are in English.

245: Check ending punctuation     (AACR and RDA)
245 (Title statement) MARC input conventions do not require an ending period if data already ends with final punctuation, which the MARC introduction explains is a period, a question mark, an exclamation mark, or a hyphen (https://www.loc.gov/marc/bibliographic/bdintro.html). However, if you are following the LC-PCC PS 1.7.1 at http://access.rdatoolkit.org/lcpschp1_lcps1-476.html, then ignore this message

300: $b spell out 'b&w'     (RDA Only)
300 subfield $b (Other physical details): under RDA, we do not abbreviate ‘black and white’ as 'b&w', so change the abbreviation to ‘monochrome’ or ‘black and white’ or some other term from a relevant vocabulary.

300: $b spell out 'sd'     (RDA Only)
300 subfield $b (Other physical details): under RDA, we do not abbreviate ‘sound’ as 'sd' (with or without a period), so replace the abbreviation with the full word.

337: $a not same as $b     (RDA Only)
In field 337 (Media Type), when both subfield $a (Media type term) and subfield $b (Media type code) are present, they should refer to the same type of content (e.g., $a video $b v; or $a video $a computer $b v $b c). Recording one type of media only in $a and another type only in $b in the same field is not good practice. Best practice is to use separate 337 fields to record data about different media types, especially if you are adding a URI in $0 for each media type.

337: Needs matching 007/00 'z'     (AACR and RDA)
337 (Media type) contains the term 'other' in 337$a or code 'x' in 337$b and so requires a corresponding 007/00 (Category of material) code 'z' (unspecified). See: http://www.loc.gov/standards/valuelist/rdamedia.html

338: $a not same as $b     (RDA Only)
In field 338 (Carrier Type), when both subfield $a (Carrier type term) and subfield $b (Carrier type code) are present, they should refer to the same type of carrier (e.g., $a online resource $b cr). Recording one type of carrier only in $a and another type only in $b in the same field is not good practice. Best practice is to use separate 338 fields to record data about different carrier types, especially if you are adding a URI in $0 for each carrier type.

Back To Top

Deleted checks

Back To Top

Modified Flags

Back To Top

Modified Brief Messages

007/03: Use fill ('|') not blanks     (AACR and RDA)       Message changed from: 007/03: Use fill (|) not blanks
007/03-04 (Class of braille writing) use two fill characters ('||') instead of blanks (##) when no attempt has been made to code.

264: _1 $c guess pubDate from © date     (AACR and RDA)       Message changed from: 264: _1 $c guess pubDate from cpyRt date
264 Indicator 2 = 1 subfield $c (Publication date) contains only a copyright date (preceded by 'copyright' or 'phonogram', or © or the phonogram symbol, or 'c' or 'p'); guess the publication date from the copyright date, and (optionally) add the copyright date again in a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol'.

264: _0 $c guess prodDate from © date     (AACR and RDA)       Message changed from: 264: _0 $c guess prodDate from cpyRt
264 Indicator 2 = 0 subfield $c (Production date) contains only a copyright date (preceded by 'copyright' or 'phonogram', or © or the phonogram symbol, or 'c' or 'p'); guess the production date from the copyright date, and (optionally) add the copyright date again in a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol'.

300: $b spell out 'col.'     (RDA Only)       Message changed from: 300: $b use 'color' or 'colour'
300 subfield $b (Other physical details): under RDA, we do not abbreviate 'color/colour' as 'col.' (with or without a period), so change the abbreviation to 'polychrome' or 'color' or 'colour' or some other term from a relevant vocabulary.

%t: Subf $i is missing     (AACR and RDA)       Message changed from: %t: $ubf $i is missing
In the %t (Linking entry field), subfield $i (relationship information) should be present in both AACR and RDA records when a title subfield is present. Relationship information describes the relationship between an work, expression, manifestation, or item to another work, expression, manifestation, or item. For a list of relationship terms valid in the current context, add a subfield $i to the beginning of the field and press <F7>.

Back To Top

Modified Notes

008/07: Do not use '|'     (AACR and RDA)       Note changed
To: 008/07-10 (Date 1) should not contain the fill character ('|'), since many systems use this date for retrieval purposes. Enter the date from 260$b (Date of publication).
From: 008/07-10 (Date 1) should not contain the fill character (|), since many systems use this date for retrieval purposes. Enter the date from 260$b (Date of publication).

008/07: If one '|', all '|||'     (AACR and RDA)       Note changed
To: 008/07-10 (Date 1) should not contain fill characters ('|'), but if fill is used, all four positions must contain the fill character.
From: 008/07-10 (Date 1) should not contain fill characters (|), but if fill is used, all four positions must contain the fill character.

008/11: Do not use '|'     (AACR and RDA)       Note changed
To: 008/11-14 (Date 2) should not contain the fill character ('|'); its better to just leave these positions blank
From: 008/11-14 (Date 2) should not contain the fill character (|); its better to just leave these positions blank

008/11: If one '|', all '|||'     (AACR and RDA)       Note changed
To: 008/11-14 (Date 2) should not contain fill characters ('|'), but if fill is used, all four positions must contain the fill character.
From: 008/11-14 (Date 2) should not contain fill characters (|), but if fill is used, all four positions must contain the fill character.

008/15: Do not use '|'     (AACR and RDA)       Note changed
To: 008/15-17 (Place of publication, production, or execution code) should not contain fill character ('|'), since many systems use the place code for retrieval purposes. Enter an appropriate Ctry code to correspond to the place of publication in 260$a
From: 008/15-17 (Place of publication, production, or execution code) should not contain fill character (|), since many systems use the place code for retrieval purposes. Enter an appropriate Ctry code to correspond to the place of publication in 260$a

008/15: If one '|', all '|||'     (AACR and RDA)       Note changed
To: 008/15-17 (Place of publication, production, or execution code) should not contain fill characters ('|'), but if fill is used, all three positions must contain the fill character.
From: 008/15-17 (Place of publication, production, or execution code) should not contain fill characters (|), but if fill is used, all three positions must contain the fill character.

008/35: Do not use '|'     (AACR and RDA)       Note changed
To: 008/35-37 (Language code) should not be coded with fill characters ('|'), since many systems use the language code for retrieval purposes.
From: 008/35-37 (Language code) should not be coded with fill characters (|), since many systems use the language code for retrieval purposes.

008/35: If one '|', all '|||'     (AACR and RDA)       Note changed
To: 008/35-37 (Language code) should usually not contain fill characters ('|'), but if fill is used, all three positions must contain the fill character.
From: 008/35-37 (Language code) should usually not contain fill characters (|), but if fill is used, all three positions must contain the fill character.

008/35: Use '|||' if non-MARC     (AACR and RDA)       Note changed
To: 008/35-37 (Language code) must contain fill characters ('|||') when the 041 indicates that a non-MARC code is being used to express the predominant language in an item (that is, when I2=7 and subf $2 is present).
From: 008/35-37 (Language code) must contain fill characters (|||) when the 041 indicates that a non-MARC code is being used to express the predominant language in an item (that is, when I2=7 and subf $2 is present).

%t: Subf $7 length incorrect     (AACR and RDA)       Note changed
To: Subfield $7 of the %t is a fixed length field and must be 15 characters long. Any positions not coded must be filled with a blank or the fill character ('|'). Also, the end of field punctuation must precede the $7 and not follow it.
From: Subfield $7 of the %t is a fixed length field and must be 15 characters long. Any positions not coded must be filled with a blank or the fill character (|). Also, the end of field punctuation must precede the $7 and not follow it.

008/07: LC uses only '|' here     (AACR and RDA)       Note changed
To: 008/07 (Romanization scheme): LC uses only the fill character ('|') here.
From: 008/07 (Romanization scheme): LC uses only the fill character (|) here.

008/08: LC uses only blank here     (AACR and RDA)       Note changed
To: 008/08 (Language of cataloging): LC does not code for Language of cataloging and so uses only a blank here. LC has not implemented the fill character ('|') here.
From: 008/08 (Language of cataloging): LC does not code for Language of cataloging and so uses only a blank here. LC has not implemented the fill character (|) here.

008/%p: LC does not use '|' here     (AACR and RDA)       Note changed
To: 008/%p: LC has not implemented the fill character ('|') here. Enter a valid code instead
From: 008/%p: LC has not implemented the fill character (|) here. Enter a valid code instead

008/28: LC uses only '|' here     (AACR and RDA)       Note changed
To: 008/28 (Type of government agency): LC uses only the fill character ('|') here.
From: 008/28 (Type of government agency): LC uses only the fill character (|) here.

336: $a not same as $b     (RDA Only)       Note changed
To: In field 336 (Content Type), when both subfield $a (Content type term) and subfield $b (Content type code) are present, they should refer to the same type of content (e.g., $a text $b txt; or $a text $a still image $b txt $b sti). Recording one type of content only in $a and another type only in $b in the same field is not good practice. Best practice is to use separate 336 fields to record data about different content types, especially if you are adding a URI in $0 for each content type.
From: In field 336 (Content Type), when subfield $a (Content type term) is present, the corresponding subfield $b (Content type code) should contain the code for the term in subfield $a. Press F1 and expand the 'codelist' section to view a list of valid codes for subf $b. Note: this message is optional; to turn it off, goto the RDA page of the options.

000/06: 'e' needs matching 336     (RDA Only)       Note changed
To: 000/06 (Type of record) code 'e' (Cartographic material) requires a corresponding cartographic term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: 000/06 (Type of record) code 'e' (Cartographic material) requires a corresponding cartographic term in 336$a or code in 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html

000/06: 't' needs matching 336     (RDA Only)       Note changed
To: 000/06 (Type of record) code 't' (Manuscript language material) requires a corresponding text or notated movement term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: 000/06 (Type of record) code 't' (Manuscript language material) requires a corresponding text or notated movement term in 336$a or code in 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html

000/06: 'c' needs matching 336     (RDA Only)       Note changed
To: 000/06 (Type of record) code 'c' (Notated music) requires a corresponding term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: 000/06 (Type of record) code 'c' (Notated music) requires a corresponding term in 336$a or code in 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html

007/00: 's' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 's' (sound recording) requires the term 'audio' in a 337$a or code 's' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 's' (sound recording) requires the term 'audio' in 337$a or code 's' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'c' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'c' (electronic resource) requires the term 'computer' in a 337$a or code 'c' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'c' (electronic resource) requires the term 'computer' in 337$a or code 'c' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'h' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'h' (microform) requires the term 'microform' in a 337$a or code 'h' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'h' (microform) requires the term 'microform' in 337$a or code 'h' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'g' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'g' (projected graphic) requires the term 'projected' in a 337$a or code 'g' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'g' (projected graphic) requires the term 'projected' in 337$a or code 'g' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'm' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'm' (motion picture) requires the term 'projected' in a 337$a or code 'g' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'm' (motion picture) requires the term 'projected' in 337$a or code 'g' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 't' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 't' (text) requires the term 'unmediated' in a 337$a or code 'n' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 't' (text) requires the term 'unmediated' in 337$a or code 'n' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'k' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'k' (non-projected graphic) requires the term 'unmediated' in a 337$a or code 'n' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'k' (non-projected graphic) requires the term 'unmediated' in 337$a or code 'n' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'v' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'v' (videorecording) requires the term 'video' in a 337$a or code 'v' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'v' (videorecording) requires the term 'video' in 337$a or code 'v' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

007/00: 'z' needs matching 337     (RDA Only)       Note changed
To: 007/00 (Category of material) code 'z' (unspecified) requires the term 'other' or 'unspecified' in a 337$a or code 'v' or 'x' in a 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 007/00 (Category of material) code 'z' (unspecified) requires the term 'other' or 'unspecified' in 337$a or code 'v' or 'x' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html

337: Needs matching 007/00 'z'     (AACR and RDA)       Note changed
To: 337 (Media type) contains the term 'unspecified' in 337$a or code 'z' in 337$b and so requires a corresponding 007/00 (Category of material) code 'z' (unspecified). See: http://www.loc.gov/standards/valuelist/rdamedia.html
From: 337 (Media type) contains the term 'other' or 'unspecified' in 337$a or code 'x' or code 'z' in 337$b and so requires a corresponding 007/00 (Category of material) code 'z' (unspecified). See: http://www.loc.gov/standards/valuelist/rdamedia.html

250/ccs_changes.txt · Last modified: 2017/12/29 11:27 by richard
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed