RDA Cataloging Checks in version 236

Here is an incomplete of list of cataloging checks that have been added to support RDA MARC version 236 of MARC Report.

The overall application of the cataloging checks is now influenced by a new option named 'Description Rules support'. By default, this option looks at the 040 $e and then decides what cataloging checks to display for a record.

In addition, keep in mind that any cataloging check can now be:

1. turned off (None)
2. applied to all records (AACR and RDA)
3. applied to AACR records only (AACR Only)
4. applied to RDA records only (RDA Only)

by customizing them in the Cataloging Checks options. For details on the change made to the 'Enabled' column that makes this customization possible, please click here.

---

The following cataloging checks are, by default, set-up to run on AACR records only

040: subfield $e = 'rda'
040 (Cataloging source) subfield $e (Description conventions) contains the code 'rda'. Your current option for 'Description rules support' is set to 'AACR only' (on the Cataloging checks page), so no cataloging checks for RDA will be run.

336: subfield $e not 'rda' Field 336 (Content Type) is intended to support RDA in MARC, but this record does not appear to be an RDA record (040 $e is not 'rda').

337: subfield $e not 'rda' Field 337 (Media Type) is intended to support RDA in MARC, but this record does not appear to be an RDA record (040 $e is not 'rda').

338: subfield $e not 'rda' Field 338 (Carrier Type) is intended to support RDA in MARC, but this record does not appear to be an RDA record (040 $e is not 'rda').

The 33X messages are warnings, since these fields were designed for RDA MARC and are not needed in an AACR record

---

000/18: Check Desc. Cat. Form
Leader/18 (Descriptive cataloging form) contains code 'c' (ISBD punctuation omitted) or code 'i' (ISBD punctuation included). Both of these codes are intended to support RDA in MARC and should not be used in AACR2 records. If this record is indeed an AACR2 record, change Leader/18 to 'a' (AACR2).

260: Abbreviate subfield $a
Do not use the phrase '[Place of publication not identified]' in AACR records. If the place of publication is unknown, then the abbreviation 's.l.' should be entered in square brackets in 260 subfield $a. For example: $a[S.l.] :$bInsight Press,$c1981. (The 'S' is capitalized when it begins the publication statement).

260: Abbreviate subfield $b
Do not use the phrase '[Name of publisher not identified]' in AACR records. If the publisher of a resource is unknown, then the abbreviation 's.n.' should be entered in square brackets in 260 subfield $b. For example: $aLondon :$b[s.n.],$c1889-1912.

260: Abbreviate subfield $c
Do not use the phrase '[Date of publication not identified]' in AACR records. If the date of publication is not found on the item, note that in AACR2 we must still add a date even if we have to guess at one (AACR2R 1.4F7).

300: page(s) should be 'p.'
Do not use the terms 'page' or 'pages' in Tag 300 subfield $a (Physical description). In AACR2, this should be abbreviated as 'p.'; for example: $axii, 246 p., 32 p. of plates.

300: portrait(s) shld be 'port.'
Do not use the terms 'portrait' or 'portraits' in Tag 300 subfield $b (Other physical details). In AACR2, these terms should be abbreviated as 'port.' (singular) or 'ports.' (plural), respectively; for example: $axii, 246 p. :$b 1 port.

300: illustration shld be 'ill.'
Do not use the terms 'illustration' or 'illustrations' in tag 300 subfield $b (Other physical details). In AACR2, these terms should be abbreviated as 'ill.'; for example: $a40 p. :$bill.

300: illustration shld be 'ill.'
Do not use the terms 'illustration' or 'illustrations' in tag 300 subfield $a (Physical description). In AACR2, these terms should be abbreviated as 'ill.'; for example: $a74 p. of ill., 15 p. ;$c28 cm.

300: colo(u)r should be 'col.'
Do not use the terms 'color' or 'colour' in tag 300 subfield $b (Other physical details). In AACR2, these terms should be abbreviated as 'col.'; for example: $a40 p. :$bcol. ill. or: $a1 map :$bcol.

504: page(s) should be 'p.'
Do not use the terms 'page' or 'pages' in Tag 504 (Bibliography, etc., Note). In AACR2, this term should be abbreviated as 'p.'; for example: $aBibliography: p. 238-239.

---

The following cataloging checks are, by default, set-up to run on RDA records only

000/18: Check Desc. Cat. Form
Leader position 18 (Descriptive cataloging form) is coded 'a' (AACR 2), but 040 (Cataloging source) subfield $e (Description conventions used to create the record) is coded 'rda'. If the record is indeed a RDA/MARC record, 008/18 should be coded either 'i' (ISBD punctuation included), or 'c' (ISBD punctuation omitted).

040: subfield $e not 'rda'
040 (Cataloging source) subfield $e (Description conventions) does not contain 'rda', but your current option for 'Description rules support' is set to 'RDA only' (on the Cataloging checks page), so no standard (AACR) cataloging checks will be run.

245: GMD not used in RDA
The Title GMD (245 subfield $h) is not appropriate in an RDA record (040 $e='rda') and should be replaced by appropriately coded 336 (Content type), 337 (Media type), and 338 (Carrier type) fields.

245: Do not use [et al.] in RDA
In the 245 (Title) field, RDA does not permit the use of the abbreviation '[et al.]'. Enter all of the items that are being referred to by the abbreviation, or replace the abbreviation with a simple phrase (such as 'and others', 'and other authors', etc.)

250: Do not abbreviate 'edition'
In field 250, the subfield $a (Edition statement) contains 'ed.'. RDA does not permit the use of the abbreviation 'ed.' for 'edition' unless the abbreviation is found on the resource itself. But if the word is spelled out on the item, then enter the word as it is spelled (eg. 'edition', 'edición', 'édition', etc.)

260: Invalid copyright symbol
The copyright date (260 subfield $c) for RDA records should be preceded by the actual copyright symbol. In this record, either the symbol is invalid, or it does not match the record's encoding. Use the diacritic editor (F3) to replace the invalid symbol.
Note: in version 2 press <Ctrl>+I to pop-up the diacritic editor

260: Do not use [s.l.] in RDA
In the 260 subfield $a (Place of publication, distribution, etc.), RDA does not permit the use of the abbreviation '[s.l.]' to indicate an unknown place of publication. The phrase '[Place of publication not identified]' should be entered instead.

260: Do not use [s.n.] in RDA
In the 260 subfield $b (Name of publisher, distributor, etc.), RDA does not permit the use of the abbreviation '[s.n.]' to indicate an unknown publisher name. The phrase '[Name of publisher not identified]' should be entered instead.

260: Missing subfield $a
This record is missing Place of publication data (260 $a). 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 to enter '[Place of publication not identified]' in subfield $a.

260: Missing subfield $b
This record is missing Publisher data (260 $b). 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 to enter '[publisher not identified]' in subfield $b.

260: Missing subfield $c
This non-serial record is missing Date of publication data (260 $c). Find the item and try to guess a date of publication, or enter '[date of publication not identified]' in subfield $c.

300: Do not abbreviate 'page(s)'
In field 300 (Physical description), subfield $a (Extent of item) contains ' p ' or 'p.'. Do not abbreviate 'pages'; enter the word as 'page' or 'pages' as appropriate.

300: Do not abbreviate 'volume'
In field 300 (Physical description), subfield $a (Extent of item) contains ' v ' or 'v.'. Do not abbreviate 'volume'; enter the word as 'volume' or 'volumes' as appropriate.

300: Do not abbreviate 'color'
In field 300 (Physical description), subfield $b (Other physical details) contains ' col ' or 'col.' Do not bbreviate 'color/colour'; enter the word as 'color' or 'colour' as appropriate for your catalog/catalogue.

300: Do not abbreviate 'illus'
In field 300 (Physical description), subfield $b (Other physical details) contains ' ill ' or ' illus ' or 'ill.'. Do not abbreviate 'illustration(s)'; enter the word as 'illustration' or 'illustrations' as appropriate.

300: Do not abbreviate portrait
In field 300 (Physical description), subfield $b (Other physical details) contains 'ports' or 'port' with or without a period. Do not abbreviate 'portrait'; enter the word as 'portrait' or 'portraits' as appropriate.

300: Move 'plates' to subf $a
In field 300 (Physical description), 'plates' should be entered in subfield $a (Extent of item) at the end of the pagination sequence. For example: $axii, 246 pages, 32 pages of plates. Move the 'plates' numbering from subfield $b to subfield $a.

336: Required field in RDA
In RDA/MARC records (040 subfield $e='rda'), field 336 (Content Type: the form of communication through which a work is expressed) is a required data element.

336: Subfield $2 missing
When controlled values from a MARC valuelist are used in field 336 (Content Type), subfield $2 is needed to indicate the source of the values used. Code $2 from: Genre/Form Code and Term Source Codes.

336: Subfield $2 needed
No values in field 336 (Content Type) could be validated against the RDA valuelist for this field. Add a subfield $2 (Source code) to indicate the source of the values used. Code $2 from: Genre/Form Code and Term Source Codes.

336: Change $2 to 'rdacontent'
All values in field 336 (Content Type) validated against the 'rdacontent' valuelist, but subfield $2 (Source code) is not 'rdacontent'. Change subfield $2 to 'rdacontent' to indicate the source of the codes used in the field.

336: Subfield $2 code incorrect
No values in field 336 (Content Type) validated against the RDA valuelist for this field, but subf $2 (Source code) is set to 'rdacontent'. Change subfield $2 to indicate the source of the codes used in the field, or replace the values with rda values.

336: Some values do not match $2
Subf $2 (Source code) in field 336 (Content Type) is not set to 'rdacontent', but some values in the field are present in the 'rdacontent' valuelist. Add a new 336, as terms from different source vocabularies require separate occurrences of the field.

336: Need 'rdacontent' in $2
In field 336 (Content Type), when using RDA valuelists in subfields $a (Content type term) and/or $b (Content type code), Subf $2 (Source code) must be set to 'rdacontent'. Code subf $2 'rdamedia' only in field 337, and 'rdacarrier' only in field 338.

336: Unmatched subf $a term
In field 336 (Content Type), when subfield $a (Content type term) is present, the corresponding code for subfield $b (Content type code) should also be present in the field. Press F1 and expand the 'codelist' section to view a list of valid codes/terms.

336: Unmatched subf $b code
In field 336 (Content Type), when subfield $b (Content type code) is present, the corresponding term for subfield $a (Content type term) should also be present in the field. Press F1 and expand the 'codelist' section to view a list of valid codes/terms.

337: Required field in RDA
In RDA/MARC records (040 subfield $e='rda'), field 337 (MediaType: the type of intermediation device required to view, play, run, etc., the content of a resource) is a required data element.

337: Subfield $2 missing
When controlled values from a MARC valuelist are used in field 337 (Media Type), subfield $2 is needed to indicate the source of the values used. Code $2 from: Genre/Form Code and Term Source Codes.

337: Subfield $2 needed
No values in field 337 (Media Type) could be validated against the RDA valuelist for this field. Add a subfield $2 (Source code) to indicate the source of the values used. Code $2 from: Genre/Form Code and Term Source Codes.

337: Change $2 to 'rdamedia'
All values in field 337 (Media Type) validated against the 'rdamedia' valuelist, but subfield $2 (Source code) is not 'rdamedia'. Change subfield $2 to 'rdamedia' to indicate the source of the codes used in the field.

337: Subfield $2 code incorrect
No values in field 337 (Media Type) validated against the RDA valuelist for this field, but subf $2 (Source code) is set to 'rdamedia'. Change subfield $2 to indicate the source of the codes used in the field, or replace the values with rda values.

337: Some values do not match $2
Subf $2 (Source code) in field 337 (Media Type) is not set to 'rdamedia', but some values in the field are present in the 'rdamedia' valuelist. Add a new 337, as terms from different source vocabularies require separate occurrences of the field.

337: Need 'rdamedia' in Subf $2
In field 337 (Media Type), when using RDA valuelists in subfields $a (Media type term) and/or $b (Media type code), Subf $2 (Source code) must be set to 'rdamedia'. Code subf $2 'rdacontent' only in field 336, and 'rdacarrier' only in field 338.

337: Unmatched subf $a term
In field 337 (Media Type), when subfield $a (Media type term) is present, the corresponding code for subfield $b (Media type code) should also be present in the field. Press F1 and expand the 'codelist' section to view a list of valid codes/terms.

337: Unmatched subf $b code
In field 337 (Media Type), when subfield $b (Media type code) is present, the corresponding term for subfield $a (Media type term) should also be present in the field. Press F1 and expand the 'codelist' section to view a list of valid codes/terms.

338: Required field in RDA
In RDA/MARC records (040 subfield $e='rda'), field 338 (Carrier Type: the format of the storage medium) is a required data element.

338: Subfield $2 missing
When controlled values from a MARC valuelist are used in field 338 (Carrier Type), subfield $2 is needed to indicate the source of the values used. Code $2 from: Genre/Form Code and Term Source Codes.

338: Subfield $2 needed
No values in field 338 (Carrier Type) could be validated against the RDA valuelist for this field. Add a subfield $2 (Source code) to indicate the source of the values used. Code $2 from: Genre/Form Code and Term Source Codes.

338: Change $2 to 'rdacarrier'
All values in field 338 (Carrier Type) validated against the 'rdacarrier' valuelist, but subfield $2 (Source code) is not 'rdacarrier'. Change subfield $2 to 'rdacarrier' to indicate the source of the codes used in the field.

338: Subfield $2 code incorrect
No values in field 338 (Carrier Type) validated against the RDA valuelist for this field, but subf $2 (Source code) is set to 'rdacarrier'. Change subfield $2 to indicate the source of the codes used in the field, or replace the values with rda values.

338: Some values do not match $2
Subf $2 (Source code) in field 338 (Carrier Type) is not set to 'rdacarrier', but some values in the field are present in the 'rdacarrier' valuelist. Add a new 338, as terms from different source vocabularies require separate occurrences of the field.

338: Need in 'rdacarrier' in $2
In field 338 (Carrier Type), when using RDA valuelists in subfields $a (Carrier type term) and/or $b (Carrier type code), Subf $2 (Source code) must be set to 'rdacarrier'. Code subf $2 'rdacontent' only in field 336, and 'rdamedia' only in field 337.

338: Unmatched subf $a term
In field 338 (Carrier Type), when subfield $a (Carrier type term) is present, the corresponding code for subfield $b (Carrier type code) should also be present in the field. Press F1 and expand the 'codelist' section to view a list of valid codes/terms.

338: Unmatched subf $b code
In field 338 (Carrier Type), when subfield $b (Carrier type code) is present, the corresponding term for subfield $a (Carrier type term) should also be present in the field. Press F1 and expand the 'codelist' section to view a list of valid codes/terms.

33X: Does not end in punct.
The 'RDA Fields' (336 - Content Type, 337 - Media Type, 338 - Carrier Type) contain only coded values and should not end in punctuation.

504: Do not abbreviates page(s)
Field 504 (Bibliography, Etc. Note) contains ' p ' or 'p.'. Do not abbreviate 'pages' as 'p.' in the RDA/MARC environment; enter the word as 'page' or 'pages' as appropriate.

Generic changes

If the program is checking an RDA record, any of the several cataloging checks ¹⁾ that look for the strings 'p.' or 'v.' in the 300 $a will instead look for the strings 'page' and 'volume'.

---

For a basic tutorial on customizing the cataloging checks, click here.