MARC Report 241: Cataloging Check Changes

This page is produced by an automated comparison of the current cataloging checks (241) with those of the previous version (240). 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: Ellipsis requires blank     (RDA Only)
The filing indicator did not validate because a blank is required after an ellipsis (…) that indicates a mark of omission. Add the blank and check the indicator. (Set the indicator to skip the ellipsis and the first word, if it is an initial article). But, if the ellipsis is transcribed from the resource, and the resource does not show an ending blank space, then ignore this message.

%t: Carriage return in data     (AACR and RDA)
The data for this field includes a carriage return (x0D) or line feed (x0A) or both (Windows end-of-line). These characters are not valid in MARC–delete the offending character(s). Because this problem may be difficult to see in the default view, switch to Text view (tabs on top left) to identify and fix the problem.

001: Check 'on' number format     (AACR and RDA)
The 001 (Control number) contains an invalid OCLC number–numbers prefixed with 'on' must contain 10 or more digits and may not begin with a zero. Fix the number, or change the 001 to a local number and the 003 to your local control number ID. For more information refer to: http://www.oclc.org/batchload/controlnumber.en.html

001: Check 'ocm' number format     (AACR and RDA)
The 001 (Control number) contains an invalid OCLC number–numbers prefixed with 'ocm' should contain 8 digits, right-justified with leading zeroes. Fix the number, or change the 001 to a local number and the 003 to your local control number ID. For more information refer to: http://www.oclc.org/batchload/controlnumber.en.html

%t: Need comma before Subf $e     (AACR and RDA)
%t: When a relator term (subfield $e) is repeated for a name, a comma, with no subsequent blank spaces, should be used to separate the repeated relator terms.

%t: Need comma before Subf $e     (AACR and RDA)
%t: When a relator term (subfield $e) is repeated for a corporate name, a comma, with no subsequent blank spaces, should be used to separate the repeated relator terms.

%t: Blank space before ellipsis     (RDA Only)
The %t tag ends with an ellipsis; if the ellipsis indicates a mark of omission, then it should be preceded by a single blank space–add a blank space before the three periods. If the ellipsis is transcribed from the resource, however, and the resource does not show a preceding blank space, then ignore this message.

%t: Need blank before '…'     (RDA Only)
The %t tag contains an ellipsis within the data (i.e., not at the end the field or subfield); if the ellipsis indicates a mark of omission, then it should be preceded by a single blank space–add a blank space before the three periods. If the ellipsis is transcribed from the resource, however, and the resource does not show a preceding blank space, then ignore this message.

%t: Need blank after '…'     (RDA Only)
The %t tag contains an ellipsis within the data (i.e., not at the end the field or subfield); if the ellipsis indicates a mark of omission, then it should be followed by a single blank space–add a blank space after the three periods. If the ellipsis is transcribed from the resource, however, and the resource does not show a ending blank space, then ignore this message.

Back To Top

Deleted checks

008/11: Check © date in 260$c     (AACR and RDA)
008/06 (Type of date) is coded 't' (Publication date and copyright date), so Date 2 must match a copyright date in the 260 $c; but there does not appear to be such a date present, or the dates do not match. Watch out for 'c' instead of the copyright symbol or complete word to indicate a copyright date.

%t: Ellipsis     (AACR and RDA)
The %t field contains a broken ellipsis near position %p.

264: Publ or Prod data needed     (None)
264 Indicator 2 = 1 (Publication) data or 264 Indicator 2 = 0 (Production) data must be present in an RDA record.

338: 'object' needs 000/06 'r'     (AACR and RDA)
338 (Carrier type) contains the term 'object' in 338$a or code 'nr' in 338$b and so requires a corresponding 000/06 (Type of record) code 'r' (Three-dimensional artifact or naturally occurring object). See: http://www.loc.gov/standards/valuelist/rdacarrier.html

Back To Top

Modified Flags

%t: Ellipsis requires blank       Flag changed to: AACR Only       Flag was: AACR and RDA
The program was unable to validate the filing indicator because a blank is required after an ellipsis (…). Add the blank and check the indicator. (Set the indicator to skip the ellipsis and, if it is an initial article, the first word.)

000/18: 'i' should be 'a'       Flag changed to: None       Flag was: AACR Only
000/18 (Descriptive cataloging form) is coded 'i' (ISBD punctuation included), but this position should be coded 'a' (AACR 2), since 040 subfield $e (Description conventions) is coded 'aacr'–unless this is a 'hybrid record' (a mix of AACR and RDA).

245: $c Don't use [and others]       Flag changed to: None       Flag was: AACR Only
245 subfield $c (Statement of responsibility, etc.): AACR does not allow the use of phrases such as '[and others]', '[and other authors]', etc. Enter the abbreviation '[et al.]' instead.

250: $a use '1st'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'First' as '1st'

250: $a use '2nd'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Second' as '2nd'

250: $a use '3rd'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Third' as '3rd'

250: $a use '4th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Fourth' as '4th'

250: $a use '5th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Fifth' as '5th'

250: $a use '6th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Sixth' as '6th'

250: $a use '7th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Seventh' as '7th'

250: $a use '8th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Eighth' as '8th'

250: $a use '9th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Ninth' as '9th'

250: $a use '10th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Tenth' as '10th'

250: $a use '11th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Eleventh' as '11th'

250: $a use '12th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Twelfth' as '12th'

250: $a use '13th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Thirteenth' as '13th'

250: $a use '14th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Fourteenth' as '14th'

250: $a use '15th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Fifteenth' as '15th'

250: $a use '16th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Sixteenth' as '16th'

250: $a use '17th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Seventeenth' as '17th'

250: $a use '18th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Eighteenth' as '18th'

250: $a use '19th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Nineteenth' as '19th'

250: $a use '20th'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Twentieth' as '20th'

250: $a use 'ed.'       Flag changed to: None       Flag was: AACR Only
250 subfield $a (Edition statement): AACR says: abbreviate 'Edition' as 'ed.'

264: Field is not used for AACR       Flag changed to: None       Flag was: AACR Only
264 field(s) (Production, Publication, Distribution, Manufacture, and Copyright Notice) are not appropriate in an AACR record (040 $e aacr, or no 040 $e) for a single-part monograph; move Publication, etc. data to a combined 260 (Publication, Distribution, etc.) field.

260: $b Do not begin with 'The '       Flag changed to: None       Flag was: AACR Only
260 subfield $b (Name of publisher, etc.) must not begin with the word 'The'. Delete this initial article from the name of the publisher (eg. 'The World Bank' should be 'World Bank'), or use the actual name instead of a shortened form (eg. 'The Dept.' should be 'Dept. of Labour.')

260: $a Use '[S.l.]'       Flag changed to: None       Flag was: AACR Only
260 subfield $a (Place of publication, etc.): AACR does not use '[Place of publication not identified]'. If the place of publication is unknown, use '[s.l.]'. For example: $a[S.l.] :$bInsight Press,$c1981. (Capitalize the 'S' when it begins the publication statement).

260: $b Use '[s.n.]'       Flag changed to: None       Flag was: AACR Only
260 subfield $b (Name of publisher, etc.): AACR does not use '[Name of publisher not identified]'. If the publisher of a resource is unknown, use '[s.n.]'. For example: $aLondon :$b[s.n.],$c1889-1912.

260: $c Guess a date       Flag changed to: None       Flag was: AACR Only
260 subfield $c (Date of publication, etc.): AACR does not use '[Date of publication not identified]'. If the date of publication is unknown, we must still add a date even if we have to guess at one (AACR2R 1.4F7).

260: $c invalid copyright symbol       Flag changed to: None       Flag was: AACR Only
260 subfield $c (Date of publication, etc.), contains a symbol of some sort before a date; this is not an RDA record (no 040$e) and AACR does not allow a copyright (or phonogram) symbol before a date; so, change the symbol to a 'c' (or 'p', if applicable).

260: $c do not use 'copyright'       Flag changed to: None       Flag was: AACR Only
260 subfield $c (Date of publication, etc.), contains the term 'copyright' before a date; this is not an RDA record (no 040$e) and AACR does not allow this term before a copyright date; so, change the term to a 'c'.

264: Field is not used for AACR       Flag changed to: None       Flag was: AACR Only
264 field(s) (Production, Publication, Distribution, Manufacture, and Copyright Notice) are not appropriate in an AACR record (040 $e aacr, or no 040 $e) for a multi-part monograph, serial, or integrating resource, except for changed publication data (Indicator 1 = '2' or '3') in updated records; move 'earliest' Publication, etc. data to a combined 260 (Publication, Distribution, etc.) field.

260: $c has no date       Flag changed to: AACR and RDA       Flag was: RDA Only
260 subfield $c (Date of publication, etc.) contains no text resembling a date (YYYY or Roman numerals). Check whether this subfield $c has been miscoded, and should be coded as another subfield. If the subfield contains a chronogram as a date, change it to Arabic–LC PCC PS 2.8.6.4

264: $c Invalid copyright symbol       Flag changed to: None       Flag was: AACR and RDA
264 subfield $c (Date of publication, etc.), contains a symbol of some sort before a date; this is not an RDA record (no 040$e) and AACR does not allow a copyright (or phonogram) symbol before a date; so, change the symbol to a 'c' (or 'p', if applicable).

300: $a does not match Rec Type       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) does not match the 000/06 (Type of record) code, which should be: g,i,j,o for proj. med, sound rec., or kit. Either change the Type code or check the appr. AACR ch. (.5) for the correct way to enter the 300 $a for the material.

300: $a does not match Bib Level       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) does not appear to match the 000/07 (Bibliographic Level) 's'. If a print item is being cataloged as a serial, then the 300 $a should contain 'v.' (AACR 12.5B), or an appropriate electronic resource SMD–not a common usage term (A9.5)

300: $a does not match Bib Level       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) does not appear to match the 000/07 (Bibliographic Level) 's'. If a non-print item is being cataloged as a Continuing Resource (serial), then the 300 $a should contain a plural form of the specific material designation (AACR 12.5B)

300: $a check SMD–Score       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) might not be entered correctly for this score. See AACR2R 5.5 for instructions.

300: $a check SMD–proj. graphic       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) might not be entered correctly for this projected graphic. See AACR2R 7.5 or 8.5 for instructions.

300: $a check SMD–SR       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) might not be entered correctly for this sound recording. See AACR2R 6.5 for instructions.

300: $a check SMD–ER       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) might not be entered correctly for this electronic resource. See AACR2R 9.5 for instructions.

300: $a does not match Rec Type       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) does not appear to match the 000/06 (Type of record) coded 'r' for artifacts or naturally occurring objects. See AACR Ch. 10.5 for how to describe these materials.

300: $a does not match Rec Type       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) does not appear to match the 000/06 (Type of record) coded 'k' for two-dimensional nonprojectable graphical materials. See AACR Ch. 8.5 for how to describe these materials.

300: $a does not match Rec Type       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) does not appear to match the 000/06 (Type of record) coded 'e' or 'f' for cartographic materials. See AACR Ch. 3.5 for how to describe these materials.

300: $a use 'p.'       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent): under AACR, we abbreviate 'pages' as 'p.'; so change 'page' or 'pages' to 'p.'

300: $b use 'port.'       Flag changed to: None       Flag was: AACR Only
300 subfield $b (Other physical details): under AACR, we abbreviate 'portrait' or 'portraits' as 'port.' or 'ports.' (with a period), so change 'portrait' or 'portraits' to 'port.' or 'ports.'

300: $b use 'ill.'       Flag changed to: None       Flag was: AACR Only
300 subfield $b (Other physical details): under AACR, we abbreviate 'illustration(s)' as 'ill.'; so change 'illustration' or 'illustrations' to 'ill.'

300: $a use 'ill.'       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent): under AACR, we abbreviate 'illustration(s)' as 'ill.'; so change 'illustration' or 'illustrations' to 'ill.'

300: $b use 'col.'       Flag changed to: None       Flag was: AACR Only
300 subfield $b (Other physical details): under AACR, we abbreviate 'color/colour' as 'col.'; so change 'color' or 'colour' to 'col.'

300: $a use 'v.'       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent): under AACR, we abbreviate 'volume' or 'volumes' as 'v.'; so change 'volume' or 'volumes' to 'v.'

300: $b needs 'ports.'       Flag changed to: None       Flag was: AACR Only
300 subfield $b (Other physical details) needs 'port.' or 'ports.', since 008/18-21 (Illustrations) is coded 'c' (Portraits); e.g., $bill., port. Check the item and either provide 300$b details, or change the coding in 008/18-21 to blanks.

300: $a check SMD–BK       Flag changed to: None       Flag was: AACR Only
300 subfield $a (Extent) might not be entered correctly for this book or manuscript. See AACR2R 2.5 for instructions.

377: Not used in bib records       Flag changed to: None       Flag was: AACR and RDA
377 (Associated language) is used in an Authority record for an Expression; it is not intended for use in a Bibliographic record unless you are using that record to represent a Work or Expression with no manifestation information (i.e, record contains only Work or Expression data)

380: Not used in bib records       Flag changed to: None       Flag was: AACR and RDA
380 (Form of work) is used in an Authority record for a Work; it is not intended for use in a Bibliographic record unless you are using that record to represent a Work or Expression with no manifestation information (i.e, record contains only Work or Expression data)

381: Not used in bib records       Flag changed to: None       Flag was: AACR and RDA
381 (Other Distinguishing Characteristics of Work or Expression) is used in an Authority record for a Work or an Expression; it is not intended for use in a Bibliographic record unless you are using that record to represent a Work or Expression with no manifestation information (i.e, record contains only Work or Expression data)

383: Not used in bib records       Flag changed to: None       Flag was: AACR and RDA
383 (Numeric Designation of Musical Work) is used in an Authority record for a Work or an Expression; it is not intended for use in a Bibliographic record unless you are using that record to represent a Work or Expression with no manifestation information (i.e, record contains only Work or Expression data)

384: Not used in bib records       Flag changed to: None       Flag was: AACR and RDA
384 (Key) is used in an Authority record for a Work or an Expression; it is not intended for use in a Bibliographic record unless you are using that record to represent a Work or Expression with no manifestation information (i.e, record contains only Work or Expression data)

504: Use 'p.'       Flag changed to: None       Flag was: AACR Only
504 (Bibliography, Etc. Note) under AACR2, we abbreviate 'pages' as 'p.'; so change 'page' or 'pages' to 'p.'; e.g., $aIncludes bibliographical reference (p. 238-239)

%t: Blank space before ellipsis       Flag changed to: AACR Only       Flag was: AACR and RDA
The %t tag ends with an ellipsis. An ellipsis should be preceded by a single blank space. Add a blank space before the three periods

%t: Need blank before '…'       Flag changed to: AACR Only       Flag was: AACR and RDA
The %t tag contains an ellipsis within the data (ie. it does not begin the field or subfield) that is not preceded by a single blank space. Add the blank space before the three periods.

%t: Need blank after '…'       Flag changed to: AACR Only       Flag was: AACR and RDA
The %t tag contains an ellipsis within the data (ie. it does not ends the field or subfield) that is not followed by a single blank space. Add the blank space after the three periods.

336: but 040 $e not 'rda'       Flag changed to: None       Flag was: AACR Only
336 (Content Type) is not used in AACR/MARC. It is required in an RDA/MARC record, but this record does not appear to be an RDA record (040 $e is not 'rda'). If you are intentionally creating a 'hybrid' record, indicate your intention by adding 040$e aacr after $e rda.

337: but 040 $e not 'rda'       Flag changed to: None       Flag was: AACR Only
337 (MediaType) is not used in AACR/MARC. It is required in an RDA/MARC record, but this record does not appear to be an RDA record (040 $e is not 'rda'). If you are intentionally creating a 'hybrid' record, indicate your intention by adding 040$e aacr after $e rda.

338: but 040 $e not 'rda'       Flag changed to: None       Flag was: AACR Only
338 (Carrier Type) is not used in AACR/MARC. It is required in an RDA/MARC record, but this record does not appear to be an RDA record (040 $e is not 'rda'). If you are intentionally creating a 'hybrid' record, indicate your intention by adding 040$e aacr after $e rda.

Back To Top

Modified Brief Messages

001: Check 'ocn' number format     (AACR and RDA)       Message changed from: 001: Check new OCLC format
The 001 (Control number) contains an invalid OCLC number–numbers prefixed with 'ocn' must contain 9 digits and may not begin with a zero. Fix the number, or change the 001 to a local number and the 003 to your local control number ID. For more information refer to: http://www.oclc.org/batchload/controlnumber.en.html

Back To Top

Modified Notes

000/18: 'c' should be 'a'     (AACR Only)       Note changed
To: 000/18 (Descriptive cataloging form) is coded 'c' (ISBD punctuation included), but this position should be coded 'a' (AACR 2), since 040 subfield $e (Description conventions) is not present, or is coded 'aacr'–unless this is a 'hybrid record' (a mix of AACR and RDA).
From: 000/18 (Descriptive cataloging form) is coded 'c' (ISBD punctuation included), but this position should be coded 'a' (AACR 2), since 040 subfield $e (Description conventions) is coded 'aacr'--unless this is a 'hybrid record' (a mix of AACR and RDA).

000/18: 'i' should be 'a'?     (None)       Note changed
To: 000/18 (Descriptive cataloging form) is coded 'i' (ISBD punctuation included), but, since this appears to be an AACR record (040 $e is not present, or is coded 'aacr'), this leader position should probably be coded 'a' (AACR 2) unless this is an old pre-AACR record.
From: 000/18 (Descriptive cataloging form) is coded 'i' (ISBD punctuation included), but, since this appears to be an AACR record (040 $e is not present) this position should probably be coded 'a' (AACR 2) unless this is an old pre-AACR record.

003: Check Control number ID     (AACR and RDA)       Note changed
To: 003 (Control number ID) contains 'OCoLC' (the OCLC ID), but 001 (Control number) contains a number that is not an OCLC control number (the 001 prefix is not 'ocl', 'ocm', 'ocn', or 'on', or the numeric portion is missing or invalid). Fix the number, or change the 001 to a local number and the 003 to your local control number ID. See: http://www.oclc.org/batchload/controlnumber.en.html
From: 003 (Control number ID) contains 'OCoLC' (the OCLC ID), but 001 (Control number) contains a number that is not an OCLC control number (the 001 prefix is not 'ocm' or 'ocn'). Change the 001 to an OCLC number, or the 003 to your local ID, or disable this message if it is a system issue.

008/11: Check © date in 260$c     (AACR and RDA)       Note changed
To: 008/06 (Type of date) is coded 't' (Publication date and copyright date), so Date 2 must match a copyright date in the 260 $c; but there does not appear to be such a date present, or if there is, the dates do not match. Watch out for 'c' instead of the copyright symbol or complete word to indicate a copyright date.
From: 008/06 (Type of date) is coded 't' (Publication date and copyright date), so Date 2 must match a copyright date in the 260 $c; but there does not appear to be an added copyright date present in 260 $c, or if there is, it does not match 008/Date 2.

100: Ind 1 = '3' not used in AACR     (AACR Only)       Note changed
To: 100 (Main entry - Personal Name) Indicator 1 = 3 (Family name) is not used in an AACR record because a family cannot be a main entry or an added entry under AACR, it can only be a subject heading. If you want to add a family as a main entry, recatalog this entire record following RDA instructions.
From: 100 (Main entry - Personal Name) Indicator 1 = 3 (Family name) is not used in an AACR record because a family cannot be a main entry or an added entry under AACR, it can only be a subject heading

260: $a missing     (AACR Only)       Note changed
To: 260 subfield $a (Place of publication, etc.) is missing. This is OK if the item is not published, but if it is published, then find the item and add the missing data, even if only as “$a[S.l.]”, or ”;$a[s.n.]” (AACR); or “$a[Place of publication not identified]” or ”[publisher not identified]” (RDA)
From: 260 subfield $a (Place of publication, etc.) is missing. This is OK if the item is not published, but if it is published, then find the item and add the missing data, even if only as $a[S.l.], or ;$a[s.n.]

260: $b missing     (AACR Only)       Note changed
To: 260 subfield $b (Name of publisher, etc.) is missing. This is OK if the item is not published, but if it is published, find the item and add the missing data, even if only as :$b[s.n.] (AACR); or ”:$b[publisher not identified]” (RDA)
From: 260 subfield $b (Name of publisher, etc.) is missing. This is OK if the item is not published, but if it is published, find the item and add the missing data, even if only as :$b[s.n.]

260: $a [s.l.] must be [S.l.]     (AACR Only)       Note changed
To: 260 subfield $a (Place of publication, etc.) contains '[s.l.]'; because this $a is at the beginning of the field, that should be entered as ”[S.l.]” (AACR) or [Place of publication not identified] (RDA)
From: 260 subfield $a (Place of publication, etc.) contains '[s.l.]'; because this $a is at the beginning of the field, that should be entered as '[S.l.]'

264: Field is incompatible with 260     (AACR Only)       Note changed
To: 264 (Production, Publication, Distrib., Manufacture, and Copyright) and 260 (Publication, Distrib., etc.) cannot both be present in the same AACR record (040 $e aacr, or no 040 $e), except for changed publication data (Indicator 1 = '2' or '3') in updated multi-part monograph, serial, or integrating resource records; move this data to a general 260 field (AACR) or to an appropriate 264 field (RDA)
From: 264 (Production, Publication, Distribution, Manufacture, and Copyright Notice) and 260 (Publication, Distribution, etc.) should not both be present in the same AACR record (040 $e aacr, or no 040 $e), except for changed publication data (Indicator 1 = '2' or '3') in updated multi-part monograph, serial, or integrating resource records.

300: $b fix abbrev for 'port(s)'     (AACR Only)       Note changed
To: 300 subfield $b (Other physical details) contains 'port' or 'ports' (without a period); change to 'port.' or 'ports.' (with a period–AACR); or 'portrait' or 'portraits' (RDA)
From: 300 subfield $b (Other physical details) contains 'port' or 'ports' (without a period). If this is meant to be an abbreviation for 'portraits', change the 'port' or 'ports' to 'port.' or 'ports.' (with a period), as appropriate.

300: $a fix abbrev for 'p.'     (AACR Only)       Note changed
To: 300 subfield $a (Extent) contains ' p ' (without a period). If this is meant to be an abbreviation for 'pages', change the ' p ' to 'p.' (with a period–AACR); or 'page' or 'pages' (RDA)
From: 300 subfield $a (Extent) contains ' p ' (without a period). If this is meant to be an abbreviation for 'pages', change the ' p ' to 'p.' (with a period)

300: $a fix abbrev for 'v.'     (AACR Only)       Note changed
To: 300 subfield $a (Extent) contains ' v ' (without a period). If this is meant to be an abbreviation for 'volumes', change the ' v ' to 'v.' (with a period–AACR); or 'volume' or 'volumes' (RDA)
From: 300 subfield $a (Extent) contains ' v ' (without a period). If this is meant to be an abbreviation for 'volumes', change the ' v ' to 'v.' (with a period)

700: Ind 1 = '3' is not used in AACR     (AACR Only)       Note changed
To: 700 (Added entry - Personal Name) Indicator 1 = 3 (Family name) is not used in an AACR record because a family cannot be an added entry or a main entry under AACR, it can only be a subject heading. If you want to add a family as an added entry, recatalog this entire record following RDA instructions.
From: 700 (Added entry - Personal Name) Indicator 1 = 3 (Family name) is not used in an AACR record because a family cannot be an added entry or a main entry under AACR, it can only be a subject heading

008/32: Personal name missing     (AACR and RDA)       Note changed
To: 008/32 (Undifferentiated personal name): 'a' indicates that the personal name in 100 is a unique name, but there does not appear to be a 100 field with a personal name in the record. Code this position 'n' if the 1XX is not a personal name.
From: 008/32 (Undifferentiated personal name): 'a' indicates that the personal name in 100 is a unique name, but there is no 100 field. Code this position 'n' if the 1XX is not a personal name.

300: $b fix abbrev for 'ill.'     (AACR Only)       Note changed
To: 008/10 (Descriptive cataloging rules): LC uses only 'c' (AACR2), 'd' (AACR2 compatible) and 'n' (Not applicable). Records with 'a' or 'b' should be updated and changed to 'c' or 'd'.
From: 300 subfield $b (Other physical details) contains ' ill ' (without a period) or ' illus ' (with or without a period); change to 'ill.' (with a period)

300: $b fix abbrev for 'col.'     (AACR Only)       Note changed
To: 008/10 (Descriptive cataloging rules): code 'c' (AACR2) or 'd' (AACR2 compatible) identifies rules used to formulate name, name/title, or uniform title headings (100, 110, 111, 130) so one of these fields must be present.
From: 300 subfield $b (Other physical details) contains ' col ' (without a period). If this is meant to be an abbreviation for 'color', change the ' col ' to 'col.' (with a period)

245: $c Do not use '…'     (RDA Only)       Note changed
To: 245 subfield $c (Statement of responsibility, etc.): RDA does not allow the use of an ellipsis, or mark of omission, in transcribed fields. If the ellipsis is transcribed from the resource, however, then ignore this message.
From: 245 subfield $c (Statement of responsibility, etc.): RDA does not allow the use of an ellipsis, or mark of omission, in transcribed fields. RDA says: For transcribed elements, use only those abbreviations found in the sources of information for the element.

250: $b Do not use '…'     (RDA Only)       Note changed
To: 250 subfield $b (Edition statement): RDA does not allow the use of an ellipsis, or mark of omission, in transcribed fields. If the ellipsis is transcribed from the resource, however, then ignore this message.
From: 250 subfield $b (Edition statement): RDA does not allow the use of an ellipsis, or mark of omission, in transcribed fields. RDA says: For transcribed elements, use only those abbreviations found in the sources of information for the element.

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