MARC Report 253: Cataloging Check Changes

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

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.


Back To Top

Added checks

%t: Check subfield order     (AACR and RDA)
%t: When both subfields $e and $0 are present, subfield $e should precede subfield $0.

%t: Needs ending punct.     (AACR and RDA)
%t: Although the number and code fields do not usually end with punctuation, this field is an exception. If you want to turn off this message, go to the Cataloging Checks page of the options and unselect the option named ”… at the end of fields 01X-09X”

343: End of field punct. needed     (AACR and RDA)
343 (Planar Coordinate Data) ends with a period. A semicolon (;) is used to separate each subfield.

Back To Top

Deleted checks

Back To Top

Modified Flags

Back To Top

Modified Brief Messages

%t: Indicator 1 should be '1'     (AACR and RDA)       Message changed from: %t: Check indicator 1
%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'.

Back To Top

Modified Notes

%t: Check Indicator 1     (AACR and RDA)       Note changed
To: %t: If the name in subfield $a is a forename, or name consisting of words, initials, letters, etc., formatted in direct order, then Indicator 1 should be coded '0'. If, on the contrary, the name consists only of a surname (eg. $aSeuss,$cDr.), then Indicator 1 = '1' is correct. If you are not sure about the type of name, check the coding for the heading in your national authority file (https://viaf.org/)
From: If the name in tag %t is a forename, or name consisting of words, initials, letters, etc., formatted in direct order, then indicator 1 should be coded '0'. If, on the contrary, the name consists only of a surname (eg. $aSeuss,$cDr.), then I1='1' is correct.

740: Analytic or 246?     (AACR and RDA)       Note changed
To: Tag 740 indicator 2 is not coded 2 for an analytic. Change to 2 if the heading is an analytic, change tag to 246 and fix indicators if heading is not an analytic (i.e. a variant title).
From: The 740 indicator 2 is not coded 2 for an analytic. Change to 2 if the heading is an analytic, change tag to 246 and fix indicators if heading is not an analytic (i.e. a variant title).

760: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 760 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 760 is not going to make the same note that is already in the 580.
From: The 760 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 760 is not going to make the same note that is already in the 580.

762: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 762 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 762 is not going to make the same note that is already in the 580.
From: The 762 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 762 is not going to make the same note that is already in the 580.

765: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 765 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 765 is not going to make the same note that is already in the 580.
From: The 765 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 765 is not going to make the same note that is already in the 580.

767: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 767 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 767 is not going to make the same note that is already in the 580.
From: The 767 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 767 is not going to make the same note that is already in the 580.

770: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 770 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 770 is not going to make the same note that is already in the 580.
From: The 770 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 770 is not going to make the same note that is already in the 580.

772: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 772 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 772 is not going to make the same note that is already in the 580.
From: The 772 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 772 is not going to make the same note that is already in the 580.

773: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 773 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 773 is not going to make the same note that is already in the 580.
From: The 773 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 773 is not going to make the same note that is already in the 580.

774: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 774 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 774 is not going to make the same note that is already in the 580.
From: The 774 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 774 is not going to make the same note that is already in the 580.

775: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 775 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 775 is not going to make the same note that is already in the 580.
From: The 775 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 775 is not going to make the same note that is already in the 580.

776: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 776 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 776 is not going to make the same note that is already in the 580.
From: The 776 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 776 is not going to make the same note that is already in the 580.

777: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 777 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 777 is not going to make the same note that is already in the 580.
From: The 777 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 777 is not going to make the same note that is already in the 580.

780: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 780 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 780 is not going to make the same note that is already in the 580.
From: The 780 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 780 is not going to make the same note that is already in the 580.

785: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 785 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 785 is not going to make the same note that is already in the 580.
From: The 785 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 785 is not going to make the same note that is already in the 580.

786: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 786 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 786 is not going to make the same note that is already in the 580.
From: The 786 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 786 is not going to make the same note that is already in the 580.

787: Ind 1 = 0 and 580?     (AACR and RDA)       Note changed
To: Tag 787 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 787 is not going to make the same note that is already in the 580.
From: The 787 indicator 1 is coded to make a note, but a 580 note is already present. Check that the 787 is not going to make the same note that is already in the 580.

%t: End of field punct. needed     (AACR and RDA)       Note changed
To: %t (Personal name heading): ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a '?', '-', or ')' ) at the end of this heading. If the final subfield is numeric (eg. $0, $1, $2, etc.), the closing punctuation precedes it.
From: %t (Personal name heading): ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a '?', '-', or ')' ) at the end of this heading. If the final subfield is $0, $2, $3, $4, or $5, the closing punctuation precedes it.

%t: End of field punct. needed     (AACR and RDA)       Note changed
To: Tag %t: ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a closing paren, '!', '?', or '-') at the end of this heading. If the final subfield is numeric (eg. $0, $1, $2, etc.), the closing punctuation precedes it.
From: Tag %t: ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a closing paren, '!', '?', or '-') at the end of this heading. If the final subfield is $0, $2, $3, $4, or $5, the closing punctuation precedes it.

%t: End of field punct. needed     (AACR and RDA)       Note changed
To: Tag %t: ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a closing paren, '!', '?', or '-') at the end of this heading. If the final subfield is numeric (eg. $0, $1, $2, etc.), the closing punctuation precedes it.
From: Tag %t: ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a closing paren, '!', '?', or '-') at the end of this heading. If the final subfield is $0, $2, $3, $4, or $5, the closing punctuation precedes it.

%t: End of field punct. needed     (AACR and RDA)       Note changed
To: In a name/titIe heading, ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a closing paren, '!', '?', or '-') after the title. If the final subfield is numeric (eg. $0, $1, $2, etc.), the closing punctuation precedes it.
From: In a name/titIe heading, ISBD punctuation requires a closing mark of punctuation (a period, unless the field ends in a closing paren, '!', '?', or '-') after the title. If the final subfield is $0, $2, $3, $4, or $5, the closing punctuation precedes it.

%t: Should not end in punct.     (AACR and RDA)       Note changed
To: Tag %t does not end with a closing mark of punctuation unless the last word in the field contains it (as in an abbreviation, initial, etc.)
From: 856 (Electronic location and access): This field does not end with a closing mark of punctuation unless the last word in the field contains it (as in an abbreviation, initial, etc.)

253/ccs_changes.txt · Last modified: 2019/07/25 10:05 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed