Showing posts with label RELATIONSHIP DESIGNATORS. Show all posts
Showing posts with label RELATIONSHIP DESIGNATORS. Show all posts

Saturday, August 3, 2013

Relationship Designators : LC-PCC Best Practices Guidelines

RDA RELATIONSHIP DESIGNATORS
RDA RELATIONSHIP DESIGNATORS

 Myth:
“I must include relationship designators with all access points.”

Reality:
Wrong.  You may include relationship designators in all access points.  But the only relationship designator that is required is “$e illustrator” for an illustrator of a resource intended for children.

Note: LC will soon implement the PCC requirement for relationship designators for all creators. 

[Source : 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):

Posted by at
Links to this post
Labels: , , ,

Creators and Contributors : LC-PCC Best Practices Guidelines

Myth:
“Creators and contributors perform the same function, and the instructions regarding them are interchangeable and found in the same chapter of RDA”

Reality:

Absolutely not true!  Creators are involved at the work level, and are covered in Chapter 19; contributors are involved at the expression level, and are covered in Chapter 20.  Further, if you use a relationship designator, be sure to use one appropriate to the “WEMI” level.

[Source : Library of Congress]
RDA RELATIONSHIP DESIGNATORS
RDA RELATIONSHIP DESIGNATORS

Posted by at
Links to this post
Labels: , , , , , , , , ,

Recording Statement of Responsibility : LC-PCC Best Practices Guidelines

Myth:
“You must always record all statements of responsibility.”

Reality:

Incorrect.  You must record the first statement of responsibility, generally in full.  Recording subsequent statements of responsibility is a matter of judgment -- but of course they are usually helpful for the user.  Also, note this from 2.4.2.3: “If not all statements of responsibility appearing on the source or sources of information are being recorded, give preference to those identifying creators of the intellectual or artistic content. In case of doubt, record the first statement.”
Myth:
“But aren’t you required to record a subsequent statement of responsibility if it describes an illustrator of a resource intended for children?”

Reality:

This is good cataloging practice, but not necessarily required.  You must provide an access point for the illustrator; and that the relationship designator “$e illustrator”. But a statement of responsibility other than the first one is not a core element.

[Source : Library of Congress]
Posted by at
Links to this post
Labels: , , , , , , , ,

Monday, May 27, 2013

Use of 500 and 510 Field to Show Relationships in a Corporate Body Name

RDA RELATIONSHIP DESIGNATORS
RDA RELATIONSHIP DESIGNATORS

RDA Cataloging Examples of Relationships in a Corporate Body Name : Founder ; Hierarchical superior

Click on image to enlarge

(note the use of relationship designator in 510 field)
(note NAR change from AACR2 to RDA in 410 field)

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

RDA Cataloging Examples of Relationships in a Corporate Body Name : Successor ; Predecessor ; Hierarchical superior ; 

RDA Relationship Designators Example
Click on image to enlarge

RDA Relationship Designators Example
Click on image to enlarge





[Revised on 2015-04-13]


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

RDA Blog : RDA Blog is a blog on Resource Description and Access (RDA), a new library cataloging standard that provides instructions and guidelines on formulating data for resource description and discovery, organized based on the Functional Requirements for Bibliographic Records (FRBR), intended for use by libraries and other cultural organizations replacing Anglo-American Cataloging Rules (AACR2). This blog lists description and links to resources on Resource Description & Access (RDA). It is an attempt to bring together at one place all the useful and important information, rules, references, news, and links on Resource Description and Access, FRBR, FRAD, FRSAD, MARC standards, AACR2, BIBFRAME, and other items related to current developments and trends in library cataloging practice.

RDA Blog History: RDA Blog was created by Salman Haider, a Cataloging & Metadata Librarian Blogger & Online Social Media Expert from India. RDA Blog embarked on its journey to provide useful information to Resource Description and Access (RDA) in August 2011. It received good response from librarians, catalogers, and library professionals from all around the world. It is interesting to note that the first hundred thousand pageviews to RDA Blog came in 3 years, but it took just 8 months to reach another hundred thousand pageviews. At present it is viewed at a rate of fifteen to twenty thousand times per month. RDA Blog is widely followed in social media.

See also:

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

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

Posted by at
Links to this post
Labels: , , , , , ,

Tuesday, March 5, 2013

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:

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

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

Posted by at
Links to this post
Labels: , , , , , , , ,

Thursday, December 6, 2012

RDA Refresher Training at LC: Special Topics

(Source: LC RDA pages)

Art catalogs examples (reviewed): LCCN: 2012354343

Posted by at
Labels: , , , , , , , , , ,

Friday, November 23, 2012

LC-PCC PS for 1.7.1 General Guidelines on Transcription

LC-PCC PS for 1.7.1 General Guidelines on Transcription>>Access Points for Corporate Names, Including Meetings, in Name Authority and Bibliographic Records (LC practice/PCC practice):

1. Quotation marks. If the form of name in the access point includes quotation marks around an element or elements of the name, retain them. Use double quotation marks in the access point instead of other forms of quotation marks.

2. Initials. If the form of name in the access point consists of or contains initials, regularize the spacing and put one space after an initial that is followed by a word or other element that is not an initial and no space after an initial that is followed by another initial consisting of one letter.

EXAMPLE
source
F&H Denby
authorized access point
110 2#$a F & H Denby

EXAMPLE
source
U. S. D. A. Symposium …
authorized access point
111 2#$a U.S.D.A. Symposium ...

EXAMPLE
source
I E E E ...
authorized access point
110 2#$a IEEE ...
  
3. Abbreviations. Precede or follow abbreviations consisting of two or more letters with a space, e.g., "Gauley Bridge (W. Va.)," "Ph. D. Associates."

4. Place name at end. If the form of name in the access point includes a place name at the end and the place is enclosed within parentheses or is preceded by a comma-space, retain in the access point the punctuation as found.

EXAMPLE
110 2#$a California State University, Northridge

5. Subfield $i (Relationship information) in authority records. When subfield $i for relationship designator is used in a 5XX field, begin the field with subfield $w r. Give subfield $i as the second subfield; the first word in the relationship designator is capitalized, and the subfield ends with a colon.

EXAMPLE
100 1#$a Garr, Arnold K.
510 2#$w r $i Employer:$a Brigham Young University

[Source:  RDA Toolkit]


See also:

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

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

Posted by at
Labels: , , , , , , , , ,
Subscribe to: Posts (Atom)