MARC Report 248: Cataloging Check Changes

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

Message strings have been normalized to prevent slight differences in spacing, punctuation, etc., from being considered a change; but therehas 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=26500003–> 650: Subf $v not used in new records <html>     (AACR and RDA) </html>
650 Indicator 2 is coded '2' (Medical Subject Heading). MeSH does not use subfield $v (Form subdivision) in new records (Jan. 2016- ). MeSH publication characteristics are now recorded in subfield $a of tag 655, with the first indicator blank, and second indicator 2. For example: “650 _2 $aHealth Policy$vCongresses” becomes: “650 _2 $aHealth Policy” and “655 _2 $aCongresses”.

<!– Id=26500004–> 650: Subf $z not used in new records <html>     (AACR and RDA) </html>
650 Indicator 2 is coded '2' (Medical Subject Heading). MeSH does not use subfield $z (Geographic subdivision) in new records (Jan. 2016- ). MeSH geographical descriptors are now recorded in subfield $z of tag 651, with the first indicator blank, and second indicator of 2. For example: “650 _2 $aHealth Policy$zIndia” becomes: “650 _2 $aHealth Policy” and “651 _2$a India”.

<!– Id=33360002–> 336: Field useful for linked data <html>     (AACR Only) </html>
336 (Content type) should be present in all records for future linked data purposes. Press <Insert> in the Tag column, add the 336 tag, then <Tab> over to the data column and select the appropriate Content type for your resource from the list that appears.

<!– Id=33370002–> 337: Field useful for linked data <html>     (AACR Only) </html>
337 (Media type) should be present in all records for future linked data purposes. Press <Insert> in the Tag column, add the 337 tag, then <Tab> over to the data column and select the appropriate Media type for your resource from the list that appears.

<!– Id=33380002–> 338: Field useful for linked data <html>     (AACR Only) </html>
338 (Carrier type) should be present in all records for future linked data purposes. Press <Insert> in the Tag column, add the 338 tag, then <Tab> over to the data column and select the appropriate Carrier type for your resource from the list that appears.

<!– Id=41000002–> %t: Subf $e is missing <html>     (AACR and RDA) </html>
In the %t (main entry), a subfield $e (relator term) should be present in both AACR and RDA records. A relator term describes the relationship between an agent (person, corporate body, family) and a work. For a list of RDA relators valid in the current context, add a subfield $e to the end of the field and press <F7>. (To disable this reminder, goto the RDA page of the options)

<!– Id=41110002–> 111: Subf $j is missing <html>     (AACR and RDA) </html>
In the 111 (main entry - meeting or conference), a subfield $j (relator term) should be present in both AACR and RDA records. A relator term describes the relationship between an agent and a work. For a list of RDA relators valid in the current context, add a subfield $j to the end of the 111 and press <F7>. (To disable this reminder, goto the RDA page of the options)

<!– Id=47000010–> %t: Remove parens from relator <html>     (AACR and RDA) </html>
%t: Subfield %p contains a valid RDA relationship term, and it should not be enclosed in parentheses. Remove the parentheses.

<!– Id=47000011–> %t: subf $e is missing <html>     (RDA Only) </html>
In the %t (Added entry), a subfield $e (relator term) should be present in both AACR and RDA records. A relator term describes the relationship between an agent (person, corporate body, family) and a work. For a list of RDA relators valid in the current context, add a subfield $e to the end of the field and press <F7>. (To disable this reminder, goto the RDA page of the options)

<!– Id=47000012–> %t: Subf $i is missing <html>     (AACR and RDA) </html>
In the %t (Added entry), a subfield $i (relationship information ) should be present in both AACR and RDA records when a title subfield is present. Relationship information describes the relationship between an work, expression, manifestation, or item to another work, expression, manifestation, or item. For a list of relationship terms valid in the current context, add a subfield $i to the beginning of the field and press <F7>.

<!– Id=47110001–> 711: Subf $j is missing <html>     (RDA Only) </html>
In the 711 (Added entry - meeting or conference), a subfield $j (relator term) should be present in both AACR and RDA records. A relator term describes the relationship between an agent and a work. For a list of RDA relators valid in the current context, add a subfield $j to the end of the 711 and press <F7>. (To disable this reminder, goto the RDA page of the options)

<!– Id=47600005–> %t: $ubf $i is missing <html>     (AACR and RDA) </html>
In the %t (Linking entry field), subfield $i (relationship information) should be present in both AACR and RDA records when a title subfield is present. Relationship information describes the relationship between an work, expression, manifestation, or item to another work, expression, manifestation, or item. For a list of relationship terms valid in the current context, add a subfield $i to the beginning of the field and press <F7>.

Deleted checks

Modified Flags

<!– Id=23770001–> 377: Not used in bib records <html>       Flag changed to: AACR and RDA       Flag was: None</html>
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)

<!– Id=23800001–> 380: Not used in bib records <html>       Flag changed to: AACR and RDA       Flag was: None</html>
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)

<!– Id=23810001–> 381: Not used in bib records <html>       Flag changed to: AACR and RDA       Flag was: None</html>
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)

<!– Id=23830001–> 383: Not used in bib records <html>       Flag changed to: AACR and RDA       Flag was: None</html>
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)

<!– Id=23840001–> 384: Not used in bib records <html>       Flag changed to: AACR and RDA       Flag was: None</html>
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)

<!– Id=29100034–> %t: Expression heading but Work 034 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100336–> %t: Work heading but Expression 336 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100370–> %t: Expression heading but Work 370 <html>       Flag changed to: RDA Only       Flag was: None</html>
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

<!– Id=29100377–> %t: Work heading but Expression 377 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100380–> %t: Expression heading but Work 380 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100382–> %t: Expression heading but Work 382 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100384–> %t: Expression heading but Work 384 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100385–> %t: Expression heading but Work 385 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=29100665–> %t: Expression heading but Work 665 <html>       Flag changed to: RDA Only       Flag was: None</html>
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.

<!– Id=33006322–> 300: Remove '.' after 'cm' or 'mm' <html>       Flag changed to: AACR and RDA       Flag was: RDA Only</html>
300 (Physical description field): 'cm' and 'mm' are symbols, not abbreviations; current understanding of ISBD is: 300 does not end with an ending mark of punctuation except when a 4XX field is also present, or when the punctuation is a closing parenthesis, or is part of the data (e.g., for an abbreviation)–LC PCC PS 1.7.1

<!– Id=40000001–> %t: Blank space before ellipsis <html>       Flag changed to: AACR and RDA       Flag was: RDA Only</html>
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.

<!– Id=40000002–> %t: Need blank before '…' <html>       Flag changed to: AACR and RDA       Flag was: RDA Only</html>
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.

<!– Id=40000003–> %t: Need blank after '…' <html>       Flag changed to: AACR and RDA       Flag was: RDA Only</html>
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.

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

<!– Id=42640001–> 264: Check Ind 2 (Publ data) <html>       Flag changed to: AACR and RDA       Flag was: RDA Only</html>
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.

<!– Id=42640002–> 264: Check Ind 2 (Prod data) <html>       Flag changed to: AACR and RDA       Flag was: RDA Only</html>
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.

<!– Id=47000003–> %t: Subf $e term no longer used <html>       Flag changed to: None       Flag was: AACR and RDA</html>
%t (Added entry field) subfield $e (Relator term): the term 'editor of compilation' is no longer used as a relationship designator in RDA. Instead, use 'editor' in subfield $e. See RDA 2014 Update summary, section I.3.1: http://access.rdatoolkit.org/rdarev201402_r201402-2027.html

<!– Id=47000006–> %t: Subf $i should end with ':' <html>       Flag changed to: None       Flag was: AACR and RDA</html>
%t (Added entry field) subfield $i (Relationship information) should end with a colon in a name/title heading. For example: 700 12 $iContains (work): $aBiddle, Tami Davis.$tStrategic bombardment. See LC-PCC PS: http://access.rdatoolkit.org/lcpschp1_lcps1-465.html.

Modified Brief Messages

<!– Id=22640012–> 264: _4 Copyright needs ©date <html>     (AACR and RDA)       Message changed from: 264: _4 Copyright needs Â©date</html>
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)

<!– Id=30400001–> 040: $e 'rda' but DRS=AACR <html>     (AACR Only)       Message changed from: 040: $erda but DRS=AACR</html>
040 subfield $e (Description conventions) contains 'rda' (i.e., this is an RDA record), but your DRS Option (Description rules support) is set to 'AACR only', meaning you want to edit RDA records to AACR–if you want to do this: change 040$e 'rda' to 'aacr', and edit the record; otherwise, disable this message by changing your DRS option (on the 'Cataloging Check' page of the options) to 'Follow 040'.

<!– Id=40400002–> 040: $e not 'rda', but DRS=RDA <html>     (RDA Only)       Message changed from: 040: $e not rda, but DRS=RDA</html>
040 subfield $e (Description conventions) does not contain 'rda' (i.e., this is not an RDA record); but your DRS Option (Description rules support) is set to 'RDA only', meaning you want to treat all records as RDA. To do this: add 040 $e 'rda', delete 04 $e 'aacr' (if present), and edit the record; otherwise, disable this message by changing your DRS option (on the 'Cataloging Check' page of the options) to 'Follow 040'.

Modified Notes

<!– Id=20000047–> 000/18: 'i' should be 'a' (DRS=A) <html>     (AACR Only)       Note changed</html>
To: 000/18 (Descriptive cataloging form) is coded 'i' (ISBD punctuation included), but your DRS (Description Rules Support) setting is AACR Only, so this position should be coded 'a' (AACR 2; unless this is an old, pre-AACR record).
From: <html>000/18 (Descriptive cataloging form) is coded 'i' (ISBD punctuation included), but your DRS (Descriptive Rules Support) setting is AACR Only, so this position should be coded 'a' (AACR 2; unless this is an old, pre-AACR record). </html>

<!– Id=20000056–> 000/06: RecType not ok for 264_0 <html>     (AACR and RDA)       Note changed</html>
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: <html>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).</html>

<!– Id=20080101–> 008/06: Continuing resource code needed <html>     (AACR and RDA)       Note changed</html>
To: 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.
From: <html>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.</html>

<!– Id=20080102–> 008/06: Collection code required <html>     (AACR and RDA)       Note changed</html>
To: 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.
From: <html>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.</html>

<!– Id=20080103–> 008/06: Monographic code required <html>     (AACR and RDA)       Note changed</html>
To: 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').
From: <html>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’).</html>

<!– Id=20400003–> 040: Subf $b is not 'eng' <html>     (AACR and RDA)       Note changed</html>
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: <html>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. </html>

<!– Id=21000004–> 100: 'editor' must be tagged 700 <html>     (AACR and RDA)       Note changed</html>
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: <html>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) </html>

<!– Id=22600003–> 260: $a missing <html>     (AACR Only)       Note changed</html>
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: <html>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)</html>

<!– Id=22600004–> 260: $b missing <html>     (AACR Only)       Note changed</html>
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: <html>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)</html>

<!– Id=22600022–> 260: $a [s.l.] must be [S.l.] <html>     (AACR Only)       Note changed</html>
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: <html>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) </html>

<!– Id=22640008–> 264: _1 $c move cpyRt date to I2=4 <html>     (AACR and RDA)       Note changed</html>
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: <html>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' </html>

<!– Id=22640009–> 264: _2 $c move cpyRt date to I2=4 <html>     (AACR and RDA)       Note changed</html>
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: <html>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'</html>

<!– Id=22640010–> 264: _3 $c move cpyRt date to I2=4 <html>     (AACR and RDA)       Note changed</html>
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: <html>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'</html>

<!– Id=22640011–> 264: _4 Copyright notice needs $c <html>     (AACR and RDA)       Note changed</html>
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: <html>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') </html>

<!– Id=22640013–> 264: _4 Copyright must have $c only <html>     (AACR and RDA)       Note changed</html>
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: <html>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') </html>

<!– Id=22640067–> 264: _4 Fix Copyright symbol <html>     (AACR and RDA)       Note changed</html>
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: <html>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'.</html>

<!– Id=22640068–> 264: _1 $c guess pubDate from cpyRt date <html>     (AACR and RDA)       Note changed</html>
To: 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'.
From: <html>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'.</html>

<!– Id=22640069–> 264: _0 $c move cpyRt date to I2=4 <html>     (AACR and RDA)       Note changed</html>
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: <html>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' </html>

<!– Id=22640070–> 264: _0 $c guess prodDate from cpyRt <html>     (AACR and RDA)       Note changed</html>
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: <html>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'. </html>

<!– Id=22640083–> 264: _1 $b contains a distributor <html>     (AACR and RDA)       Note changed</html>
To: 264 Indicator 2 = 1 subfield $b (Publisher name) contains a distribution statement (e.g., 'Distributed by'); unless that statement is an integral part of the publication statement (e.g., 'Published and distributed by') move that statement to the field that is specified for the distribution of a resource: 264 Indicator 2 = 2.
From: <html>264 Indicator 2 = 1 subfield $b (Publisher name) contains a distribution statement (e.g., “Distributed by”); unless that statement is an integral part of the publication statement (e.g., “Published and distributed by”) move that statement to the field that is specified for the distribution of a resource: 264 Indicator 2 = 2.</html>

<!– Id=22640084–> 264: _0 No abbrev. when in [ ] in $a <html>     (AACR and RDA)       Note changed</html>
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]. In RDA, we are to spell out abbreviations in supplied data (given in square brackets).
From: <html>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) </html>

<!– Id=22640085–> 264: _1 No abbrev. when in [ ] in $a <html>     (AACR and RDA)       Note changed</html>
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]. In RDA, we are to spell out abbreviations in supplied data (given in square brackets).
From: <html>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) </html>

<!– Id=22640086–> 264: _2 No abbrev. when in [ ] in $a <html>     (AACR and RDA)       Note changed</html>
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]. In RDA, we are to spell out abbreviations in supplied data (given in square brackets).
From: <html>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) </html>

<!– Id=22640087–> 264: _3 No abbrev. when in [ ] in $a <html>     (AACR and RDA)       Note changed</html>
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]. In RDA, we are to spell out abbreviations in supplied data (given in square brackets).
From: <html>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) </html>

<!– Id=23000049–> 300: $a use 'unnumbered' not '[ ]' <html>     (AACR and RDA)       Note changed</html>
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 RDA Toolkit 3.4.5.3 for more examples.
From: <html>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. </html>

<!– Id=33360001–> 336: But 040 $e not 'rda' <html>     (None)       Note changed</html>
To: 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').
From: <html>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.</html>

<!– Id=33370001–> 337: But 040 $e not 'rda' <html>     (None)       Note changed</html>
To: 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').
From: <html>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.</html>

<!– Id=33380001–> 338: But 040 $e not 'rda' <html>     (None)       Note changed</html>
To: 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').
From: <html>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.</html>

<!– Id=40001803–> 000/18: Code 'a' should be 'i' <html>     (RDA Only)       Note changed</html>
To: 000/18 (Descriptive cataloging form) is coded 'a' (AACR 2), but your DRS (Description Rules Support) option is set to 'RDA Only', so this position must be 'i' (ISBD punctuation included)
From: <html>000/18 (Descriptive cataloging form) is coded 'a' (AACR 2), but your DRS (Descriptive Rules Support) setting is RDA Only, so this position must be 'i' (ISBD punctuation included) </html>

<!– Id=42500001–> 250: $a Check abbreviation 'ed.' <html>     (RDA Only)       Note changed</html>
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')
From: <html>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.)</html>

<!– Id=43360003–> 336: Subf $2 required <html>     (AACR and RDA)       Note changed</html>
To: 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 (Press <F7> after the subf $2 for a list of codes).
From: <html>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 (Press <F1> for a list of codes).</html>

<!– Id=43360005–> 336: Need rdacontent values <html>     (AACR and RDA)       Note changed</html>
To: No values in field 336 (Content Type) validated against the RDA Content Type valuelist. If this valuelist is indeed the source of the term(s) used in the field (and subfield $2 indicates that it is), correct or replace the existing values with RDA Content Type values. Click on the data column of the field for a list of RDA terms.)
From: <html>No values in field 336 (Content Type) validated against the RDA Content Type valuelist. If this valuelist is indeed the source of the term(s) used in the field (and subfield $2 indicates that it is), correct or replace the existing values with RDA Content Type values. (Click on the field and press <F1> for a list of RDA terms.)</html>

<!– Id=43360006–> 336: Some values do not match $2 <html>     (AACR and RDA)       Note changed</html>
To: Subf $2 (Source code) in field 336 (Content Type) is not 'rdacontent', but some values in this field are present in the RDA Content Type valuelist. Change the non-rdacontent value(s) to 'rdacontent' values (click on the data field for a list), or delete them, or split the values from different sources into separate 336 fields, each with their own appropriate $2.
From: <html>Subf $2 (Source code) in field 336 (Content Type) is not 'rdacontent', but some values in this field are present in the RDA Content Type valuelist. Change the non-rdacontent value(s) to 'rdacontent' values (press <F1> for a list), or delete them, or split the values from different sources into separate 336 fields, each with their own appropriate $2.</html>

<!– Id=43360008–> 336: RDA Content type missing <html>     (AACR and RDA)       Note changed</html>
To: 336 (Content type) field(s) are present in this RDA record (040$e rda), but no 336 contains a valid rdacontent term or code. Change the term(s) and/or code(s) in one or more of these fields to valid 'rdacontent' values (click on the data field for a list), or add another 336 with valid 'rdacontent' values.
From: <html>336 (Content type) field(s) are present in this RDA record (040$e rda), but no 336 contains a valid rdacontent term or code. Change the term(s) and/or code(s) in one or more of these fields to valid 'rdacontent' values (press <F1> for a list), or add another 336 with valid 'rdacontent' values.</html>

<!– Id=43360009–> 336: $a or $b required <html>     (AACR and RDA)       Note changed</html>
To: 336 (Content type) must contain an appropriate term or code in subfield $a (Content type term) and/or subfield $b (Content type code). Click on the data column of the field for a list of appropriate RDA terms and codes; add whatever is appropriate for this work.
From: <html>336 (Content type) must contain an appropriate term or code in subfield $a (Content type term) and/or subfield $b (Content type code). Press <F1> for a list of appropriate RDA terms and codes and add whatever is appropriate for this work. </html>

<!– Id=43360051–> 000/06: 'e' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'e' (Cartographic material) requires a corresponding cartographic term in 336$a or code in 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'e' (Cartographic material) requires a corresponding cartographic term in 336$a or code in 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360052–> 000/06: 'f' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'f' (Manuscript cartographic material) requires a corresponding cartographic term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'f' (Manuscript cartographic material) requires a corresponding cartographic term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360054–> 000/06: 'm' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'm' (Computer file) requires a corresponding computer term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'm' (Computer file) requires a corresponding computer term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360056–> 000/06: 'a' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'a' (Language material) requires a corresponding text or notated movement term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'a' (Language material) requires a corresponding text or notated movement term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360057–> 000/06: 't' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 't' (Manuscript language material) requires a corresponding text or notated movement term in 336$a or code in 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 't' (Manuscript language material) requires a corresponding text or notated movement term in 336$a or code in 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360059–> 000/06: 'c' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'c' (Notated music) requires a corresponding term in 336$a or code in 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'c' (Notated music) requires a corresponding term in 336$a or code in 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360060–> 000/06: 'd' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'd' (Manuscript notated music) requires a corresponding notated music term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'd' (Manuscript notated music) requires a corresponding notated music term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360062–> 000/06: 'j' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'j' (Musical sound recording) requires a corresponding performed music term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'j' (Musical sound recording) requires a corresponding performed music term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360064–> 000/06: 'i' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'i' (Nonmusical sound recording) requires a corresponding sound or spoken word term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'i' (Nonmusical sound recording) requires a corresponding sound or spoken word term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360066–> 000/06: 'k' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'k' (Two-dimensional nonprojectable graphic) requires a corresponding still image term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'k' (Two-dimensional nonprojectable graphic) requires a corresponding still image term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360068–> 000/06: 'r' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'r' (Three-dimensional artifact or naturally occurring object) requires a corresponding 3-D term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'r' (Three-dimensional artifact or naturally occurring object) requires a corresponding 3-D term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360070–> 000/06: 'g' needs matching 336 <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'g' (Projected medium) requires a corresponding moving image term in a 336$a or code in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'g' (Projected medium) requires a corresponding moving image term in a 336$a or code in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43360072–> 000/06: 'o' needs at least two 336's <html>     (RDA Only)       Note changed</html>
To: 000/06 (Type of record) code 'o' (Kit) requires at least two or more terms in 336$a or codes in a 336$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacontent.html
From: <html>000/06 (Type of record) code 'o' (Kit) requires at least two or more terms in 336$a or codes in a 336$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdacontent.html</html>

<!– Id=43370005–> 337: Need rdamedia values <html>     (AACR and RDA)       Note changed</html>
To: No values in field 337 (Media Type) validated against the RDA Media Type valuelist. If this valuelist is indeed the source of the term(s) used in the field (and subfield $2 indicates that it is), correct or replace the existing values with RDA Media Type values. Click on the data column of the field for a list of RDA terms.
From: <html>No values in field 337 (Media Type) validated against the RDA Media Type valuelist. If this valuelist is indeed the source of the term(s) used in the field (and subfield $2 indicates that it is), correct or replace the existing values with RDA Media Type values. (Click on the field and press <F1> for a list of RDA terms.)</html>

<!– Id=43370006–> 337: Some values do not match $2 <html>     (AACR and RDA)       Note changed</html>
To: Subf $2 (Source code) in field 336 (Media Type) is not 'rdamedia', but some values in this field are present in the RDA Media Type valuelist. Change the non-rdamedia value(s) to 'rdamedia' values (click on the data column of the field for a list of RDA terms), or delete them, or split the values from different sources into separate 337 fields, each with their own appropriate $2.
From: <html>Subf $2 (Source code) in field 336 (Media Type) is not 'rdamedia', but some values in this field are present in the RDA Media Type valuelist. Change the non-rdamedia value(s) to 'rdamedia' values (press <F1> for a list), or delete them, or split the values from different sources into separate 337 fields, each with their own appropriate $2.</html>

<!– Id=43370008–> 337: RDA Media type missing <html>     (AACR and RDA)       Note changed</html>
To: 337 (Media type) field(s) are present in this record, but no 337 contains a valid rdamedia term or code. Change the term(s) and/or code(s) in one or more of these fields to valid 'rdamedia' values (click on the data column of the field for a list of RDA terms), or add another 337 with valid 'rdamedia' values.
From: <html>337 (Media type) field(s) are present in this record, but no 337 contains a valid rdamedia term or code. Change the term(s) and/or code(s) in one or more of these fields to valid 'rdamedia' values (press <F1> for a list), or add another 337 with valid 'rdamedia' values. </html>

<!– Id=43370009–> 337: $a or $b required <html>     (AACR and RDA)       Note changed</html>
To: 337 (Media type) must contain an appropriate term or code in subfield $a (Media type term) and/or subfield $b (Media type code). Click on the data column of the field for a list of RDA terms and add whatever is appropriate for this work.
From: <html>337 (Media type) must contain an appropriate term or code in subfield $a (Media type term) and/or subfield $b (Media type code). Press <F1> for a list of appropriate RDA terms and codes and add whatever is appropriate for this work. </html>

<!– Id=43370051–> 007/00: 's' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 's' (sound recording) requires the term 'audio' in 337$a or code 's' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 's' (sound recording) requires the term 'audio' in 337$a or code 's' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370053–> 007/00: 'c' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'c' (electronic resource) requires the term 'computer' in 337$a or code 'c' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'c' (electronic resource) requires the term 'computer' in 337$a or code 'c' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370055–> 007/00: 'h' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'h' (microform) requires the term 'microform' in 337$a or code 'h' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'h' (microform) requires the term 'microform' in 337$a or code 'h' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370057–> 007/00: 'g' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'g' (projected graphic) requires the term 'projected' in 337$a or code 'g' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'g' (projected graphic) requires the term 'projected' in 337$a or code 'g' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370058–> 007/00: 'm' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'm' (motion picture) requires the term 'projected' in 337$a or code 'g' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'm' (motion picture) requires the term 'projected' in 337$a or code 'g' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370060–> 007/00: 't' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 't' (text) requires the term 'unmediated' in 337$a or code 'n' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 't' (text) requires the term 'unmediated' in 337$a or code 'n' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370061–> 007/00: 'k' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'k' (non-projected graphic) requires the term 'unmediated' in 337$a or code 'n' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'k' (non-projected graphic) requires the term 'unmediated' in 337$a or code 'n' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370063–> 007/00: 'v' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'v' (videorecording) requires the term 'video' in 337$a or code 'v' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'v' (videorecording) requires the term 'video' in 337$a or code 'v' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43370065–> 007/00: 'z' needs matching 337 <html>     (RDA Only)       Note changed</html>
To: 007/00 (Category of material) code 'z' (unspecified) requires the term 'other' or 'unspecified' in 337$a or code 'v' or 'x' in 337$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdamedia.html
From: <html>007/00 (Category of material) code 'z' (unspecified) requires the term 'other' or 'unspecified' in 337$a or code 'v' or 'x' in 337$b. For appropriate terms/codes, press <F1> or see: http://www.loc.gov/standards/valuelist/rdamedia.html</html>

<!– Id=43380005–> 338: Need rdacarrier values <html>     (AACR and RDA)       Note changed</html>
To: No values in field 338 (Carrier Type) validated against the RDA Carrier Type valuelist. If this valuelist is indeed the source of the term(s) used in the field (and subfield $2 indicates that it is), correct or replace the existing values with RDA Carrier Type values. Click on the data column of the field for a list of RDA terms.
From: <html>No values in field 338 (Carrier Type) validated against the RDA Carrier Type valuelist. If this valuelist is indeed the source of the term(s) used in the field (and subfield $2 indicates that it is), correct or replace the existing values with RDA Carrier Type values. (Click on the field and press <F1> for a list of RDA terms.)</html>

<!– Id=43380006–> 338: Some values do not match $2 <html>     (AACR and RDA)       Note changed</html>
To: Subf $2 (Source code) in field 336 (Carrier Type) is not 'rdacarrier', but some values in this field are present in the RDA Carrier Type valuelist. Change the non-rdacarrier value(s) to 'rdacarrier' values (click on the data column of the field for a list of RDA terms), or delete them, or split the values from different sources into separate 338 fields, each with their own appropriate $2.
From: <html>Subf $2 (Source code) in field 336 (Carrier Type) is not 'rdacarrier', but some values in this field are present in the RDA Carrier Type valuelist. Change the non-rdacarrier value(s) to 'rdacarrier' values (press <F1> for a list), or delete them, or split the values from different sources into separate 338 fields, each with their own appropriate $2.</html>

<!– Id=43380008–> 338: RDA Carrier type missing <html>     (AACR and RDA)       Note changed</html>
To: 338 (Carrier type) field(s) are present in this record, but no 338 contains a valid rdacarrier term or code. Change the term(s) and/or code(s) in one or more of these fields to valid 'rdacarrier' values (click on the data column of the field for a list of RDA terms), or add another 338 with valid 'rdacarrier' values.
From: <html>338 (Carrier type) field(s) are present in this record, but no 338 contains a valid rdacarrier term or code. Change the term(s) and/or code(s) in one or more of these fields to valid 'rdacarrier' values (press <F1> for a list), or add another 338 with valid 'rdacarrier' values.</html>

<!– Id=43380009–> 338: $a or $b required <html>     (AACR and RDA)       Note changed</html>
To: 338 (Carrier type) must contain an appropriate term or code in subfield $a (Carrier type term) and/or subfield $b (Carrier type code). Click on the data column of the field for a list of RDA terms and add whatever is appropriate for this work.
From: <html>338 (Carrier type) must contain an appropriate term or code in subfield $a (Carrier type term) and/or subfield $b (Carrier type code). Press <F1> for a list of appropriate RDA terms and codes and add whatever is appropriate for this work. </html>

<!– Id=43380051–> 007/01: 'a' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'a' (Tape cartridge) requires the term 'computer tape cartridge' in 338$a or code 'ca' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'a' (Tape cartridge) requires the term 'computer tape cartridge' in 338$a or code 'ca' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380052–> 007/01: 'b' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'b' (Chip cartridge) requires the term 'computer chip cartridge' in 338$a or code 'cb' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'b' (Chip cartridge) requires the term 'computer chip cartridge' in 338$a or code 'cb' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380053–> 007/01: 'd' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'd' (Computer disc, type unspecified) requires the term 'computer disc' in 338$a or code 'cd' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'd' (Computer disc, type unspecified) requires the term 'computer disc' in 338$a or code 'cd' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380054–> 007/01: 'e' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'e' (Computer disc cartridge, type unspecified) requires the term 'computer disc cartridge' in 338$a or code 'ce' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'e' (Computer disc cartridge, type unspecified) requires the term 'computer disc cartridge' in 338$a or code 'ce' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380055–> 007/01: 'f' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'f' (Tape cassette) requires the term 'computer tape cassette' in 338$a or code 'cf' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'f' (Tape cassette) requires the term 'computer tape cassette' in 338$a or code 'cf' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380056–> 007/01: 'h' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'h' (Tape reel) requires the term 'computer tape reel' in 338$a or code 'ch' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'h' (Tape reel) requires the term 'computer tape reel' in 338$a or code 'ch' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380057–> 007/01: 'k' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'k' (Computer card) requires the term 'computer card' in 338$a or code 'ck' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'k' (Computer card) requires the term 'computer card' in 338$a or code 'ck' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380058–> 007/01: 'r' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'r' (Remote) requires the term 'online resource' in 338$a or code 'cr' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'r' (Remote) requires the term 'online resource' in 338$a or code 'cr' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380059–> 007/01: 'z' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'cz' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'cz' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380060–> 007/01: 'c' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'c' (Filmstrip cartridge) requires the term 'filmstrip cartridge' in 338$a or code 'gc' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'c' (Filmstrip cartridge) requires the term 'filmstrip cartridge' in 338$a or code 'gc' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380061–> 007/01: 'd' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'd' (Filmslip) requires the term 'filmslip' in 338$a or code 'gd' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'd' (Filmslip) requires the term 'filmslip' in 338$a or code 'gd' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380062–> 007/01: 'f' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'f' (Filmstrip, type unspecified) requires the term 'filmstrip' in 338$a or code 'gf' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'f' (Filmstrip, type unspecified) requires the term 'filmstrip' in 338$a or code 'gf' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380063–> 007/01: 's' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 's' (Slide) requires the term 'slide' in 338$a or code 'gs' in 338$b.For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 's' (Slide) requires the term 'slide' in 338$a or code 'gs' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380064–> 007/01: 't' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 't' (Transparency) requires the term 'overhead transparency' in 338$a or code 'gt' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 't' (Transparency) requires the term 'overhead transparency' in 338$a or code 'gt' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380065–> 007/01: 'z' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'gz' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'gz' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380066–> 007/01: 'a' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'a' (Aperture card) requires the term 'aperture card' in 338$a or code 'ha' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'a' (Aperture card) requires the term 'aperture card' in 338$a or code 'ha' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380067–> 007/01: 'b' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'b' (Microfilm cartridge) requires the term 'microfilm cartridge' in 338$a or code 'hb' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'b' (Microfilm cartridge) requires the term 'microfilm cartridge' in 338$a or code 'hb' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380068–> 007/01: 'c' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'c' (Microfilm cassette) requires the term 'microfilm cassette' in 338$a or code 'hc' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'c' (Microfilm cassette) requires the term 'microfilm cassette' in 338$a or code 'hc' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380069–> 007/01: 'd' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'd' (Microfilm reel) requires the term 'microfilm reel' in 338$a or code 'hd' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'd' (Microfilm reel) requires the term 'microfilm reel' in 338$a or code 'hd' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380070–> 007/01: 'e' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'e' (Microfiche) requires the term 'microfiche' in 338$a or code 'he' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'e' (Microfiche) requires the term 'microfiche' in 338$a or code 'he' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380071–> 007/01: 'f' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'f' (Microfiche cassette) requires the term 'microfiche cassette' in 338$a or code 'hf' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'f' (Microfiche cassette) requires the term 'microfiche cassette' in 338$a or code 'hf' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380072–> 007/01: 'g' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'g' (Microopaque) requires the term 'microopaque' in 338$a or code 'hg' in 338$b.
From: <html>007/01 (Specific material designation) code 'g' (Microopaque) requires the term 'microopaque' in 338$a or code 'hg' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380073–> 007/01: 'h' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'h' (Microfilm slip) requires the term 'microfilm slip' in 338$a or code 'hh' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'h' (Microfilm slip) requires the term 'microfilm slip' in 338$a or code 'hh' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380074–> 007/01: 'j' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'j' (Microfilm roll) requires the term 'microfilm roll' in 338$a or code 'hj' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'j' (Microfilm roll) requires the term 'microfilm roll' in 338$a or code 'hj' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380075–> 007/01: 'z' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'hz' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'hz' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380076–> 007/01: 'c' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'c' (Film cartridge) requires the term 'film cartridge' in 338$a or code 'mc' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'c' (Film cartridge) requires the term 'film cartridge' in 338$a or code 'mc' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380077–> 007/01: 'f' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'f' (Film cassette) requires the term 'film cassette' in 338$a or code 'mf' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'f' (Film cassette) requires the term 'film cassette' in 338$a or code 'mf' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380078–> 007/01: 'o' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'o' (Film roll) requires the term 'film roll' in 338$a or code 'mo' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'o' (Film roll) requires the term 'film roll' in 338$a or code 'mo' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380079–> 007/01: 'r' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'r' (Film reel) requires the term 'film reel' in 338$a or code 'mr' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'r' (Film reel) requires the term 'film reel' in 338$a or code 'mr' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380080–> 007/01: 'z' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'mz' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'mz' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380081–> 007/01: 'd' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'd' (Sound disc) requires the term 'audio disc' in 338$a or code 'sd' in 338$b.For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'd' (Sound disc) requires the term 'audio disc' in 338$a or code 'sd' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380082–> 007/01: 'e' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'e' (Cylinder) requires the term 'audio cylinder' in 338$a or code 'se' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'e' (Cylinder) requires the term 'audio cylinder' in 338$a or code 'se' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380083–> 007/01: 'g' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'g' (Sound cartridge) requires the term 'audio cartridge' in 338$a or code 'sg' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'g' (Sound cartridge) requires the term 'audio cartridge' in 338$a or code 'sg' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380084–> 007/01: 'i' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'i' (Sound-track film) requires the term 'sound-track reel' in 338$a or code 'si' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'i' (Sound-track film) requires the term 'sound-track reel' in 338$a or code 'si' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380085–> 007/01: 'q' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'q' (Roll ) requires the term 'audio roll' in 338$a or code 'sq' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'q' (Roll ) requires the term 'audio roll' in 338$a or code 'sq' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380086–> 007/01: 's' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 's' (Sound cassette) requires the term 'audiocassette' in 338$a or code 'ss' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 's' (Sound cassette) requires the term 'audiocassette' in 338$a or code 'ss' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380087–> 007/01: 't' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 't' (Sound-tape reel) requires the term 'audiotape reel' in 338$a or code 'st' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 't' (Sound-tape reel) requires the term 'audiotape reel' in 338$a or code 'st' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380088–> 007/01: 'z' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'sz' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'sz' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380089–> 007/01: 'c' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'c' (Videocartridge) requires the term 'video cartridge' in 338$a or code 'vc' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'c' (Videocartridge) requires the term 'video cartridge' in 338$a or code 'vc' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380090–> 007/01: 'd' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'd' (Videodisc) requires the term 'videodisc' in 338$a or code 'vd' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'd' (Videodisc) requires the term 'videodisc' in 338$a or code 'vd' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380091–> 007/01: 'f' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'f' (Videocassette) requires the term 'videocassette' in 338$a or code 'vf' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'f' (Videocassette) requires the term 'videocassette' in 338$a or code 'vf' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380092–> 007/01: 'r' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'r' (Videotape reel) requires the term 'videoreel' in 338$a or code 'vr' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'r' (Videotape reel) requires the term 'videoreel' in 338$a or code 'vr' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380093–> 007/01: 'z' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'vz' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'z' (Other) requires the term 'other' in 338$a or code 'vz' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=43380095–> 007/01: 'u' needs matching 338 <html>     (RDA Only)       Note changed</html>
To: 007/01 (Specific material designation) code 'u' (unspecified) requires the term 'unspecified' in 338$a or code 'zu' in 338$b. For appropriate terms/codes, click on the data column of the field. See also: http://www.loc.gov/standards/valuelist/rdacarrier.html
From: <html>007/01 (Specific material designation) code 'u' (unspecified) requires the term 'unspecified' in 338$a or code 'zu' in 338$b. For appropriate terms/codes, press <F1>, or see: http://www.loc.gov/standards/valuelist/rdacarrier.html</html>

<!– Id=47000008–> %t: Only one subf $i per tag <html>     (AACR and RDA)       Note changed</html>
To: %t (Added entry field) subfield $i (Relationship information) should not be repeated in the same tag: 'Where multiple relationships exist … provide separate access points, each with a single relationship designator in a single $i subfield.'–PCC Relationship Designator Guidelines, #15
From: <html>%t (Added entry field) subfield $i (Relationship information) should not be repeated in the same tag: “Where multiple relationships exist … provide separate access points, each with a single relationship designator in a single $i subfield.”–PCC Relationship Designator Guidelines, #15</html>

<!– Id=47600003–> %t: Only one subf $i per tag <html>     (AACR and RDA)       Note changed</html>
To: %t (Linking entry field) subfield $i (Relationship information) should not be repeated in the same tag: 'Where multiple relationships exist … provide separate access points, each with a single relationship designator in a single $i subfield.'–PCC Relationship Designator Guidelines, #15
From: <html>%t (Linking entry field) subfield $i (Relationship information) should not be repeated in the same tag: “Where multiple relationships exist … provide separate access points, each with a single relationship designator in a single $i subfield.”–PCC Relationship Designator Guidelines, #15</html>

Table of Contents