MARC Report 247: Cataloging Check Changes

This page is produced by an automated comparison of the current cataloging checks (247) with those of the previous version (246). 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

008/06: Check Date1/Date2 for 'b'     (AACR and RDA)
008/06 (Type of date) is coded 'b' when one or more dates associated with the item are Before Common Era (B.C.) dates. If this is really the case, then both Date1 and Date2 must contain 4 blank spaces, and the date(s) must be entered in tag 046 (Date1 goes in $b, and Date2 in $d).

008/06: Check Date2 for 'e'     (AACR and RDA)
008/06 (Type of date) is coded 'e' (Detailed date) when Date1 is coded for the year (yyyy), and Date2 is coded for the month and day (mmdd); If the day is unknown, enter a two-digit month in Date2 followed by 'uu'; if the item indicates only the month, append two blank spaces to the month in Date2.

008/06: Check Date2 for 'd'     (AACR and RDA)
008/06 (Type of date) is coded 'd' (Continuing resource ceased publication), indicating that Date1 contains the beginning date of publication and Date2 contains the date the item ceased to be published.

008/06: Check Date2 for 'm'     (AACR and RDA)
008/06 (Type of date) is coded 'm' (Multiple dates) when Date1 and Date2 contain the range of years of publication of a multipart item; Date1 contains the initial (or beginning) date and Date2 the terminal (or ending) date, or '9999' if the publication is ongoing.

008/06: Check Date1/Date2 for 'n'     (AACR and RDA)
008/06 (Type of date) is coded 'n' (Dates unknown; e.g. when no dates are given in field 260 or 264); in this case, both Date1 and Date2 contain 'uuuu'. If this is not the case, change the Type of date code to an appropriate value (http://www.loc.gov/marc/bibliographic/bd008a.html)

008/06: Check Date1/Date2 for 'q'     (AACR and RDA)
008/06 (Type of date) is coded 'q' (Questionable date) when the exact date for a single date item is not known, but a range of years for the date can be specified; enter the earliest possible date in Date1, and the latest possible date in Date2. Do not use 'uuuu' with Type of date 'q'.

008/06: Check Date1 for 's'     (AACR and RDA)
008/06 (Type of date) is coded 's' when Date1 consists of a known single date of distribution, publication, release, production, execution, writing, or a probable date that can be represented by four digits (but not 'uuuu').

008/06: Check Date2 for 't'     (AACR and RDA)
008/06 (Type of date) is coded 't' (Publication date and copyright date). In this case, the date of publication/release/production/execution is given in Date1 and a copyright notice date or phonogram copyright notice date is given in Date2 (do not use 'u' in Date2).

008/06: Continuing resource code needed     (AACR and RDA)
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.

008/06: Collection code required     (AACR and RDA)
008/06 (Type of date/Publication status) should be coded for a collection (‘i', or ‘k’), since 000/07 (Bibliographic level) is coded for a collection (’c’ or ‘d’); either change the 008/06 code to ‘i’ (Inclusive dates of collection) or ‘k’ (Range of years of bulk of collection) and check your Date1 and Date2 dates, or change the 000/07 code to one that is not for a collection.

008/06: Monographic code required     (AACR and RDA)
008/06 (Type of date/Publication status) should be coded for a monograph (‘b’, ‘e’, ‘m’, ‘n’, ‘p’, ‘q’, ‘r’, ‘s’, ‘t’), since 000/07 (Bibliographic level) is coded for a monograph (’m’); either change the 008/06 code and check your Date1 and Date2 dates, or change the 000/07 code to one that is not for a monograph (not ‘m’).

008/07: Missing Date1 and Date2     (AACR and RDA)
Both Date1 and Date2 are blank. This should only occur when the Type of date code is 'b', indicating a B.C. date that is coded in tag 046. If the date is completely unknown, or unknowable (as for a naturally occurring object), code Type of Date 'n', and enter 'uuuu' in Date1 and Date2. For more options, see: http://www.loc.gov/marc/bibliographic/bd008a.html

008/06: Check Date2 for 'i'     (AACR and RDA)
008/06 (Type of date) is coded 'i' (Inclusive dates of collection), indicating that Date1 and Date2 contain the inclusive dates applicable to a collection. If the inclusive dates are represented by a single year, that date is given in both Date1 and Date2.

008/06: Check Date2 for 'k'     (AACR and RDA)
008/06 (Type of date) is coded 'k' (Range of years of bulk of collection), indicating Date1 and Date2 contain the range of years applicable to most of the material in a collection. If the bulk dates are represented by only a single year, that date is given in both Date1 and Date2.

008/06: Check Date2 for 'p'     (AACR and RDA)
008/06 (Type of date) is coded 'p' (Different dates of distribution and production), indicating there is a difference between the distribution/release/issue date (Date1) and the date of production/recording (Date2). For more details, see: http://www.loc.gov/marc/bibliographic/bd008a.html

008/06: Check Date2 for 'r'     (AACR and RDA)
008/06 (Type of date) is coded 'r' (Reprint/reissue date and original date), indicating Date1 contains the date of reproduction or reissue, and Date2 contains the date of the original, if known. (Date1 or Date2 contains 'uuuu' if unknown). If multiple dates are available for the original publication, Date2 contains the earlier date.

%t: Subf $t expected     (AACR and RDA)
Linking tags (760-787) should contain a $t for the Title of the resource being referred to. Check the subfield $a to see if 1) it should be coded $t instead, or 2) a title has been appended to $a without being coded as such.

