Thursday, January 24, 2013

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:

See also:

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

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

Friday, January 18, 2013

Wednesday, January 16, 2013

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:

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

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

Tuesday, January 15, 2013

Undifferentiated Personal Name Authority Records

LC and PCC have agreed to the interim guidelines for undifferentiated names found at:

http://www.loc.gov/aba/pcc/rda/RDA%20Interim%20Policies%20and%20Best%20Practices.html

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


Undifferentiated Personal Name Authority Records (Jan. 7, 2013)

Pending the final report of the PCC Non-MARC Task Group, due March 29, 2013, PCC NACO catalogers encountering identities that may be candidates for an undifferentiated name authority record are asked to follow these guidelines:

RDA-trained NACO Catalogers:

• Avoid if at all possible creating new RDA or AACR2 undifferentiated personal name authority records

• Avoid if at all possible adding entities to existing RDA or AACR2 undifferentiated personal name authority records

Instead, apply one of the following RDA instructions, based on cataloger's judgment, to create a unique authorized access point for the person:

• RDA 9.19.1.6 (Profession or Occupation)

• RDA 9.19.1.5 (Period of Activity of the Person)

OR

• Determine if a date of birth, a date of death, a fuller form of name, or an initial is available to create a unique authorized access point for the person.

AACR2 NACO Catalogers:

• Until they are RDA-trained, AACR2 NACO catalogers may continue to create new AACR2 undifferentiated name authority records

• Until they are RDA-trained, AACR2 NACO catalogers may continue to add entities to existing AACR2 undifferentiated name authority records

All RDA questions should be directed to LChelp4rda@loc.gov.

Comments on PCC-related aspects of the US RDA Test may be sent to: coop@loc.gov with the words "PCC/RDA aspects" in the subject line


Thursday, January 10, 2013

Differentiating Names of Persons: Answers to Questions

Answers and comments by experts are posted on RDA Cataloging, an online community/forum/group on Google+ at following URL.

https://plus.google.com/communities/114381713914946747
Please check "comments" following the post tilted "DIFFERENTIATING NAMES OF PERSONS: QUESTIONS"


Wednesday, January 9, 2013

Submitting Proposals to Revise RDA

Following is the link from the website of Joint Steering Committee for Development of RDA (JSC RDA) for Submitting Proposals to Revise RDA:

The Rule Revision Process: Submitting Proposals to Revise RDA


Monday, January 7, 2013

Differentiating Names of Persons: Questions

Join RDA Cataloging, a companion Google+ Community for this blog and discuss/answer/comment on a question on "Differentiating Names of Persons in RDA".

According to RDA: Additions to the name are given as instructed under 9.19.1.2–9.19.1.6

•9.19.1.2 (9.4 and 9.6): Title or other designation associated with the person
–Required for certain names

•9.19.1.3 (9.3.2/9.3.3): Date of birth and/or death
–Give if available

•9.19.1.4 (9.5): Fuller form of name
–Add to differentiate (LC!)

•9.19.1.5 (9.3.4): Period of activity of person
–Add to differentiate

•9.19.1.6 (9.16): Profession or occupation
–Required for certain names; Can add to differentiate


QUESTION: Can we still use qualifiers to 100 field according to MARC X00 - Personal Names-General Information to differentialte in Name Authority Records of different persons with same name
--------------------------------------------------------------------------------
http://www.loc.gov/marc/authority/adx00.html

can we use qualifier in subfield $c which is defined as:

$c - Titles and other words associated with a name
Includes qualifying information such as
•titles designating rank, office, or nobility, e.g., Sir
•terms of address, e.g., Mrs.
•initials of an academic degree or denoting membership in an organization, e.g., F.L.A.
•a roman numeral used with a surname
•other words or phrases associated with the name, e.g., clockmaker, Saint.
---------------------------------------------------------------------------
Please note

RDA Rule 9.19.1.2 Title or Other Designation Associated with the Person
Add to the name one or more of the following elements (in this order), as applicable:
a)a title of royalty (see 9.4.1.4) or nobility (see 9.4.1.5)
b)the term Saint (see 9.6.1.4)
c)title of religious rank (see 9.4.1.6–9.4.1.8)
d)the term Spirit (see 9.6.1.5)
e)the profession or occupation (see 9.16) for a person whose name consists of a phrase or appellation not conveying the idea of a person.
---------------------------------------------------------------------------

EXAMPLES OF SITUATIONS : suppose there is an NAR already established as [100-1- Haider, Salman]. Now while cataloging we come across a different person named as "Salman Haider"

Question 1: Can we use Dr. in subfield c to differentiate NAR. (e.g. only information available on the resource Dr. Salman Haider ; no other information available on the resource or on the web)
Question 2: Can we use Ph. D. in subfield to differentiate NAR (e.g. only information available on the resource Salman Haider, Ph. D. ; no other information available on the resource or on the web)
Question 3: Can we use period of activity of the person belonging to 20th/21st century in subfield to differentiate NAR (e.g. only information available on the resource Salman Haider ; no other information available on the resource or on the web)