Posts

Showing posts with the label MONOGRAPHS

LC RDA Implementation of Relationship Designators in Bibliographic Records

Image
RDA RELATIONSHIP DESIGNATORS Library of Congress Implementation of Resource Description and Access Relationship Designators in Bibliographic Records with MARC 21 RDA Cataloging Examples, Guidelines, and Best Practices Key points The training manual is only for relationship designators in  bibliographic  records. The  requirement  for providing relationship designators is only applicable to  creators , whether coded in MARC 1XX or 7XX. Relationship designators for Person-Family-Corporate Body  should not be used in a name/title access point tagged 7XX or 8XX, even if they are creators. If the nature of the relationship cannot be ascertained even at a general level,  do not assign a relationship designator  (if in doubt, leave it out). Other relationship designators are encouraged. The element name, e.g., “creator”, may be used as a relationship designator when you can’t determine a more appropriate relationship designator. The tr...

Temporary / Permanent Date in an Incomplete Multipart Monograph : Questions and Answers in the Google+ Community "RDA Cataloging"

Image
RDA Cataloging is an online community/group/forum for library and information science students, professionals and cataloging & metadata librarians. It is a place where people can get together to share ideas, trade tips and tricks, share resources, get the latest news, and learn about Resource Description and Access (RDA), a new cataloging standard to replace AACR2, and other issues related to cataloging and metadata.  Questions and Answers in the Google+ Community " RDA Cataloging " <<<<====>>>> Publication etc., dates (MARC21 264 ). These conventions do not apply to serials or integrating resources (temporary data not recorded in this field). Temporary date. If a portion of a date is temporary, enclose the portion in angle brackets. EXAMPLE , 1980-〈1981〉  v. 1-2 held; v. 2 published in 1981 , 〈1981-〉  v. 2 held; v. 1-2 published in 1981 , 〈1979〉-1981.  v. 2-3 held of a 3-volume set , 〈1978-1980〉...

Corrected Titles Proper & Variant Titles : RDA vs AACR2 : Questions and Answers & Best Practices

Image
Loading... See is infographic in full screen:  Corrected Titles Proper & Variant Titles : RDA vs AACR2 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):

Number of Bibliographic Volumes Differing from Number of Physical Volumes - Questions and Answers

Question: AACR2 says  If the number of bibliographic volumes differs from the number of physical volumes, give the number of bibliographic volumes followed by   in   and the number of physical volumes: 8 v. in 5. How will we treat this in RDA. Answer: Relevant RDA rule is given below from RDA Toolkit . RDA rule 3.21.2.8 is for " Number of Bibliographic Volumes Differing from Number of Physical Volumes " According to this rule it should be given in MARC as: 300 $a 5 volumes 500 $a 8 bibliographic volumes in 5 physical volumes Please note that 3.21.2.8 is revised. Earlier it was numbered as 3.22.2.8. Note: Serials are exception. [Revised: 2015-02-04]

Incomplete Resource

Image
RDA Rule 3.4.1.10 for Incomplete Resource record the term indicating the type of unit without the number. This has to be applied also for a resource when the total number of units issued is unknown. 300 $a volumes 300 $a volumes (loose-leaf) LC-PCC PS for 3.4.1.10 - INCOMPLETE RESOURCE Incomplete Multipart Monographs LC practice: Do not give LC’s local holdings for incomplete multipart monographs in MARC field 300 ; ensure that there are item records for each part or unit. PCC practice: Do not give local holdings for multipart monographs in MARC field 300 . Updating Loose-leafs LC practice/PCC practice: If the updating loose-leaf includes transfer volumes, describe the extent in terms of "loose-leaf" and "transfer." EXAMPLE 300 ## $a volumes (loose-leaf), volume (transfer) <<<<------>>>> NOTE: ABOVE PRACTICES ARE "CHANGES FROM AACR2 TO RDA" ...

2A CATALOGING IN RDA

2A CATALOGING This statement is in response to questions stimulated by 2A cataloging done under RDA.  2A cataloging is a cataloging technique applied to certain unnumbered (or, rarely, partially numbered) multipart sets classified as a collection and not analyzed.  Such materials are judged of significance primarily as a group; individual items are not considered significant enough to catalog separately.  Though the set is "made up" because the individual items lack numerical designation, the individual items in the set are usually closely related by subject and other strong similarities, such as title (or parts of title), issuing body, or publisher. With respect to the inventory aspect of 2A cataloging under RDA, we want on the one hand to make it clear in the bibliographic record the state of the material as it was issued by the publisher but on the other hand to state clearly the rearrangement/repackaging that LC has done.  Thus, the extent statement (30...

RDA Purpose and Scope

Image
RDA provides a set of guidelines and instructions on recording data to support resource discovery. The data created using RDA to describe a resource are designed to assist users performing the following tasks:(1) find —i.e., to find resources that correspond to the user’s stated search criteria identify —i.e., to confirm that the resource described corresponds to the resource sought, or to distinguish between two or more resources with similar characteristics select —i.e., to select a resource that is appropriate to the user’s needs obtain —i.e., to acquire or access the resource described. The data created using RDA to describe an entity associated with a resource (a person, family, corporate body, concept, etc.) are designed to assist users performing the following tasks:(2) find —i.e., to find information on that entity and on resources associated with the entity identify —i.e., to confirm that the entity described corresponds ...

Recording Statement of Responsibility : LC-PCC Best Practices Guidelines

Myth: “You may not omit persons, families, or corporate bodies from a statement of responsibility.” Reality: Generally, this is true for monographs -- and it is the preferred practice, according to LC-PCC PS 2.4.1.5.  But in exceptional cases, if the statement names a burdensome number of entities, you may record the first and indicate the omission by summarizing what has been omitted, e.g. “ [and eleven others] .” Myth: “ ‘ Burdensome’ is defined in RDA as ‘ more than 3 entities or more than 12 parts of a table of contents.’ ” Reality: Wrong!  “Burdensome” is not defined in RDA or the LC-PCC PS.  Use cataloger judgment. [Source : 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  |  ...

Recording of Other Title Information : LC-PCC Best Practices Guidelines

Myth: “Recording of other title information is optional and a matter of cataloger judgment.” Reality: This statement is true for serials.  But not for LC monograph catalogers!  Although other title information is not a core element in ‘pure’ RDA, it is “LC Core” for monographs.  You must record it if it appears on the same source as the title proper. [Source : Library of Congress]

RDA Policies for Library of Congress

LC policies for a few topics recently discussed by the ABA Management Team.  These policies either confirm that the interim policies LC staff have been following are still in place, or note where policies will be different in the post-March period. The topics covered are: Policy 1:  RDA Acceptable Authority Records after March 31, 2013 Policy 2:  Monographs Imported from OCLC (including copy cataloging) Policy 3:  CIP Verification Policy 4:  Working with Existing Serial Records Policy 5: Added Volumes for Multipart Monographs Policy 6:  Manual Hybridization of AACR2 Records with RDA Elements All staff involved with creating and updating LC/NACO authority records should pay particular attention to Policy 1 on the treatment of authority records. Policies 2-6 are primarily applicable to ABA and other processing units choosing to follow them.   These policies are also posted at http://www.loc.gov/aba/rda/pdf/rda-policies-fo...

RDA Bibliographic Template for Monographs in Voyager ILS

Image
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):

Training Examples for RDA at the Library of Congress

Resource Description and Access at the Library of Congress (08/29/11) Authority Records RDA Authority Records (September 2010) [DOC, 123 KB] RDA Authority Records (August 2011) [PDF, 89 KB] Bibliographic Records Overview of Changes [DOC, 80 KB] Books [DOC, 82 KB] Language of Expression [DOC, 59 KB] Legal Works [DOC, 59 KB] Preferred title (including compilations) [DOC, 106 KB] Publication, distribution, and/or manufacture statement [DOC, 60 KB] Replacement of GMD and carrier description [DOC, 72 KB] Statement of Responsibility [DOC, 64 KB]

RDA Blog is DISCONTINUED

RDA Blog is discontinued. Visit below link for updated information on RDA:

Resource Description and Access (RDA)