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]

    Tuesday, December 30, 2014

    Resource Description & Access (RDA) & RDA Blog History Timeline

    Resource Description & Access (RDA) History


    Important Dates in the History and Development of Resource Description & Access (RDA). 
    • Click on the + sign to expand the timeline as shown by the arrow. 
    • RDA History Timeline can also be viewed in a Flipbook or List format as shown by the arrows. 
    • Click on each item to view detailed description and sources of information, photos, videos.

    Contribute in the further development of this RDA History Timeline by suggesting important dates in the history of RDA and RDA implementation in libraries around the world. For example you can suggest a date when your library implemented RDA Cataloging, or any date which is important to be noted in the Resource Description & Access (RDA) History. Suggestions should by accompanied with proper reference sources, from which the information could be verified/cited.

    If you like it, then show it with your Likes, +1, Tweets, and shares.


    Friday, December 26, 2014

    Parallel Titles in RDA, AACR2 Cataloging & MARC21

    Parallel Titles RDA AACR2 MARC21 Cataloging



    • Questions and Answers on treatment Parallel Titles in RDA, AACR2 and MARC21 in Google+ Community RDA Cataloging
    • Join the Google+ Community RDA Cataloging to view, ask, and share information and issues related to Resource Description & Access (RDA) and AACR2 Cataloging

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


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







    Aaron Kuperman
    Yesterday 10:55 PM
    +
    1
    0
    1
     
     
    At LC, and this is very important for records of works in non-Roman scripts, if there is a parallel title (typically in English or another Latin script langauge) anywhere in the item being cataloged, it ends up both as a parallel title (245, following an "="), and usually as a 246 , often with a $i indicating where the parallel title came from, such as the verso t.p., added title page, the collophon, or whereever.  In the past the 246 would have sufficient if the Roman script title was not on the title page.


    Saturday, December 20, 2014

    Correct Coding of ISBN in MARC21 field 020 in RDA & AACR2 Cataloging with Examples



    Several years ago the definition of $z of the 020 (International Standard Book Identifier) was expanded—it is now used for “structurally invalid” ISBNs (those that are too short, too long, wrong check digit, etc.) and also for “application invalid” ISBNs (ISBNs for a manifestation that would be described in a different bibliographic record).

    The LC-PCC Policy Statement for 2.15.1.7 provides the following instruction:  
    Record ISBNs in $z (Canceled/invalid) of MARC field 020 if they clearly represent a different manifestation from the resource being cataloged and would require a separate record (e.g., an ISBN for the large print version, e-book, or teacher’s manual on the record for a regular trade publication). If separate records would not be made (e.g., most cases where ISBNs are given for both the hardback and paperback simultaneously), or in cases of doubt, record the ISBNs in $a (International Standard Book Number) of MARC field 020

    Please remember to use $z for ISBNs when appropriate. For regular print publications, this is most likely to occur when you also have an ISBN for a large print edition or e-book that would be cataloged on a separate record.

    When we do not use the correct subfield code in field 020, systems that receive records from LC may incorrectly merge or replace records for the wrong format—we have received several complaints about this, and we hope we can improve the situation with your help.

    [Source: Dave Reser, Library of Congress, Policy and Standards Division] 


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


    Question: Record ISBNs in 020 $z if they represent a different manifestation from the resource being cataloged.

    • If a printed monograph presents different ISBNs for different manifestation, do we have to transcribe them like below given example?


    AACR2            020 $a 9780415692847 (hardback: alk. paper)
                                            020 $a 9780203116852 (e-book)

    RDA                020 $a 9780415692847 (hardback: alk. paper)
                                          020 $z 9780203116852 (e-book)   (recorded in $z ISBN clearly representing an e-book version of the same manifestation)

    Answer: Yes, the example you have given shows LC’s practice documented in LC PCC PS 2.15.1.7 for multiple ISBN:

    “…if they clearly represent a different manifestation from the resource being cataloged and would require a separate record (e.g., an ISBN for the large print version, e-book, or teacher’s manual on the record for a regular trade publication). If separate records would not be made (e.g., most cases where ISBNs are given for both the hardback and paperback simultaneously), or in cases of doubt, record the ISBNs in $a”

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


    See Also: RDA Blog Labels (Categories) in below links for posts on related information on treatment of ISBN in RDA.


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







    David Bigwood

    12 hours ago  -  Shared publicly
    While not part of the question and answer it would be nice to show subfield q being used. 


    RDA                020 $a 9780415692847 $q (hardback: alk. paper)

                                          020 $z 9780203116852 $q (e-book) 



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








    Sasha Birman
    Yesterday 4:29 PM
    +
    1
    0
    1
     
    Reply

    We use both fields, 440 is former series field. 490 is very current.





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


    Sasha Birman
    Yesterday 4:29 PM

    We use both fields, 440 is former series field. 490 is very current.

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