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]


See also:

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

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

Friday, April 25, 2014

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

RESOURCE DESCRIPTION & ACCESS RDA

Loading...
Loading...


See is infographic in full screen: Corrected Titles Proper & Variant Titles : RDA vs AACR2


See also:

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

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

Saturday, April 19, 2014

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
111Main entry—Meeting name19.2Creator
111Main entry—Meeting name19.3Other Person, Family, or Corporate Body Associated with a Work
111aMeeting name or jurisdiction name as entry element11.2.2Preferred Name for the Corporate Body
111aMeeting name or jurisdiction name as entry element11.3.3Location of Headquarters, etc.
111aMeeting name or jurisdiction name as entry element11.4.3Date of Establishment
111aMeeting name or jurisdiction name as entry element11.4.4Date of Termination
111aMeeting name or jurisdiction name as entry element11.5Associated Institution
111aMeeting name or jurisdiction name as entry element11.7Other Designation Associated with the Corporate Body
111cLocation of meeting11.3.2Location of Conference, etc.
111cLocation of meeting11.5Associated Institution
111dDate of meeting11.4.2Date of Conference, etc. (Core Element)
111dDate of meeting6.4Date of Work
111eSubordinate unit11.2.2Preferred Name for the Corporate Body
111fDate of a work6.10Date of Expression
111gMiscellaneous informationN/A
111jRelator term18.5Relationship Designator
111kForm subheading6.2.2Preferred Title for the Work
111lLanguage of a work6.11Language of Expression
111nNumber of part/section/meeting6.2.2Preferred Title for the Work
111nNumber of part/section/meeting6.3Form of Work
111nNumber of part/section/meeting6.4Date of Work
111nNumber of part/section/meeting6.5Place of Origin of the Work
111nNumber of part/section/meeting6.6Other Distinguishing Characteristic of the Work
111nNumber of part/section/meeting11.6Number of a Conference, etc.
111pName of part/section of a work6.2.2Preferred Title for the Work
111pName of part/section of a work6.3Form of Work
111pName of part/section of a work6.4Date of Work
111pName of part/section of a work6.5Place of Origin of the Work
111pName of part/section of a work6.6Other Distinguishing Characteristic of the Work
111qName of meeting following jurisdiction name entry element11.2.2Preferred Name for the Corporate Body
111tTitle of a work6.2.2Preferred Title for the Work
111tTitle of a work6.3Form of Work
111tTitle of a work6.4Date of Work
111tTitle of a work6.5Place of Origin of the Work
111tTitle of a work6.6Other Distinguishing Characteristic of the Work
111uAffiliation11.9Address of the Corporate Body

[Source: RDA Toolkit]



See also:

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

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

Monday, April 7, 2014

111 - Main Entry-Meeting Name (NR) - MARC 21

111 - Main Entry-Meeting Name (NR)


First IndicatorSecond Indicator
Type of meeting name entry element
0 - Inverted name
1 - Jurisdiction name
2 - Name in direct order
Undefined
# - Undefined

Subfield Codes
  • $a - Meeting name or jurisdiction name as entry element (NR)
  • $c - Location of meeting (R)
  • $d - Date of meeting (NR)
  • $e - Subordinate unit (R)
  • $f - Date of a work (NR)
  • $g - Miscellaneous information (R)
  • $j - Relator term (R)
  • $k - Form subheading (R)
  • $l - Language of a work (NR)
  • $n - Number of part/section/meeting (R)
  • $p - Name of part/section of a work (R)
  • $q - Name of meeting following jurisdiction name entry element (NR)
  • $t - Title of a work (NR)
  • $u - Affiliation (NR)
  • $0 - Authority record control number or standard number (R)
  • $4 - Relator code (R)
  • $6 - Linkage (NR)
  • $8 - Field link and sequence number (R)

FIELD DEFINITION AND SCOPE

Meeting or conference name used as a main entry in a bibliographic record.
According to various cataloging rules, main entry under a meeting name is assigned to works that contain proceedings, reports, etc.
Meetings entered subordinately to a corporate body that are used as main entries are recorded in field 110.

GUIDELINES FOR APPLYING CONTENT DESIGNATORS

Descriptions of the first indicator position and all subfield codes, as well as input conventions for the 111 field, are given in the X11 Meeting Names-General Information section. Because the second indicator is different for various X11 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: