Thursday, May 29, 2014

RDA BLOG - NEW UPDATES

1. RDA page: A blog page is added giving brief introduction and overview of Resource Description & Access (RDA).



2. Categories: on the right side has been significantly consolidated and modified. 

3. RDA Resources: page is modified. This page now includes Cataloger's Reference Directory having useful links to web-resources for catalogers.

4. A "scrolling bar": appears at the bottom listing select feedback from the RDA Blog Testimonials page.


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

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

Friday, May 16, 2014

Authorized Access Point - Main Entry - Uniform Title (AACR2) / Preferred Title (RDA) - MARC to RDA Mapping

MARC 21
FIELD
TAG
MARC 21
SUBFIELD CODE
MARC 21 FIELD /
SUBFIELD NAME
RDA
INSTRUCTION
NUMBER
RDA
ELEMENT
NAME
130Main entry—Uniform title
130aUniform title6.2.2Preferred Title for the Work
130aUniform title6.3Form of Work
130aUniform title6.4Date of Work
130aUniform title6.5Place of Origin of the Work
130aUniform title6.6Other Distinguishing Characteristic of the Work
130dDate of treaty signing6.4Date of Work
130fDate of a work6.10Date of Expression
130gMiscellaneous informationN/A
130hMedium6.9Content Type
130kForm subheading6.2.2Preferred Title for the Work
130lLanguage of a work6.11Language of Expression
130mMedium of performance for music6.15Medium of Performance
130nNumber of part/section of a work6.2.2Preferred Title for the Work
130nNumber of part/section of a work6.3Form of Work
130nNumber of part/section of a work6.4Date of Work
130nNumber of part/section of a work6.5Place of Origin of the Work
130nNumber of part/section of a work6.6Other Distinguishing Characteristic of the Work
130nNumber of part/section of a work6.16Numeric Designation of a Musical Work
130oArranged statement for music6.12Other Distinguishing Characteristic of the Expression
130pName of part/section of a work6.2.2Preferred Title for the Work
130pName of part/section of a work6.3Form of Work
130pName of part/section of a work6.4Date of Work
130pName of part/section of a work6.5Place of Origin of the Work
130pName of part/section of a work6.6Other Distinguishing Characteristic of the Work
130rKey for music6.17Key
130sVersion6.12Other Distinguishing Characteristic of the Expression
130tTitle of a workN/A

[Source: RDA Toolkit]

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

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

Monday, May 12, 2014

130 - Main Entry - Uniform Title (AACR2) / Preferred Title (RDA) - [NR]

130 - Main Entry-Uniform Title (NR)

First IndicatorSecond Indicator
Nonfiling characters
0-9 - Number of nonfiling characters
Undefined
# - Undefined

Subfield Codes
  • $a - Uniform title (NR)
  • $d - Date of treaty signing (R)
  • $f - Date of a work (NR)
  • $g - Miscellaneous information (R)
  • $h - Medium (NR)
  • $k - Form subheading (R)
  • $l - Language of a work (NR)
  • $m - Medium of performance for music (R)
  • $n - Number of part/section of a work (R)
  • $o - Arranged statement for music (NR)
  • $p - Name of part/section of a work (R)
  • $r - Key for music (NR)
  • $s - Version (NR)
  • $t - Title of a work (NR)
  • $0 - Authority record control number or standard number (R)
  • $6 - Linkage (NR)
  • $8 - Field link and sequence number (R)

FIELD DEFINITION AND SCOPE

Uniform title used as a main entry in a bibliographic record.
Main entry under a uniform title is used when a work is entered directly under title and the work has appeared under varying titles, necessitating that a particular title be chosen to represent the work. Cataloging rules also prescribe the use of this field when the work is entered directly under title and additions or deletions to the title proper must be accommodated. In this latter case, the title may not actually vary from iteration to iteration. The title that appears on the work being cataloged is contained in field 245. There will be no 100, 110, or 111 field in records with field 130.

GUIDELINES FOR APPLYING CONTENT DESIGNATORS

Descriptions of the first indicator position and all subfield codes, as well as input conventions for the 130 field, are given in the X30 Uniform Titles-General Information section. Because the second indicator is different for various X30 fields, it is not described in the general information section, but is described below.

 INDICATORS

Second Indicator - Undefined
Undefined and contains a blank (#).

See also: 


Wednesday, May 7, 2014

The Structure of RDA

General Structure

Remember that RDA has a clear structure:
  • Table of Contents
  • Introduction
  • Specific instructions
o   Entities and their attributes
·            Group 1 (WEMI) (Chapters 1-7)
·            Group 2 (PFC) (Chapters 8-16)
o   Relationships (Chapters 17-22, 24-32)
  • Appendices for
o   Abbreviation
o   Capitalization
o   Relationship designators (more on this later)
  • Glossary with links to the text of the instructions
  • Index

Not Organized Like AACR2

The organization of RDA is very different from AACR2. Instead of separate chapters for classes of materials (books, cartographic materials, printed music, etc.), RDA is principle-based and organized around the FRBR/FRAD tasks to help users “identify” and “relate” the resources they need from our collections. There are general instructions applying to all resources with specific instructions for characteristics unique to certain categories of resources.

The identifying elements for each thing we are describing are addressed separately in each chapter. RDA provides instructions on what identifying elements are needed; for those chapters related to access points, it then provides -- at the end of those chapters -- the instructions on how to assemble those elements to create authorized access points (remember, that’s what AACR2 calls headings). We will see this particularly in chapter 6 and chapters 9-11.

Not a Linear Resource

When you use online tools, you don’t read the content in the same way as you read a printed text.  You don’t generally read linearly from one page to the next. Instead, you read purposefully.  You perform keyword searches (and then view several hits from the results list), follow links, and jump to elements from a Table of Contents or other navigational feature

Some of the “length” of RDA is due to the need for duplicating content to serve the catalogers who will be arriving at that content in these different ways from different starting points.

ALA also publishes a print version of RDA. A print version of the RDA element set (a subset of the RDA content, organized by FRBR and FRAD entity) is also available from ALA Publishing.


“Core-ness”

Core Elements  Core elements in Resource Description & Access (RDA) are minimum elements required for describing resources. Core elements are a new feature of RDA which allowed for certain metadata elements to be identified as “required” in the cataloging process. The assignment of core status is based on attributes mandatory for a national level record, as documented in the FRBR/FRAD modules. ... ... ... ... (Visit below link to read complete article)

Read now complete article: Core Elements : Glossary of Library & Information Science


Alternatives, Options, and Exceptions

Contents:
  • Alternatives Options and Exceptions in RDA : What Every Cataloger Needs to Know
  • What are RDA Alternatives?
  • Example of RDA Alternatives
  • What are RDA Options?
  • Example of RDA Optional Additions
  • Example of RDA Optional Omissions
  • What are RDA Exceptions? 
  • Example of RDA Exceptions
  • How to decide whether to apply the alternatives, options, or exceptions?
  • Note on the use of screen images from RDA Toolkit (Following RDA and RDA Toolkit Copyright Statement and guidelines)
Alternatives Options and Exceptions in RDA : What Every Cataloger Needs to Know
RDA contains a number of guidelines and instructions that are marked as alternatives, options (optional additions, optional omissions), and exceptions. Each of these is clearly identified by an italicized label, which in the RDA Toolkit appears in green color in the instruction (alternative, optional addition, optional omission, exception). A green vertical bar also appears in the left margin next of an alternative, optional, or exceptional instruction in RDA Toolkit. These allow individual libraries or cataloging agencies to make decisions based on individual considerations in cases where two or more provisions are equally valid. Guidelines for alternatives and options are provided in RDA rule 0.8, and instructions for applying exceptions is at RDA 0.9 of chapter 0. ... ... ... 


Library of Congress Policy Statements

LC has created an extensive body of Library of Congress Policy Statements (LCPS), to facilitate a standard interpretation and application of these alternatives, options, and exceptions.  Think of these as the ‘RDA version’ of the LC Rule Interpretations. Be sure to consult and follow the LCPS in all such cases. To access the LCPS, click on the green “LCPS” link in the RDA Toolkit. [Note: LCPS is now LC-PCC PS]

Examples

The examples in RDA illustrate the application of the specific instruction under which they appear. They illustrate only the data that are addressed by that instruction. They are normally given without showing the preceding or enclosing punctuation that is prescribed for an ISBD presentation. All examples illustrate elements as they would be recorded by an agency whose preferred language is English.

Examples appear in yellow shading, clearly setting them off from the instructions themselves.


Sunday, May 4, 2014

Bibliographic Framework Initiative - BIBFRAME

Bibliographic Framework Initiative (BIBFRAME)

Initiated by the Library of Congress, BIBFRAME provides a foundation for the future of bibliographic description, both on the web, and in the broader networked world. This site presents general information about the project, including presentations, FAQs, and links to working documents. In addition to being a replacement for MARC, BIBFRAME serves as a general model for expressing and connecting bibliographic data. A major focus of the initiative will be to determine a transition path for the MARC 21 formats while preserving a robust data exchange that has supported resource sharing and cataloging cost savings in recent decades.

See also: