RECORDING SCRIPTS IN RDA

LC-PCC PS for 7.13.2

SCRIPT

CORE ELEMENT FOR LC/PCC

Script is a core element for LC if a language is commonly written in more than one script, and if the resource is in a script other than the primary one for the language.

[2012-05]

LC-PCC PS for 7.13.2.3

RECORDING SCRIPTS

Form of Script Name

LC practice/PCC practice: Use the English language names of scripts found at: 〈http://www.unicode.org/iso15924/iso15924-en.html〉. Generally do not include the parenthetical information found in the list when recording the script name.

If a resource is in a language that is commonly written in more than one script, name both the language and the script.

  

EXAMPLE

546 ##

$a Konkani $b Kannada.

546 ##

$a Konkani $b Devanagari.

546 ##

$a Serbian $b Latin.

546 ##

$a Serbian $b Cyrillic.

546 ##

$a Syriac $b Nestorian.

Applicability

LC practice/PCC practice: If the resource is in a script other than the primary one for the language, name both the language and the script in the language note (MARC field 546).

EXAMPLE

546 ##

$a Panjabi.

For a publication using the Gurmukhi script

but

546 ##

$a Panjabi $b Devanagari.

For a publication using the Devanagari script

546 ##

$a Sindhi.

For a publication using the Persian script

but

546 ##

$a Sindhi $b Gurmukhi.

For a publication using the Gurmukhi script

546 ##

$a Azerbaijani.

For a publication using the Latin script

but

546 ##

$a Azerbaijani $b Arabic.

For a publication using the Arabic script

546 ##

$a Azerbaijani $b Cyrillic.

For a publication using the Cyrillic script

546 ##

$a Church Slavic.

For a publication using the Cyrillic script

but

546 ##

$a Church Slavic $b Glagolitic.

For a publication using the Glagolitic script

  

For complex notes involving multiple languages and scripts, see Policy Statement 7.13.2.4.

[2012-04]

LC-PCC PS for 7.13.2.4

Details of Scripts

LC practice/PCC practice: When recording complex notes involving multiple languages, record information about both the language and script in $a (Language note) of MARC field 546 (language and script in same subfield because $a is not repeatable).

EXAMPLE

546 ##

$a Kazakh, Uighur (Cyrillic), and Chagatai (Cyrillic and Arabic script).

EXAMPLE

546 ##

Sanskrit (Latin and Devanagari) and English.

[2012-04]

[Source: RDA Toolkit]

Illustrative Content

 

ILLUSTRATIVE CONTENT

• LC CORE ELEMENT for resources intended for children
• RDA 7.15
• Open list of vocabulary terms
• Recorded in MARC 008/18 as applicable and field 300 $b

This data is recorded in MARC 008/18 as applicable and field 300 $b

Sources: Take information on illustrative content from any source.

Recording Illustrative Content

If the resource contains illustrative content, record illustration or illustrations, as appropriate. Tables containing only words and/or numbers are not considered as illustrative content. Disregard illustrated title pages, etc., and minor illustrations.

Look below at LCPS 7.15.1.3 for the Alternative

“Generally do not record the type of illustrative content in place of or in addition to the term ‘illustration’ or ‘illustrations.’ ”

Optional Addition (7.15.1.3-Recording Illustrative Content)
Record the number of illustrations if their number can be ascertained readily (e.g., when the illustrations are listed and their numbers stated).
EXAMPLE
48 illustrations

<<<<-------->>>>

RDA VS AACR2 (Changes in treatment of illustrations in 300 field)

No abbreviations

“color” (not “col.”)
“sound” (not “sd.”)
“silent” (not “si.”)
“illustrations” (not “ill.”)

Color Content (Not LC Core) (RDA 7.17, LC-PCC PS-7.17.1.3)

Examples

color (illustrations are in color)
some color (10 maps, some of which are in color)
chiefly color (illustrations, most of which are in color)

Sources: Use evidence presented by the resource itself as the basis for recording the presence of color content in the resource. If desired, take additional evidence from any source.

Recording Colour Content
If the content of the resource is in colors other than black and white or shades of grey, record the presence of color using an appropriate term. Disregard colored matter outside the actual content of the resource (e.g., the border of a map).

LC practice: Use the spelling “color” when recording that term.

<<<<------>>>>

LC-PCC PS for 7.15 (RDA)

ILLUSTRATIVE CONTENT

CORE ELEMENT FOR LC

Illustrative content is a core element for LC for resources intended for children.

[2011-09]

LC-PCC PS for 7.15.1.3 (RDA)

ALTERNATIVE

LC practice for Alternative: Generally do not record the type of illustrative content in place of or in addition to the term "illustration" or "illustrations."

(Source: based on information in RDA Toolkit and LC RDA page information)

<<<<------>>>>



EXAMPLES

300 $b illustrations  [source: RDA RECORDS (JSC)]

300 $b illustrations (chiefly color)  [source: RDA RECORDS (JSC)]

300 $b color illustrations  [source: RDA RECORDS (JSC)]

Comment: includes photographs and other illustrations

300 $a ... : $b ill. ; $c ...

            comment:  if recording, do not abbreviate

_____  300 $a ... : $b illustrations ; $c ...

            comment:  acceptable but not required except for resources for children

LC       no 300 $b

_____  300 $a ... : $b illustrations, photographs ; $c ...

            comment:  acceptable but not required

Comment: includes charts, graphs, and other illustrations

_____  300 $a ... : $b illustrations ; $c ...

            comment:  acceptable but not required

_____  300 $a ... : $b ill. ; $c ...

            comment:  if recording, do not abbreviate

LC       no 300 $b

_____  300 $a ... : $b illustrations, graphs ; $c ...

            comment:  acceptable but not required

Answer from an expert from LC regarding illustrations (Note: LC policy): Under RDA only illustrations for resources intended for children is considered LC CORE in the bibliographic record. It is catalogers judgement to record the illustrations for other types of resources. So please use best judgement in providing this information if it is considered useful for users.

[Sources: RDA Toolkit, LC RDA training material, JSC RDA Records Examples, and transcript of communication from experts at LC]

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

RDA in MARC

October 2012

Contents: MARC 21 Updates 9-15 include all changes to MARC for use with RDA approved through June 2012.

Content, Media and Carrier Types and Characteristics
RDA Content Types

• MARC already indicates content type in LDR/06.
• RDA contains a list of English language content types for which a new field 336 was provided in MARC Bibliographic and in MARC Authority.
• Field 336 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10.
• For a table that relates the MARC LDR/06 to the corresponding RDA content terms and MARC codes for RDA content terms see: Term and Code List for RDA Content Types.

RDA Media Types

• MARC already indicates media type in field 007/00.
• RDA contains a list of English language media types for which a new field 337 is provided in MARC Bibliographic and in MARC Holdings.
• Field 337 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10.
• For a table that relates the MARC 007/00 to the corresponding RDA media terms and MARC codes for RDA media terms see: Term and Code List for RDA Media Types.

RDA Carrier Types

• MARC already indicates carrier type in field 007/01.
• RDA contains a list of English language carrier types for which a new field 338 is provided in MARC Bibliographic and in MARC Holdings.
• Field 338 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10.
• For a table that relates the MARC 007/01 to the corresponding RDA carrier terms and MARC codes for RDA carrier terms see: Term and Code List for RDA Carrier Types

RDA Carrier Characterisitcs

• MARC provides for recording carrier characteristics in textual form in Bibliographic fields 300, 340, and 5XX and in coded form in Bibliographic and Holdings field 007.
• RDA contains lists of English language terms that can be used to express carrier characteristics and also allows expression via notes.
• RDA carrier characteristic notes – MARC Bibliographic fields 500 and other 5XX
• RDA carrier characteristic terms in MARC Bibliographic format
       - Field 300 (Physical Description)
       - Field 340 (Physical Medium) (new subfields)
       - New Bibliographic format fields
                   344 – Sound Characteristics (R)
                   345 – Projection Characteristics of Moving Image (R)
                   346 – Video Characteristics (R)
                   347 – Digital File Characteristics (R)

Attributes of Names and Resources
Attributes of names and titles are typically information that has been recorded in name headings (e.g., date of birth) or in uniform title headings (e.g., key for music) -- or they may have been included in a note in an Authority record for the name or title. With RDA they may be recorded separately from the heading or as part of the heading (or both). New fields for these attributes have been established for names and for resources (works and expressions).
New MARC Authority fields for name attributes:

046 - Special Coded Dates (R)
368 - Other Attributes of Person or Corporate Body (R)
370 - Associated Place (R)
371 - Address (R)
372 - Field of Activity (R)
373 - Associated Group (R)
374 - Occupation (R)
375 - Gender (R)
376 - Family Information (R)
378 - Fuller Form of Personal Name (NR)

New MARC Authority and Bibliographic fields for work and expression attributes:

046 - Special Coded Dates (new subfields only)
336 - Content Type (R)
377 - Associated Language (R)
380 - Form of Work (R)
381 - Other Distinguishing Characteristics of Work or Expression (R)
382 - Medium of Performance (R)
383 - Numeric Designation of Musical Work (R)
384 - Key (NR)

Relationships
Name to resource

• RDA Appendix I lists possible relationships between a resource and persons, families and corporate bodies, e.g., author, artist, cartographer.
• MARC already records these types of relationships using relator terms ($e) or codes ($4) in 1XX, 6XX, 7XX, and 8XX in MARC Bibliographic and 1XX, 4XX, and 5XX in MARC Authority.
• MARC Relator Code list is being augmented with RDA relationships that are not already in the list.

Resource to resource

• RDA Appendix J lists over 400 relationships that may exist between works, expressions, manifestations and items, e.g., dramatized as (work), indexed in (work), sequel, digest of (expression), filmed with (manifestation), reproduction of (item).
• RDA identifies several methods for specifying these relationships:
  • identifiers - e.g., many $o, $u, $x, $w, and $0 subfields, and field 856
  • notes - 5XX Bibliographic and 6XX Authority
  • structured descriptions - 76X-78X Bibliographic
  • structured access points - 700-75X Bibliographic and 4XX and 5XX Authority
• MARC addition: $i defined for the relationship term in Bibliographic 700-75X and 76X-78X and in Authority 4XX and 5XX.

Name to name

• RDA Appendix K lists possible relationships between persons, families and corporate bodies, e.g., employee, sponsor, descendent family, employer, predecessor.
• MARC subfield $i added to 4XX and 5XX Authority is also used to specify these types of relationships.

Miscellaneous other changes to MARC for RDA

• Additional subfield specificity in field 502 (Dissertation Note)
• Additional subfield for qualifying informaton in 028 (Publisher Number)
• ISSN subfield made repeatable in field 490 (Series Statement)
• Additional codes in various 007 and 008 character positions
• Additional subfields in 033 (Date/Time and Place of an Event) and 518 (Date/Time and Place of an Event Note)
• Field 040 $e made repeatable and code "rda" added to the MARC code list for Descriptive Conventions to indicate the use of the RDA rules for description. Leader/18 will be coded i with RDA.
• New Bibliographic format field: 264 - Production, Publicaton, Distribution, Manufacture, and Copyright Notice (R)
• Experimentation with a technique for including URIs for values (no MARC content designation change) (See Discussion Paper 2010-DP02 for general description.) 

[Source: Library of Congress, MARC 21 HOME RDA in MARC (MARC 21 HOME >> RDA in MARC)]

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

Names of Royal Persons

RDA RULE-9.2.2.20 -- Names of Royal Persons

EXAMPLE

[600-00] ‡a Hanwant Singh ‡c Maharaja of Jodhpur, ‡d 1923-1952.

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

Recording the Preferred Title for a Compilation of Works of One Person, Family, or Corporate Body

See RDA Rule 6.2.2.10 for Recording the Preferred Title for a Compilation of Works of One Person, Family, or Corporate Body

RDA Rule 6.2.2.10.1 is for Complete Works

RDA Rule 6.2.2.10.2 is for Complete Works in a Single Form

RDA Rule 6.2.2.10.3 is for Other Compilations of Two or More Works

Exceptions

For compilations of musical works by a single composer, apply instead the instructions at 6.14.2.8 (RDA).

For compilations of laws, etc., apply instead the instructions at 6.19.2.5.1 (RDA).

For compilations of treaties, etc., apply instead the instructions at 6.19.2.8 (RDA).

RDA Bibliographic Template for Monographs in Voyager ILS

English

Non-roman

Note: Tags 040/906/925/955 are cataloging agency specific and can be omitted/changed as appropriate

<<<<<---------->>>>>

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

Ongoing Conferences

NUMBER, DATE, AND LOCATION OF A CONFERENCE, ETC.

Authority Records for Ongoing Conferences

LC practice/PCC practice: For ongoing conferences, separate authority records may be created for the collective conference (typically made when cataloging a serial), an individual instance of an ongoing conference (typically made when cataloging a monograph), or both. These records may coexist in the LC/NACO authority file. A record for the collective conference should always be made to connect the earlier and later names of the collective conference.

Individual Instance of an Ongoing Conference

LC practice/PCC practice: When creating an authority record for an individual instance of an ongoing conference, the additions for number, date, and location of a conference, etc. are given in the authorized access point. Variant access points may be given for variant names of the individual conference, such as acronyms for a spelled-out form. Generally do not connect an individual instance of an ongoing conference to the earlier or later instance of the conference using a 5XX field, or to an authority record for the collective conference.

EXAMPLE

111 2#	$a ILCLI International Workshop on Cognitive Science $n (10th : $d 2010 : $c San Sebastián, Spain)
411 2#	$a International Workshop on Cognitive Science $n (10th : $d 2010 : $c San Sebastián, Spain)
411 2#	$a IWCogSc-10 (Workshop) $n (10th : $d 2010 : $c San Sebastián, Spain)

Collective Treatment of an Ongoing Conference

LC practice/PCC practice: When creating an authority record for the collective conference, do not add the numbers and/or dates to the authorized access point. Variant access points may be given for variant names of the collective conference. Connect authority records for earlier and later names of the collective conference using 5XX fields. Include a 667 field shown in the example below when there are authority records for both collective and individual instances of an ongoing conference.

EXAMPLE

111 2#	$a ILCLI International Workshop on Cognitive Science
411 2#	$a International Workshop on Cognitive Science
411 2#	$a Institute for Logic, Cognition, Language, and Information International Workshop on Cognitive Science
411 2#	$a IWCogSc (Workshop)
511 2#	$w a $a International Colloquium on Cognitive Science
667 ##	$a See also related access points for individual instances of this conference which include specific information about the number, date, or place of the individual conference.

[Source: RDA Toolkit LC-PCC PS for RDA Rule 11.13.1.8]

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

RDA - in Cataloger's Desktop

Get the Most From RDA - in Cataloger's Desktop See the presentation NOW:

http://www.loc.gov/cds/desktop/training/Getting_the_most_from_RDA.ppt

(Source: CDS, LOC)

Ask Questions to Library of Congress about RDA

Write to the LChelp4rda@loc.gov account if:

• you have questions about existing headings
• you need assistance in creating a new RDA authority record because your library is not using RDA for cataloging.

<<<<------->>>>

PCC Post RDA Test Guidelines 

These guidelines apply to PCC catalogers continuing to create RDA bibliographic and authority records after the RDA test period and to PCC catalogers needing to use an authorized access point established in an RDA authority record...

Government Bodies Recorded Subordinately

RECORDING NAMES OF GOVERNMENT BODIES AND OFFICIALS--Government Bodies Recorded Subordinately--Type 3

See RDA Rule 11.2.2.19 for Government Bodies Recorded Subordinately

See RDA Rule 11.2.2.20 for Direct or Indirect Subdivision

[Source: RDA Toolkit]

[Check NAR--n 2012215382--National Data Centre--Office of the Additional Director General of Meteorology (Research), Pune]

Changing Name Authority Record from AACR2 to RDA

• Change the Descriptive cataloging rules (008/10) to "z", from "c" 
• In the 040 add cataloging source, e.g. $d DLC (if it doesn't end with this already) and a $e rda.
• Re-examine the record to see if the heading and also the references are according to RDA rules and LC-PCC PS (if applicable).

General guidelines

Do not create hybrid AACR2/RDA authorized access points in establishing new headings or in making additions to existing headings. Follow one cataloging code or the other in establishing authorized access points.

Catalogers making additions to AACR2 headings or making new headings based on existing AACR2 records will use AACR2 rules and appropriate LCRIs.  Catalogers making additions to RDA headings or making new headings based on existing RDA records will use RDA instructions.

AACR2 1XX fields that are suitable for use under RDA may be used as the base element in an extended RDA authorized access point (such as a name-title or subordinate body record).  When using an AACR2 1XX heading as the base element in an extended RDA authorized access point, the AACR2 authority record must be re-coded to RDA.  Optionally, any other existing dependent records may also be re-coded to RDA.

Approved PCC NACO Policies--Interim Documentation

In March 2012, the PCC Task Group to Formulate or Recommend PCC/NACO RDA Policy on Authority Issues recommended NACO policies and best practices on authority issues in the RDA environment. These policies and best practice recommendations were reviewed by the PCC Policy Committee and either approved as submitted, or approved with revisions.

Consolidated Table [PDF : 22 KB] summarizing all of the task group's recommended NACO policies and best practices, along with the PCC Policy Committee's action.

Individual recommendations: High Priority Recommendations (Word, 52 KB); Medium Priority Recommendations (Word, 29 KB); Low Priority Recommendations (Word, 22 KB)

The RDA Toolkit, the LC-PCC Policy Statements, and the Descriptive Cataloging Manual (DCM) Z1 will reflect the final PCC-approved decisions on the recommended NACO policies and best practices. In the interim, however, please consult this table along with the individual recommendations to identify these new PCC/NACO policies and best practices. The approved policies are in effect now. Some, but not all, specific policies and best practices are described in more detail below.

Conference headings and access points

If an AACR2 name authority record exists for an ongoing conference constructed according to LCRI 24.7B (i.e. the heading for the conference does not include the number date or place of any one specific conference), and the AACR2 heading is acceptable under RDA, PCC RDA-trained catalogers may use the AACR2 form to create RDA authorized access points for individual conferences. These RDA authorized access points will include additions such as number, date, and place, according to RDA 11.13.1.8. The PCC Policy Committee approved the conference recommendation of the PCC Task Group to Formulate or Recommend PCC/NACO RDA Policy on Authority Issues, which allows an "unqualified" RDA conference authorized access point for an ongoing conference to exist along with individual qualified RDA conference authorized access points for the same conference. The "unqualified" RDA authorized access point would be used for serial publications; the qualified RDA authorized access point would be used for monographic publications.

Personal name headings and access points

If an existing AACR2 authority record for a personal name is an undifferentiated name record and there is now a date of birth, a date of death, a fuller form of name, or occupation for the person related to the resource being cataloged, create an RDA differentiated name authority record for that person, remove the appropriate 670 fields from the AACR2 undifferentiated record, and report the necessary bibliographic file maintenance.  For other situations, use the AACR2 undifferentiated authorized access point in the RDA bibliographic record.

Changes taking place in the LC/NACO Authority File

The LC/NACO Authority File is undergoing changes to accommodate RDA implementation. The changes are based on recommendations of the PCC Acceptable Headings Implementation Task Group. PCC catalogers should consult the document Summary of Programmatic Changes to the LC/NACO Authority File: What LC-PCC RDA Catalogers need to know as it contains critical information on working in the LC/NACO Authority File during the RDA transition.

7XX RDA fields in AACR2 authority records

Do not add 7XX fields for RDA forms to any AACR2 name authority record. The addition of an RDA 7XX field authorized during the US RDA Test has been discontinued.

For those name authority records that already contain 7XX fields for RDA forms:

• If the 1XX and the 7XX in the AACR2 NAR is exactly the same, delete the 7XX. If you are an RDA trained cataloger, re-code the AACR2 NAR to RDA.
• If the 1XX and the 7XX are not exactly the same, leave the NAR as is: do not remove the 7XX. This NAR will become part of a PCC project to recode the NARs to RDA after examination of the differences, etc.

Reminders:

• Other than noted above, RDA catalogers may re-code an AACR2 authority record to RDA if there are no changes in the 1xx.
• Do not change an RDA authority record to be an AACR2 authority record.

Write to the LChelp4rda@loc.gov account if:

• you have questions about existing headings
• you need assistance in creating a new RDA authority record because your library is not using RDA for cataloging.

See Also:

• http://www.loc.gov/aba/rda/pdf/lcnaf_rdaphase.pdf  (particularly p. 4 for conference headings)

• http://www.loc.gov/catworkshop/RDA%20training%20materials/LC%20RDA%20Training/Authorities%20Presentations/RDA%20special%20topic_changes%20to%20lc-naco%20file.ppt 

• For an excellent summary paper highlighting conference names under RDA: see http://www.loc.gov/aba/rda/source/special_topics_conferences.ppt

See Also: PCC Post RDA Test Guidelines

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

RDA Toolkit Essentials

33X fields do not necessarily mean RDA

Recent questions to the Policy and Standards Division prompt this cautionary message about imported records. The presence of fields 336 (Content type), 337 (Media type), and 338 (Carrier type) in a bibliographic record does not in and of itself indicate RDA cataloging, since these fields may be used with non-RDA cataloging.  When these fields are present in a bibliographic record look for positive evidence of RDA cataloging:

            Ldr/18 (Descriptive cataloging form) = i (ISBD punctuation included) or c (ISBD

                        punctuation omitted)

            040 contains $e = rda

            If the value in Ldr/18 is neither "i" nor "c" and 040 contains $e = rda, rely on the

            evidence in field 040.

Alternatively, look for evidence of non-RDA cataloging, such as:

            Ldr/18 (Descriptive cataloging form) = a (AACR 2)

            040 does not contain $e = rda

            Another clue may be that terms are abbreviated in places that RDA would not

            abbreviate them, e.g.:

                    300 ## $a 296 p. $b ill., ports. (some col.)

Retain the 33X fields (or other RDA-defined details, such as relationship designators) already present in imported records regardless of whether the cataloging is RDA or non-RDA.

(Source: Kay Guiles, Policy and Standards Division, Library of Congress)

See also:

• RDA Blog Home
• About RDA - Resource Description and Access
• About RDA Blog
• RDA Resources
• Cataloger's Reference Directory
• RDA Blog Testimonials
• Follow RDA Blog in Social Media: Google+ | Facebook | Google+ Community | Twitter | YouTube | SlideShare | Tumblr | WordPress | Flipboard | Pinterest | LinkedIn

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):