Sunday, March 15, 2015

RDA Cataloging Rules for Pseudonyms with MARC 21 Examples


Definition
PseudonymA name used by a person (either alone or in collaboration with others) that is not the person’s real name. (RDA Toolkit Glossary)
PseudonymA name assumed by an author to conceal or obscure his or her identity. (AACR2 Glossary) 


RDA Cataloging Rules for Pseudonyms


Frequently Asked Questions (FAQ) on Library of Congress / Program for Cooperative Cataloging practice for creating Name Authority Records (NARs) for persons who use Pseudonyms:

Q1. How many NARs are needed for contemporary persons who use pseudonyms

Q2. How do I decide which name to choose as the basic heading when creating NARs for a person with multiple pseudonyms? (DCM Z1 663— Complex see-also reference—Names)

Q3. Is it required to make a NAR for every pseudonym associated with a contemporary person? Some persons purport to have ten or more pseudonyms but in my catalog we only have works under one or two of those names – are there limits set on the number of NARs required? (DCM Z1 667 Cataloger Note section) 

Q4. Should the 663 note technique also be used in a corporate name NAR when providing 500 see-also references for the members of a group? (RDA Chapter 30) 

Q5. Can the 663 note be used without coding the 500 field with subfield $w nnnc? (MARC 21 Format for Authority Records, 663 field)

Q6. What about creating NARs for non-contemporary persons? Where is the guidance? 

Q7. What about different real names used concurrently by authors? 

Q8. How do I handle a situation when a pseudonym conflicts with another name and there is no information to add to either name to differentiate them? Do I create an undifferentiated NAR (or add the name to an undifferentiated NAR if it already exists)? Do I add the prescribed 663 note as well as the 500 coded “nnnc” to the undifferentiated NAR?

Q9. How do I handle LC classification numbers: Do I add the same LCC (053) on each NAR of a pseudonym? What if the pseudonym is used on non-literary works?





See also following Resource Description & Access (RDA) Blog posts:



[Source Library of Congress and RDA Toolkit]

Sunday, March 1, 2015

Articles, Books, Presentations on Resource Description and Access (RDA)



Resource Description and Access (RDA) ➨ Articles, Books, Presentations, Thesis, Videos

A web of meaning Linked open data resources on the web

C Landis - College & Research Libraries News, 2014
... provides short descriptions of each of the terms and links out to more in-depth descriptions and
standards. ... Although still in its adolescence, BIBFRAME's emphasis on relationships between
resources means that much of the duplication encountered ... Access: http://www.kcoyle.net ...

Cataloging for School Librarians

M Kelsey - 2014

[PDF] Introduction to linked data

TP Meehan - Catalogue and Index, 2014
... and preferably one where more information can be found, potentially with further links to yet more
resources. ... Resource Description Framework (RDF). ... xml:lang="en" content="Waugh, Evelyn, 1903-
1966"></div> <div rel="mads:hasExactExternalAuthority" resource="http://viaf ...

[PDF] Bibframe

TP Meehan - Catalogue and Index, 2014
... of these are necessarily the same thing as the WorldCat Work described by Richard Wallis as:
a high-level description of a ... http://dataliberate.com/2014/02/oclc- preview-194-million-open-
bibliographic-work-descriptions/ 9Schema.org. ... http://bibframe.org/vocab/Resource.html ...
American Library Association
CHICAGO — The newest print accumulation of RDA: Resource Description and Access is now available.RDA: Resource Description and Access ...

Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA, and BIBFRAME

T Baker, K Coyle, S Petiya - Library Hi Tech, 2014
... Bibliographic Entities Seen as Single-Resource Descriptions In practical terms, the ultimate
purpose of multi-entity bibliographic models is to distribute the description of bibliographic
resources over multiple data sources which can, in principle, be separately maintained, and ...

ISBD as Bibliographic Content Standard: Interweaving Threads, Contemplating a Future

LC Howarth - Cataloging & Classification Quarterly, 2014
... The ISBD provides consistent stipulations for descriptions of all types of published ... stipulations
for specific types of resources as required to describe those resources. ... FRBR framework—itself
an essential component of standards, such as RDA: Resource Description and Access. ...

The Origins and Making of the ISBD: A Personal History, 1966–1978

  • Michael Gorman

ISBD, the UNIMARC Bibliographic Format, and RDA: Interoperability Issues in Namespaces and the Linked Data Environment

  • Mirna Willer and Gordon Dunsire

ISBD Resource and Its Description in the Context of the Semantic Web

  • Carlo Bianchini and Mirna Willer


Tuesday, February 10, 2015

Title and Statement of Responsibility in RDA with MARC 21 Examples

Resource Description & Access (RDA)


Contents:
Title Proper   
    Title Proper Transcription
Parallel Title Proper
Other Title Information
Variant Titles
Earlier Title Proper and Later Title Proper
Statement of Responsibility   
   “Rule of Three” -- Change from AACR2!     
    More Than One Statement of Responsibility

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


Title Proper

Ø         Title proper is a CORE ELEMENT

Title proper is the chief name of a resource.  It is the focus for identifying the preferred source of information.  An alternative title is treated as part of the title proper.  The title proper excludes any parallel titles proper, other title information, and parallel other title information. 

This data is recorded in MARC field 245 $a $n $p

P         Look at instruction 2.3.2

Sources:           If the information does not appear on a source forming part of the resource itself, take it from one of the following sources (in order of preference):
a)      accompanying material (e.g., a leaflet, an “about” file)
b)      a container that is not issued as part of the resource itself (e.g., a box, case made by the owner)
c)      other published descriptions of the resource
d)     any other available source (e.g., a reference source)

Title Proper Transcription
P         Look at instruction 2.3.1.4
·         Transcribe a title as it appears on the source of information.  Apply the general guidelines on transcription given in 1.7.
·         Do not correct errors for monographs.
·         Do not record “[sic]” or [i.e., …]”; instead, give a note to explain.
·         Do correct errors for serials and integrating resources.

Examples:
      AACR2 record for a monograph:
            245 $a Teusday’s [i.e. Tuesday’s] tasks
      RDA record for this monograph:
            245 $a Teusday’s tasks
      246 $i Corrected title: $a Tuesday’s tasks

      RDA record for a serial:
            245 $a Zoology studies
      246 $i Misspelled title on number 1: $a Zooology studies 


Parallel Title Proper


Ø         Parallel title proper is a CORE ELEMENT for LC

A parallel title proper is the title proper in another language and/or script. An alternative title in another language and/or script is treated as part of the parallel title proper.  An original title in a language different from that of the title proper that is presented as the equivalent of the title proper is treated as a parallel title proper.

This data is recorded in MARC field 245 $b

P         Look at instruction 2.3.3

Sources:           The source for parallel title proper has been expanded to include any source within the resource.

Record a parallel title proper applying the basic instructions on recording titles given under 2.3.1. 

Ø    Remember that 2.3.1 instructs you to “Transcribe a title as it appears on the source of information. Apply the general guidelines on transcription given under 1.7.




Other Title Information


Ø         Other title information is a CORE ELEMENT for LC

Other title information is information that appears in conjunction with, and is subordinate to, the title proper of a resource. It may include any phrase appearing with a title proper that is indicative of the character, contents, etc., of the resource or the motives for, or occasion of, its production, publication, etc. Other title information includes subtitles, avant-titres, etc., but does not include variations on the title proper such as spine titles, sleeve titles, etc. or designations and/or names of parts, sections, or supplements. Other title information may be supplied for cartographic resources and moving image resources.

This data is recorded in MARC field 245 $b

P         Look at instruction 2.3.4

Record other title information appearing on the same source of information as the title proper applying the basic instructions on recording titles given under 2.3.1.




Variant Titles


2.3.6 addresses variant titles, and LCPS 2.3.6.3 provides important guidance on the recording of variant titles in the MARC record. This LCPS is very similar to RI 21.30J.



Earlier Title Proper and Later Title Proper


For integrating resources, serials, or multipart monographs, there are sometimes earlier or later titles proper which relate to changes of the title proper of the same resource over time.  Instructions for these situations are in 2.3.7 and 2.3.8.



Statement of Responsibility


Ø         Statement of responsibility relating to title proper is a CORE ELEMENT. If there is more than one statement of responsibility relating to the title proper, only the first is required. Other statements of responsibility are optional.

A statement of responsibility is a statement relating to the identification and/or function of any persons, families, or corporate bodies responsible for the creation of, or contributing to the realization of, the intellectual or artistic content of a resource.

This data is recorded in MARC field 245 $c

