Table of Contents
MARC Report 245: Cataloging Check Changes
This page is produced by an automated comparison of the current cataloging checks (245) with those of the previous version (244). Message strings have been normalized to prevent slight differences in spacing, punctuation, etc., from being considered a change; but there has 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.
Added checks
<!– Id=26990001–> %t: Duplicate subject headings (AACR and RDA)
%t (Subject Added Entry): This record contains two or more subject headings with exactly the same tag, indicators and data.
<!– Id=32450001–> 245: Ending punct. repeated (AACR and RDA)
245 (Title statement) includes two pieces of ending punctuation at the end of the field.
<!– Id=46000001–> 6XX: if subf $t then no $e (AACR and RDA)
6XX (Subject Added entry) contains a name/title heading (i.e., $t is present). This heading refers to another resource, and not to a person, family, or corporate body associated with the resource: thus, subfield $e (Relator term) cannot be added to field. Delete the $e from this 6XX.
<!– Id=46000002–> 6XX: if subf $t then no $4 (AACR and RDA)
6XX (Subject Added entry field) contains a name/title heading (i.e., $t is present). This heading refers to another resource, and not to a person, family, or corporate body associated with the resource: thus, subfield $4 (Relator code) should not be added to field. Delete the $4 from this 6XX.
Deleted checks
<!– Id=29008002–> 008/10: NAF uses 'c' if no 664/6 (AACR and RDA)
008/10 (Descriptive cataloging rules): LC uses only 'c' (AACR2) if 1XX name headings are present and 664 (Complex See Reference–Name) or 666 (General Explanatory Reference–Name) are not present.
Modified Flags
Modified Brief Messages
<!– Id=30000036–> %t: Check repeated punct. (AACR and RDA) Message changed from: %t: Check repeated punctuation
The %t field contains a punctuation mark immediately followed by the same punctuation mark in subfield $%p. If this is a typo, correct the problem.
<!– Id=35306002–> 530: $d punct. must be ';' (AACR and RDA) Message changed from: 530: $d punc. must be ';'
530 $d: ISBD punctuation says subfield $d (Order number) must be preceded by a semicolon.
Modified Notes
<!– Id=41000001–> %t: Subf $e value not appropriate (AACR and RDA) Note changed
To: %t: Subfield $e contains a term defined in RDA Appendix I; but this term is not appropriate for use in a 1XX unless used with another Appendix I term that is appropriate in 1XX. Press <F7> to see a list of RDA terms that are appropriate for use in a 1XX. If the term is correct, then change the 1XX to a 7XX. (To configure 'appropriate' 1XX terms, goto the RDA page of the options.)
From: %t: Subfield $e contains a term that is found in RDA Appendix I but is not appropriate for use in a 1XX, except when added to another defined term that is appropriate. Press
<!– Id=41110001–> 111: Subf $j value not appropriate (AACR and RDA) Note changed
To: %t: Subfield $j contains a term that is found in RDA Appendix I but is not appropriate for use in a 1XX, except when added to another defined term that is appropriate. Press <F7> in the editor to see a list of defined terms from Appendix I that are appropriate for use in a 1XX. If the term is correct, then change the field to an appropriate 7XX instead of a 1XX.
From: %t: Subfield $j contains a term that is found in RDA Appendix I but is not appropriate for use in a 1XX, except when added to another defined term that is appropriate. Press