Nomens and Appelations
Report on Application Profiles webinar 2019 August
Choices and options were introduced to RDA due to the needs of various other countries and non-library users of RDA, and to make RDA more compatible for the data communities. Agreement could not be reached with everyone on a single set of standards. Application profiles are primarily designed for machine usability (machine-generated cataloging). Application profiles help make the decisions on options by specifying the metadata used. They may include the entities, elements, vocabulary encoding schemes (e.g. thesauri), mandatory and repeatability status of elements, string encoding scheme (specifies values to include, e.g. sub-elements of a publication statement). RDA Application Profile includes only RDA elements with their recording method, optional instruction, policy statement, links to RDA instructions. Experts in where to find what they need in RDA and how to decide among options don't need an application profile, they would just use RDA. You can make your own application profiles using a table, narrative, spreadsheet. Specific profiles might be needed for different resource types (AV, manuscripts, etc.), sector (public or academic or school library), community users (cultural, language). Application Files Working Group may start work Fall 2019 to look at profile architecture and management, what additional guidance and documentation needs to be added to the Toolkit, and technical issues including encoding formats. They hope to show a working application profile by the end of the year. My 2 cents: 1. It seems to me that, although there apparently are more options and some new concepts, we have probably already done this to great extent when RDA first came out, deciding what options to apply or not (KLN spreadsheet of RDA practices), what you would use (e.g. relators) or not, and trained our staff to do that. NOW they're giving us their blessing to use our cataloger's judgment. 2. Application profiles for resource type sounds like AACR2 chapters.
Diachronic Works are multi-part items, sort of like a kit. Especially digital materials, e.g. a web page that changes over time.
Alternative labels are just various ways of referring to something. Example from BETA Toolkit: "Hast carrier type" vs. "Type of carrier."
Retired labels does not mean the labels are retired/not used any more. It refers to the type of label--labels for or in retired elements, e.g. 780 and 785 fields
Entities have elements, all of which are optional; elements have recording methods and individual (mostly optional) instructions
Optional Omission, Optional Addition
Also "or" ; "considered appropriate" ; "use another" ; alternative"
Application profiles help make the decisions on options by specifying the metadata used.
Transcription Guidelines: choice of cataloging agency
Instruction [i.e. rule] numbers--replaced by random permanent searchable citation numbers
PDF of Index--will have to search instead
Links between AACR2 and RDA
From: Program for Cooperative Cataloging <PCCLIST@LISTSERV.LOC.GOV> On Behalf Of Jennifer W. Baxmeyer
Sent: Wednesday, December 11, 2019 2:41 PM
Subject: [PCCLIST] PCC and the new RDA (was: New task groups for RDA and LC-PCC Policy Statements)
Dear PCC colleagues,
This updates the email sent on August 21, 2019, by Beacher Wiggins and Xiaoli Li, announcing the formation of four LC-PCC task groups charged with working on specific areas of the new RDA that will likely require revised or new policy statements: aggregates, data provenance, diachronic works, and RDA element labels.
The four task groups have been working since the end of August and have submitted monthly reports to the Policy Committee and LC. The timeline for completing the recommendations related to policy statements in the beta RDA Toolkit has been modified slightly. LC still plans to begin loading existing policy statements into the beta RDA Toolkit in January, and final recommendations will be reviewed and decisions made by the end of May 2020.
The beta Toolkit will be launched as the new RDA Toolkit on Tuesday, December 15, 2020, but this will NOT be the PCC implementation date for the new RDA. The decision for a PCC implementation date for the new RDA will be made sometime between September and November 2020, after the new RDA workflow documents and policy statements have been loaded and evaluated. A later implementation date will also provide PCC with time to create proper documentation and ensure training materials are in place.
More information regarding LC-PCC policy statements and workflow documents in the beta RDA Toolkit is on the PCC website: https://www.loc.gov/aba/pcc/documents/PoCo-2019/BetaRDA-PoCo-Decisions.pdf [loc.gov].
As a reminder, catalogers should continue to use the current RDA Toolkit, which contains the official versions of RDA and the LC-PCC Policy Statements, for their current work.
Jennifer Baxmeyer (she/her)
Chair, PCC Policy Committee
Interim Assistant University Librarian for Metadata Services
Princeton University Library
693 Alexander Road
Princeton NJ 08540
Andruss Library | 570-389-4205 | email@example.com
©Copyright Bloomsburg University of Pennsylvania • 400 East Second Street, Bloomsburg PA 17815-1301 • 570.389.4000