P         Look at instruction 2.4.1

Sources:           Take statements of responsibility relating to title proper from the following sources (in order of preference):
a)   the same source as the title proper
b)   another source within the resource itself
c)   one of the other sources of information specified under 2.2.4

Square brackets are needed only when data is taken from outside of the resource.


Transcribe a statement of responsibility in the form in which it appears on the source of information. Apply the general guidelines on transcription given under 1.7.

LCPS 2.4.1.4 states: “Generally do not abridge a statement of responsibility.”
Example:
            Source reads:               Dr. Logan Carroll, Harvard Medical School
RDA/LCPS say:         245 … / $c Dr. Logan Carroll, Harvard Medical School.
RDA allows:               245 … / $c Dr. Logan Carroll.

“Rule of Three” -- Change from AACR2!
 P         Look at LCPS 2.4.1.5

The AACR2 “Rule of Three” is not part of RDA.  RDA 2.4.1.5 directs you to record the persons, families, or corporate bodies named in the resource.  It is only an option to omit all but the first of each group and indicate the omission by summarizing (in English) what has been omitted (do not record “[et al.]”).
Ø         However, LC does not generally apply this option. The LCPS clearly states:
“Generally do not omit names in a statement of responsibility.”

Example:
Source reads:                           by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson.
AACR2:                      245 $a … / $c by Susan Brown … [et al.].
RDA allows:               245 $a … / $c by Susan Brown [and four others].
RDA/LCPS say:         245 $a … / $c by Susan Brown, Melanie Carlson, Stephen Lindell, Kevin Ott, and Janet Wilson.

More Than One Statement of Responsibility
RDA 2.4.2:

“If more than one statement of responsibility relating to title proper appears on the source of information, only the first recorded is required.”

[Source: contents by Library of Congress ; design by RDA Blog]

[This RDA Blog post is best viewed in Google Chrome web browser]

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

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

Tuesday, January 20, 2015

RDA Blog Guest Book in MARC 21 Fields & RDA Element Names

RDA Blog Guest Book MARC 21
RDA Blog Guest Book

RDA Blog Guest Book is re-designed in an interesting format according to MARC 21 Field Names & Resource Description & Access (RDA) Element Names for Name Authority Records (NAR). Please post your feedback, suggestions, and reviews through this guest book, to make this blog a better place for information on Resource Description & Access (RDA), AACR2, MARC 21, FRBR, FRAD, FRSAD, BIBFRAME and other areas of Library Cataloging.

Please write/publish detailed reviews of RDA Blog  in journals, books, and encyclopedias similar to following article published in Technical Services Quarterly, Taylor & Francis:


  • Tech Services on the Web: RESOURCE DESCRIPTION AND ACCESS (RDA) BLOG http://resourcedescriptionandaccess. blogspot. com

  • See also: 

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

    Monday, January 12, 2015

    245 - Title Statement - MARC to RDA Mapping

    MARC 21
    FIELD
    TAG
    MARC 21
    SUBFIELD CODE
    MARC 21 FIELD /
    SUBFIELD NAME
    RDA
    INSTRUCTION
    NUMBER
    RDA
    ELEMENT
    NAME
    245Title statement
    245aTitle2.3.2Title Proper
    245bRemainder of title2.3.3Parallel Title Proper
    245bRemainder of title2.3.4Other Title Information
    245bRemainder of title2.3.5Parallel Other Title Information
    245cStatement of responsibility, etc.2.4.2Statement of Responsibility Relating to Title Proper
    245cStatement of responsibility, etc.2.4.3Parallel Statement of Responsibility Relating to Title Proper
    245cStatement of responsibility, etc.2.3.2Title Proper
    245cStatement of responsibility, etc.2.3.3Parallel Title Proper
    245cStatement of responsibility, etc.2.3.4Other Title Information
    245cStatement of responsibility, etc.2.3.5Parallel Other Title Information
    245fInclusive datesN/A
    245gBulk datesN/A
    245hMediumN/A
    245kForm3.9.2Production Method for Manuscript
    245kForm7.2Nature of the Content
    245nNumber of part/section of a work2.3.2Title Proper
    245pName of part/section of a work2.3.2Title Proper
    245sVersionN/A

    See also following Resource Description & Access (RDA) Blog posts:
    [Source : RDA Toolkit & RDA Blog]