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

130 - Main Entry-Uniform Title (NR)

First Indicator	Second 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: 

• Library of Congress >> MARC >> Bibliographic >> 1XX >> 130 [LC]
• 130  Main Entry–Uniform Title (NR) [OCLC]

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. ... ... ... 

Read now complete article: Alternatives Options and Exceptions in RDA : What Every Cataloger Needs to Know

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.

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:

• Bibliographic Framework Initiative
• BIBFRAME

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]

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

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

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

Authorized Access Point - Meeting Name - MARC to RDA Mapping

MARC 21 FIELD TAG	MARC 21 SUBFIELD CODE	MARC 21 FIELD / SUBFIELD NAME	RDA INSTRUCTION NUMBER	RDA ELEMENT NAME
111		Main entry—Meeting name	19.2	Creator
111		Main entry—Meeting name	19.3	Other Person, Family, or Corporate Body Associated with a Work
111	a	Meeting name or jurisdiction name as entry element	11.2.2	Preferred Name for the Corporate Body
111	a	Meeting name or jurisdiction name as entry element	11.3.3	Location of Headquarters, etc.
111	a	Meeting name or jurisdiction name as entry element	11.4.3	Date of Establishment
111	a	Meeting name or jurisdiction name as entry element	11.4.4	Date of Termination
111	a	Meeting name or jurisdiction name as entry element	11.5	Associated Institution
111	a	Meeting name or jurisdiction name as entry element	11.7	Other Designation Associated with the Corporate Body
111	c	Location of meeting	11.3.2	Location of Conference, etc.
111	c	Location of meeting	11.5	Associated Institution
111	d	Date of meeting	11.4.2	Date of Conference, etc. (Core Element)
111	d	Date of meeting	6.4	Date of Work
111	e	Subordinate unit	11.2.2	Preferred Name for the Corporate Body
111	f	Date of a work	6.10	Date of Expression
111	g	Miscellaneous information	N/A
111	j	Relator term	18.5	Relationship Designator
111	k	Form subheading	6.2.2	Preferred Title for the Work
111	l	Language of a work	6.11	Language of Expression
111	n	Number of part/section/meeting	6.2.2	Preferred Title for the Work
111	n	Number of part/section/meeting	6.3	Form of Work
111	n	Number of part/section/meeting	6.4	Date of Work
111	n	Number of part/section/meeting	6.5	Place of Origin of the Work
111	n	Number of part/section/meeting	6.6	Other Distinguishing Characteristic of the Work
111	n	Number of part/section/meeting	11.6	Number of a Conference, etc.
111	p	Name of part/section of a work	6.2.2	Preferred Title for the Work
111	p	Name of part/section of a work	6.3	Form of Work
111	p	Name of part/section of a work	6.4	Date of Work
111	p	Name of part/section of a work	6.5	Place of Origin of the Work
111	p	Name of part/section of a work	6.6	Other Distinguishing Characteristic of the Work
111	q	Name of meeting following jurisdiction name entry element	11.2.2	Preferred Name for the Corporate Body
111	t	Title of a work	6.2.2	Preferred Title for the Work
111	t	Title of a work	6.3	Form of Work
111	t	Title of a work	6.4	Date of Work
111	t	Title of a work	6.5	Place of Origin of the Work
111	t	Title of a work	6.6	Other Distinguishing Characteristic of the Work
111	u	Affiliation	11.9	Address of the Corporate Body

[Source: RDA Toolkit]

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