%t: Expression heading but Work 034     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 034 (Coded cartographic mathematical data) which is a Work element. Find or create an authority record for the Work, and move the 034 to it.

%t: Work heading but Expression 336     (None)
The heading in this authority record lacks any Expression elements, indicating that this heading is for a Work Authorized Access Point and is therefore a Work authority record; but the record contains a 336 (Content Type) which is an Expression element. Find or create an authority record for an Expression, and move the 336 to it.

%t: Expression heading but Work 370     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 370 (Place of origin of work) which is a Work element. Find or create an authority record for the Work, and move the 370 to it

%t: Work heading but Expression 377     (None)
The heading in this authority record lacks any Expression elements, indicating that this heading is for a Work Authorized Access Point and is therefore a Work authority record; but the record contains a 377 (Associated language) which is an Expression element. Find or create an authority record for an Expression, and move the 377 to it.

%t: Expression heading but Work 380     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 380 (Form of Work) which is a Work element. Find or create an authority record for the Work, and move the 380 to it.

%t: Expression heading but Work 382     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 382 (Medium of Performance) which is a Work element. Find or create an authority record for the Work, and move the 382 to it.

%t: Expression heading but Work 384     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 384 (Key) which is a Work element. Find or create an authority record for the Work, and move the 384 to it.

%t: Expression heading but Work 385     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 385 (Intended Audience) which is a Work element. Find or create an authority record for the Work, and move the 385 to it.

%t: Expression heading but Work 665     (None)
The heading in this authority record contains Expression elements, indicating that this heading is for an Expression Authorized Access Point and is therefore an Expression authority record; but the record contains a 665 (History reference) which is a Work element. Find or create an authority record for the Work, and move the 665 to it.

Back To Top

Deleted checks

Back To Top

Modified Flags

Back To Top

Modified Brief Messages

264: _4 Copyright needs ©date     (AACR and RDA)       Message changed from: 264: _4 Copyright needs ©date
264 Indicator 2 = 4 (Copyright notice date) requires a copyright date (preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol') in subfield $c (Date)

264: _1 $c guess pubDate from cpyRt date     (AACR and RDA)       Message changed from: 264: _1 $c guess pubDate from cpyRt da
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'.

Back To Top

Modified Notes

000/06: RecType not ok for 264_0     (AACR and RDA)       Note changed
To: 000/06 (Type of record) contains a code ('a', 'c', or 'e') that is not compatible with the use of a 264 field for Production data (Indicator 2 = 0). Either change the 264 Indicator 2 to ‘1’ (Publication data), or change the 000/06 to a code that is appropriate for manuscript material: 't' (text), 'd' (notated music), or 'e' (cartographic material).
From: 000/06 (Type of record) contains a code ('a', 'c', or 'e') that is not compatible with the use of a 264 field for Production data (Indicator 2 = 0). Either change the 264 Indicator 2 to ‘1’ (Publication data), or change the 000/06 to a code that is appropriate for manuscript material: 't' (text), 'd' (notated music), or 'e' (cartographic material).

001: New LCCN not normalized     (AACR and RDA)       Note changed
To: The 001 (Control number) contains a new (2001-) LCCN that should be normalized using the pattern '##yyyynnnnnn', where: '##' is two blank spaces or a lowercase, left-justified prefix; 'yyyy' is the year portion of the LCCN; 'nnnnnn' is a six-digit, zero-filled serial number. Examples: ' 2001000123', 'n 2001012345'. For complete documentation see: http://www.loc.gov/marc/lccn_structure.html
From: 001 (Contol number) contains a new (2001-) LCCN that must be normalized as '##nnnnnnnn': '##' (two blank spaces or a valid, lower case, left-justified prefix), 'nnnn' (four digits) 'nnnnnn' (6 digits, zero-filled), e.g., '##2001000123

010: New LCCN not normalized     (AACR and RDA)       Note changed
To: The 010 (LCCN) contains a new (2001-) LCCN that should be normalized using the pattern '##yyyynnnnnn', where: '##' is two blank spaces or a lowercase, left-justified prefix; 'yyyy' is the year portion of the LCCN; 'nnnnnn' is a six-digit, zero-filled serial number. Examples: ' 2001000123', 'n 2001012345'. For complete documentation see: http://www.loc.gov/marc/lccn_structure.html
From: 010 (LCCN) contains a new (2001-) LCCN that must be normalized as '##nnnnnnnn': '##' (two blank spaces or a valid, lower case, left-justified prefix), 'nnnn' (four digits) 'nnnnnn' (6 digits, zero-filled), e.g., '##2001000123).

008/11: Date2 does not match Date type     (AACR and RDA)       Note changed
To: 008/06 (Type of date) is coded with a value that indicates that a date, or '9999', or 'uuuu' must be present in 008/11-14 (Date 2). Either add a date, or '9999', or 'uuuu', to 008/11-14, or change the code in 008/06 to 's' (single date)
From: 008/06 (Type of date) is coded with a value that indicates that a date or 'uuuu' must be present in 008/11-14 ( Date 2). Either add a date, or 'uuuu', to 008/11-14, or change the code in 008/06 to 's' (single date)

040: Subf $b is not 'eng'     (AACR and RDA)       Note changed
To: 040 (cataloging source) subfield $b (Language of cataloging) is present in this record but is not coded ‘eng’. If this record is intended for use in an OPAC that uses English as its language, then you may need to replace this record with one that is cataloged in English.
From: 040 (cataloging source) subfield $b (Language of cataloging) is present in this record but is not coded ‘eng’. If this record is intended for use in an OPAC that uses English as its language, then you may need to replace this record with one that is cataloged in English.

100: 'editor' must be tagged 700     (AACR and RDA)       Note changed
To: 100 (Main entry - Personal Name) subfield $e (Relator term) contains ‘editor’; an editor relationship is not allowed in a 100; move the name of the editor to a 700 (Added entry - Personal Name) and change the first indicator of the 245 to ‘0’ (Title main entry)
From: 100 (Main entry - Personal Name) subfield $e (Relator term) contains ‘editor’; an editor relationship is not allowed in a 100; move the name of the editor to a 700 (Added entry - Personal Name) and change the first indicator of the 245 to ‘0’ (Title main entry)

264: _1 $c move cpyRt date to I2=4     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 1 subfield $c (Publication date) contains an added copyright date (preceded by 'copyright' or 'phonogram,' or © or the phonogram symbol, or 'c' or 'p'); move the copyright date to a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'
From: 264 Indicator 2 = 1 subfield $c (Publication date) contains an added copyright date (preceded by 'copyright' or 'phonogram,' or © or the phonogram symbol, or 'c' or 'p'); move the copyright date to a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'

264: _2 $c move cpyRt date to I2=4     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 2 subfield $c (Distribution date) contains an added copyright date (preceded by 'copyright' or 'phonogram,' or © or the phonogram symbol, or 'c' or 'p'); move the copyright date to a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'
From: 264 Indicator 2 = 2 subfield $c (Distribution date) contains an added copyright date (preceded by 'copyright' or 'phonogram,' or © or the phonogram symbol, or 'c' or 'p'); move the copyright date to a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'

264: _3 $c move cpyRt date to I2=4     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 3 subfield $c (Manufacturer date) contains a copyright date (preceded by 'copyright' or 'phonogram', or © or the phonogram symbol, or 'c' or 'p'); delete the copyright date, or (optionally) move it to 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'
From: 264 Indicator 2 = 3 subfield $c (Manufacturer date) contains a copyright date (preceded by 'copyright' or 'phonogram', or © or the phonogram symbol, or 'c' or 'p'); delete the copyright date, or (optionally) move it to 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'

264: _4 Copyright notice needs $c     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 4 (Copyright notice date) requires a subfield $c (Date), with a copyright date (preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol')
From: 264 Indicator 2 = 4 (Copyright notice date) requires a subfield $c (Date), with a copyright date (preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol')

264: _4 Copyright must have $c only     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 4 (Copyright notice date) can only contain a subfield $c (Date), with a copyright date (preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol')
From: 264 Indicator 2 = 4 (Copyright notice date) can only contain a subfield $c (Date), with a copyright date (preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol')

264: _4 Fix Copyright symbol     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 4 (Copyright notice date) subfield $c (Date) requires the copyright date to be preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol'.
From: 264 Indicator 2 = 4 (Copyright notice date) subfield $c (Date) requires the copyright date to be preceded by 'copyright' or 'phonogram' or © or the 'phonogram symbol'.

264: _0 $c move cpyRt date to I2=4     (AACR and RDA)       Note changed
To: 264 Indicator 2 = 0 subfield $c (Production date) contains an added copyright date (preceded by 'copyright' or 'phonogram', or © or the phonogram symbol, or 'c' or 'p'); move the copyright date to a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'
From: 264 Indicator 2 = 0 subfield $c (Production date) contains an added copyright date (preceded by 'copyright' or 'phonogram', or © or the phonogram symbol, or 'c' or 'p'); move the copyright date to a separate 264 Indicator 2 = 4 (Copyright notice date), preceded by either © or 'phonogram' or 'copyright'

264: _0 $c guess prodDate from cpyRt     (AACR and RDA)       Note changed
To: 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'.
From: 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'.

264: _0 No abbrev. when in [ ] in $a     (AACR and RDA)       Note changed
To: 264 subfield $a (Place of production) contains an abbreviation for a supplied place name–in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)
From: 264 subfield $a (Place of production) contains an abbreviation for a supplied place name--in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)

264: _1 No abbrev. when in [ ] in $a     (AACR and RDA)       Note changed
To: 264 subfield $a (Place of publication) contains an abbreviation for a supplied place name–in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)
From: 264 subfield $a (Place of publication) contains an abbreviation for a supplied place name--in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)

264: _2 No abbrev. when in [ ] in $a     (AACR and RDA)       Note changed
To: 264 subfield $a (Place of distribution) contains an abbreviation for a supplied place name–in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)
From: 264 subfield $a (Place of distribution) contains an abbreviation for a supplied place name--in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)

