MARC Report 259: Cataloging Check Changes

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

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 the source of this page.

<!– Id=25050004–> 505: $a not used with $g $r $t     (AACR and RDA)
505 (Formatted contents note): either a single subfield $a is used for all of the Contents information (and Ind 2 is blank), or the contents are recorded in repeating subfields $g, $r, and $t (and Ind 2 is 0).

<!– Id=20080101–> 008/06: Continuing resource code neede     (AACR and RDA)       Message changed from: 008/06: Continuing resource code needed
008/06 (Type of date/Publication status) should be coded for a continuing resource ('c', 'd' or 'u'), since 000/07 (Bibliographic level) is coded for a continuing resource ('s', 'b', or 'i'); either change the 008/06 code to 'c' (currently published) or 'd' (ceased publication) or 'u' (status unknown) and check your Date1 and Date2 dates, or change the 000/07 code.

<!– Id=20400004–> 040: Language validation not supported     (RDA Only)       Note changed
To: 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
From: 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.

<!– Id=20400005–> 040: Language validation not enabled     (RDA Only)       Note changed
To: 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
From: 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.

<!– Id=25070001–> 507: Prefer Tag 255 for Maps     (AACR and RDA)       Note changed
To: 507: Use field 507 for scale notes in pre-RDA and pre-AACR2 cataloging, or for the scale of graphic materials such as architectural drawings, technical drawings, models, art reproductions, and three-dimensional artifacts. For the scale notation of cartographic materials, cataloged under both AACR2 and RDA, use field 255 (Mathematical data associated with cartographic material, including a statemen
From: 507: Use field 507 for scale notes in pre-RDA and pre-AACR2 cataloging, or for the scale of graphic materials such as architectural drawings, technical drawings, models, art reproductions, and three-dimensional artifacts. For the scale notation of cartographic materials, cataloged under both AACR2 and RDA, use field 255 (Mathematical data associated with cartographic material, including a statement of scale, statement of projection, and/or a statement of bounding coordinates).

<!– Id=30400001–> 040: $e 'rda' but DRS=AACR     (AACR Only)       Note changed
To: 040 subfield $e (Description conventions) contains 'rda' (i.e., this is an RDA record), but your DRS Option (Description rules support) is set to 'AACR only', meaning you want to edit RDA records to AACR–if you want to do this: change 040$e 'rda' to 'aacr', and edit the record; otherwise, disable this message by changing your DRS option (on the 'Cataloging Check' page of the options) to 'Follow 0
From: 040 subfield $e (Description conventions) contains 'rda' (i.e., this is an RDA record), but your DRS Option (Description rules support) is set to 'AACR only', meaning you want to edit RDA records to AACR--if you want to do this: change 040$e 'rda' to 'aacr', and edit the record; otherwise, disable this message by changing your DRS option (on the 'Cataloging Check' page of the options) to 'Follow 040'.

<!– Id=31000003–> %t: Indicator 1 should be '1'     (AACR and RDA)       Note changed
To: %t: In name headings, Indicator 1 = 0 is used when the personal name in subfield $a consists of a forename, or words, phrases, initials, etc., formatted in direct order. The pattern in this field indicates that subfield $a contains a name formatted in inverted order (surname, forename); if this is indeed the case, then change Indicator 1 to '1'. If in doubt, check the coding of the heading in your
From: %t: In name headings, Indicator 1 = 0 is used when the personal name in subfield $a consists of a forename, or words, phrases, initials, etc., formatted in direct order. The pattern in this field indicates that subfield $a contains a name formatted in inverted order (surname, forename); if this is indeed the case, then change Indicator 1 to '1'. If in doubt, check the coding of the heading in your national authority file (https://viaf.org/)

<!– Id=32450002–> 245: Check ending punctuation     (AACR and RDA)       Note changed
To: 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
From: 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

<!– Id=40400002–> 040: $e not 'rda', but DRS=RDA     (RDA Only)       Note changed
To: 040 subfield $e (Description conventions) does not contain 'rda' (i.e., this is not an RDA record); but your DRS Option (Description rules support) is set to 'RDA only', meaning you want to treat all records as RDA. To do this: add 040 $e 'rda', delete 04 $e 'aacr' (if present), and edit the record; otherwise, disable this message by changing your DRS option (on the 'Cataloging Check' page of the
From: 040 subfield $e (Description conventions) does not contain 'rda' (i.e., this is not an RDA record); but your DRS Option (Description rules support) is set to 'RDA only', meaning you want to treat all records as RDA. To do this: add 040 $e 'rda', delete 04 $e 'aacr' (if present), and edit the record; otherwise, disable this message by changing your DRS option (on the 'Cataloging Check' page of the options) to 'Follow 040'.

<!– Id=41000003–> %t: Subf $e value not appropriate     (AACR and RDA)       Note changed
To: %t: Subfield $e contains a term from the MARC Relator terms list; but this term is not appropriate for use in 1XX unless used with another term that is appropriate in 1XX (based on the MARC-to-RDA alignment published here: http://www.rdaregistry.info/Maps/mapMRC2RDA.html ). Press <F7> to see a list of RDA terms that are appropriate for use in a 1XX. If the term is deemed to be correct, then recon
From: %t: Subfield $e contains a term from the MARC Relator terms list; but this term is not appropriate for use in 1XX unless used with another term that is appropriate in 1XX (based on the MARC-to-RDA alignment published here: http://www.rdaregistry.info/Maps/mapMRC2RDA.html ). Press to see a list of RDA terms that are appropriate for use in a 1XX. If the term is deemed to be correct, then reconsider whether the entity being related in this 1XX field might be a contributor (MARC 7XX) instead.

<!– Id=43360010–> 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 a
From: 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.

<!– Id=43370010–> 337: $a not same as $b     (RDA Only)       Note changed
To: 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
From: 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.

<!– Id=43380010–> 338: $a not same as $b     (RDA Only)       Note changed
To: 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, e
From: 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.

<!– Id=47000012–> %t: Subf $i is missing     (AACR and RDA)       Note changed
To: In the %t (Added entry), a 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 beginni
From: In the %t (Added entry), a 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 .

<!– Id=47600005–> %t: Subf $i is missing     (AACR and RDA)       Note changed
To: 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 be
From: 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 .