Tuesday, July 15, 2014

International Standard Serial Number (ISSN) - MARC to RDA Mapping

MARC 21
FIELD
TAG
MARC 21
SUBFIELD CODE
MARC 21 FIELD /
SUBFIELD NAME
RDA
INSTRUCTION
NUMBER
RDA
ELEMENT
NAME
022International Standard Serial Number
022aInternational Standard Serial Number2.15Identifier for the Manifestation
022lISSN-LN/A
022mCancelled ISSN-LN/A
022yIncorrect ISSN2.15Identifier for the Manifestation
022zCancelled ISSN2.15Identifier for the Manifestation

[Source: RDA Toolkit]

Friday, July 4, 2014

Identifying RDA Records

There are two indications that a record is an RDA bibliographic record:
  • Leader/18 contains the value “i” (ISBD punctuation included) 

  • Field 040 $e contains the code “rda”

[Source: Library of Congress]

Thursday, June 26, 2014

Articles on Resource Description and Access (RDA)


Resource Description and Access (RDA) ➨ Articles

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

EY Wong - Technical Services Quarterly, 2014
The frequency of the posts is steady throughout 2013. Some of the posts are extracts from
RDA toolkit and other trusted cataloging sources; other posts are snapshots of cataloging
records intended to provide interpretations on certain cataloging scenarios. The

Implementing RDA at the University of Illinois at Urbana-Champaign Library

Q Jin, JA Sandberg - Technical Services Quarterly, 2014

Technical Services Report: Cataloging in RDA and Linked Data environments. A Report of the ALCTS Cataloging & Metadata Management Section, Cataloging and …

A Guimaraes - Technical Services Quarterly, 2014

Beyond Content, Media, and Carrier: RDA Carrier Characteristics

S Bernstein - Cataloging & Classification Quarterly, 2014

RDA Display and the General Material Designation: An Innovative Solution

RS Panchyshyn - Cataloging & Classification Quarterly, 2014

RDA: Strategies for Implementation

D Sullivan - Australian Academic & Research Libraries, 2014

[PDF] Authors and Authorities in Post-RDA Library Systems: A Case Study

HL Moulaison - 2014

RDA Training and Implementation at Duke University Libraries: Minimizing the Distraction

AH Turner - Journal of Library Metadata, 2014

[PDF] Preparing LIS Students for a Career in Metadata Librarianship

B Mooney Gonzales - SLIS Student Research Journal, 2014



Saturday, June 14, 2014

DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE - RDA EXAMPLES

DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE
CASERDA / LC PCC-PS EXAMPLE
approximate date[2014?]
supplied date[2014]
date of publication not identified[date of publication not identified]
two years[2013 or 2014]
betwen years[between 2005 and 2014?]
not before[not before 2000]
not after[not after 2000]
betwen years with date[between March 13, 2000 and July 10, 2014]

<<<<<=====>>>>>

Note: Cells left blank for Catalogers to fill with data. Please supply cases and solutions quoting proper RDA rules where date of publication not identified. It will be included in this table along with name of the cataloger. Write your suggestions in the "comments" section of this blog post.

<<<<<=====>>>>>

DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE - LC-PCC PS FOR 2.8.6.6



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.

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]

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”

Some of the RDA elements are designated as “core” elements. The assignment of core status is based on attributes mandatory for a national level record, as documented in the FRBR/FRAD modules. Core-ness is identified at the element level. Some elements are always core (if applicable and the information is available); some are core only in certain situations.

Core elements can be seen in two ways within RDA:
  • They are discussed in general, and listed as a group, in the sub-instructions of RDA 0.6
  • They are clearly labeled in light blue at each core instruction.  See, for example, this label for the core element 2.3.2, “Title Proper.”  If the status of an element as core depends upon the situation, an explanation appears after the “Core element” label.
We will see that LC has identified other elements as “LC Core” for our cataloging.


Alternatives, Options, and Exceptions

RDA designates a number of guidelines and instructions as alternatives, options, or exceptions. All are clearly labeled as such in the Toolkit by the presence of a green vertical bar in the left margin and a green legend in the instruction (“alternative”, etc.).
  • Alternative guidelines and instructions provide an alternative to what is specified in the immediately preceding guideline or instruction.
  • Optional instructions provide for either:
o   the optional addition of data that supplement what is called for in the immediately preceding instruction, or
o   the optional omission of specific data called for in the immediately preceding instruction.
  • Some instructions are ‘scoped’ as being applicable only to certain types of resources (such as serials).
  • Whether to apply the alternatives, options, or exceptions is cataloger judgment, unless an LC practice has been identified in an LCPS (see next section).

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.

[Source: Library of Congress]

Sunday, April 27, 2014

RDA Toolkit Release (April 22, 2014)

TOPIC 1: Changes in RDA Content
TOPIC 2: Change in Content in LC-PCC PSs
TOPIC 3: Functional Changes in the RDA Toolkit


TOPIC 1: Changes in RDA Content
There are two types of changes in the RDA content for this update: 1) the third annual major update to RDA based on the decisions made by the Joint Steering Committee for Development of RDA (JSC) at their November 2013 meeting; and 2)  “Fast Track” changes that are relatively minor and typical of a release update.
Revisions from JSC actions:
The attached document (Summary of 2014 rda updates.docx) identifies highlights from the changes to RDA due to the JSC update (see link below).  Many of the changes in this update package are due to re-numbering of instructions and references (without a change in actual content) and are not included in the attached listing.  The changes will appear with the “revision history” icon in the RDA Toolkit.  A complete listing of all changes due to the proposal process will appear in the left-side table of contents pane on the RDA tab in the toolkit, at the bottom under “RDA Update History”—you will see an additional entry there for the “2014 April Update.”  To help you focus on the more important changes to the instructions, some parts of the attached summary have been highlighted in yellow to draw your attention.










Relationship Designators for Contributors
I.3.1
The relationship designator for “editor of compilation” has been deleted, and the concept incorporated into a revised relationship designator for “editor.”



Fast Track changes
An attached PDF file (see link below) identifies the "Fast Track" changes to RDA that will be included in this release (6JSC-Sec-12-rev.pdf); Fast Track changes are not added to the RDA Update History.  Among the changes most likely to be of interest to LC staff:
7.26.1.3: The instruction has been changed from “transcribe the statement of projection” to “record the projection of cartographic content” because other cartographic content attributes are recorded.
There are several new and revised relationship designators for Appendix J including these:
opera adaptation of (work)   Reciprocal relationship: adapted as opera (work)
container of (work)  [replaces contains (work)]
music (work)  Reciprocal relationship: music for (work)
continuation in part of (work)   [replaces continues in part (work)]
replacement in part of (work)   [replaces supersedes in part (work)]
replacement of (work)     Reciprocal relationship: replaced by (work)  [replaces supersedes (work) and superseded by (work)]
merged to form (work)   [replaces merged with … to form … (work)]
There are several new and revised relationship designators for Appendix K including these:
member   [replaces group member]
family
corporate body  [replaces group member of]
component of a merger
corporate member
membership corporate body
predecessor of split
There are several new and revised glossary terms including these:
Exhibit
Illustration
Image File
Unnumbered Leaf
Unnumbered Page
TOPIC 2: Change in Content in LC-PCC PSs
A summary of LC-PCC PS updates incorporated in this release is attached (LCPCCPS_changes_2014_April.doc) (see link below).  Many of the changes to the LC-PCC PSs are related to RDA changes (re-numbering, new references, etc.).  Several PSs are being deleted because the content has been incorporated into RDA itself or the RDA update makes the PS obsolete (e.g., to remove reference to the PCC interim guidelines on treaties).  Significant changes to PSs you should be aware of:
9.19.1.2.6:  New statement to record LC practice/PCC practice for a new Optional addition.  For new authority records, catalogers may apply the option to supply “Other Designation Associated with a Person” in the authorized access point. For existing authority records, unless otherwise changing an existing heading (e.g., conflict, incorrect dates), do not change an existing AACR2 or RDA heading merely to add an “other designation”.
11.13.1.2:  Re-captioned to “Type of Corporate Body” due to changes in RDA; guidelines applying to access points formerly found in the Policy Statement at 11.7.1.4 have been moved here.  New alternative guidelines on using the spelled-out forms of a preferred name that is an initialism or acronym have been provided.
16.2.2.13 and 16.4:  Revised the U.S. Townships section in each of these PSs.
TOPIC 3: Functional Changes in the RDA Toolkit
An excerpt from ALA Publishing on the updates to the functionality of the RDA Toolkit with this release is found at the end of this email.
The next planned release of the RDA Toolkit will be in August 2014, although the update is most likely to impact functional changes to the Toolkit, and synchronization of translations.  The October 2014 release will include content updates for RDA and the LC-PCC PSs.
The documents attached to this email may also be found on the Web:
LC Summary of 2014 RDA Updates: http://www.loc.gov/aba/rda/added_docs.html   
Fast Track entries included in the April 2014 update of the RDA Toolkit: http://www.rda-jsc.org/docs/6JSC-Sec-12-rev.pdf
Changes in LC-PCC Policy Statements in the April 2014 release of the RDA Toolkit: http://www.loc.gov/aba/rda/lcps_access.html


[Source: Library of Congress]