264: _3 No abbrev. when in [ ] in $a     (AACR and RDA)       Note changed
To: 264 subfield $a (Place of manufacture) contains an abbreviation for a supplied place name–in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)
From: 264 subfield $a (Place of manufacture) contains an abbreviation for a supplied place name--in square brackets (e.g., Paris [TX] or [Paris, TX]; spell out abbreviations in ‘supplied’ data (given in square brackets)

300: $a use 'unnumbered' not '[ ]'     (AACR and RDA)       Note changed
To: 300 subfield $a (Extent): under RDA, we do not use square brackets to indicate the number of unnumbered pages in a resource (e.g., [8] pages); use the term ‘unnumbered’ instead (e.g., 8 unnumbered pages)—see 3.4.5.3 for more examples.
From: 300 subfield $a (Extent): under RDA, we do not use square brackets to indicate the number of unnumbered pages in a resource (e.g., [8] pages); use the term ‘unnumbered’ instead (e.g., 8 unnumbered pages)—see 3.4.5.3 for more examples.

250: $a Check abbreviation 'ed.'     (RDA Only)       Note changed
To: 250 subfield $a (Edition statement): RDA says: do not use the abbreviation 'ed.' unless the abbreviation is found on the resource itself; if the word is spelled out on the item, then enter the word as it is spelled (eg. 'edition', 'edición', 'édition', etc.)
From: 250 subfield $a (Edition statement): RDA says: do not use the abbreviation 'ed.' unless the abbreviation is found on the resource itself; if the word is spelled out on the item, then enter the word as it is spelled (eg. 'edition', 'edición', 'édition', etc.)

264: Publ data is required in RDA     (RDA Only)       Note changed
To: 264 Indicator 2 = 1 (Publication data) is used in an RDA record when Leader/06 is NOT coded ‘d, f, p, or t’, indicating the record is for an published resource. Either change 264 Indicator 2 to ‘1’ (for publication data), or change Leader/06 to an appropriate code for the unpublished resource.
From: 264 Indicator 2 = 1 (Publication data) is used in an RDA record when Leader/06 is NOT coded ‘d, f, p, or t’, indicating the record is for an published resource. Either change 264 Indicator 2 to ‘1’ (for publication data), or change Leader/06 to an appropriate code for the unpublished resource.

264: Prod data is required in RDA     (RDA Only)       Note changed
To: 264 Indicator 2 = 0 (Production data) is used in an RDA record when Leader/06 is coded ‘d, f, p, or t’, indicating the record is for an unpublished resource. Either change 264 Indicator 2 to ‘0’ (for production data), or change Leader/06 to an appropriate code for the published resource.
From: 264 Indicator 2 = 0 (Production data) is used in an RDA record when Leader/06 is coded ‘d, f, p, or t’, indicating the record is for an unpublished resource. Either change 264 Indicator 2 to ‘0’ (for production data), or change Leader/06 to an appropriate code for the published resource.

247/ccs_changes.txt · Last modified: 2016/11/22 11:31 by richard
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed