RDA Training: Day One Christee Pascale, Associate Head, Metadata & Cataloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina.

RDA Training: Day One Christee Pascale, Associate Head, Metadata & Cataloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina State University Libraries September 8-10, 2010

Day One Program Introducing RDA Access Points Relationship Designators
Preferred Title

Introducing RDA

Resource Description and Access (RDA)
Succeeds AACR2 Based on IFLA International models and principles: FRBR (Functional Requirements for Bibliographic Records) FRAD (Functional Requirements for Authority Data) Statement of International Cataloging Principles (ICP) Addresses FRBR & FRAD user tasks Is a content standard RDA is more than a revision of AACR2 Attempts to address deep-seated problems of AACR (lack of flexibility, extensibility) RDA is the product of a process of deconstruction (AACR2) and then reconstruction (RDA) around a new framework (FRBR and FRAD conceptual models) Important links continue to exist between AACR2 and RDA: AACR and RDA share the same governance structure RDA was intentionally built on the foundations of AACR Many RDA instructions are derived from AACR2 Cataloging records created according to RDA guidelines will be compatible with AACR records RDA was born out of an initial attempt to do a radical revision of AACR -- Oliver, Chris. Introducing RDA: a Guide to the Basics. Chicago: American Library Association, Print.

RDA Addresses User Tasks
FRBR Find Identify Select Obtain FRAD Find Identify Contextualize Justify The first objective of RDA is responsiveness to user needs Each section begins with a general chapter where the functional objectives and principles are stated Functional objectives relate the section’s instructions back to the user tasks “Convenience of the user”—ICP’s highest principle

Developed for the Future
When authority and bibliographic data are packaged separately When access points can be assembled on the fly What data for works and expressions can be reused for multiple manifestations RDA elements are independent, separate units of bibliographic or authority data RDA moves away from the concatenation of different units of information into one long string of characters Emphasis on data elements opens the possibility: For using any element as a search term or search limit Flexibility in displaying data Recording data in defined, unambiguous elements prepares for RDA to move into a formally registered metadata element set AACR2 “other physical details” records information ranging from illustrative content to details about base material or projection speed RDA segments the data into separate elements Discrete data is adaptable -- Oliver, Chris. Introducing RDA: A Guide to the Basics. Chicago: American Library Association, Print. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 1.” Microsoft Powerpoint file.

Organization AACR2, part 1 is organized by ISBD area
RDA AACR2, part 1 is organized by ISBD area Separate chapters for classes of materials, e.g. books, continuing resource, etc. Print resource intended to be read linearly RDA is organized by FRBR entities and relationships Sections that contain separate elements based on the identify and relate goals Online resource not intended to be read linearly RDA is a product of thorough deconstruction of AACR2 During collective deconstruction of Part I of AACR2 all individual rules: Were taken out of chapters Removed from “class of material” structure Reworded from AACR2 to fit RDA’s vocabulary Eliminated Changed Generalized Added -- Oliver, Chris. Introducing RDA: A Guide to the Basics. Chicago: American Library Association, Print. As you know from using other online tools such as Cataloger’s Desktop, you don’t read the content in such a tool the same way you read a printed text on paper. Instead, you’re using keyword searches, following links, etc. 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 different ways: Keyword search Table of content pane Following links RDA Toolkit Tip Advanced search allows you to limit results by: Content type (e.g. text or moving image only) Media type (e.g. computer, unmediated, or video only) Issuance type (e.g. multipart monographs, serials or single units only) If you only want to see search results relating to just monographic books, use content type = text only and issuance type = single units only Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 1.” Microsoft Powerpoint file.

RDA Construction New terminology Controlled vocabularies
Closed – example: Media type Not closed – example: Frequency New concepts (FRBR, FRAD) New structure Some new instructions Some changed instructions RDA uses FRBR and FRAD conceptual model vocabulary RDA Controlled Vocabularies: “Closed” and “Not Closed” Not Closed = cataloger assigns a term from an open list, or, if no term applies, cataloger supplies term Frequency Closed = cataloger assigns a term from a closed list. Media type Complete list summarized in the RDA Controlled Vocabularies: “Not Closed” and “Closed” document

RDA Structure Functional organization Core, Core If, LC Core+
Element choices: Alternatives Exceptions Optional omissions & additions Or Agency creating the data Local policies & decisions RDA is the application of FRBR and FRAD conceptual models RDA itself is not a conceptual model – it’s a set of instructions based on the FRBR & FRAD models Vocabulary reflects FRBR and FRAD language Core elements v. “Levels of Description” RDA does not identify “levels of description” “Core elements contain data about the attributes and relationships that have the highest value in fulfilling users tasks,” (White 61) Core element set is the minimum description required to achieve the basic FRBR or FRAD users tasks Core is a floor, not a ceiling “Core If” Instructions that are core if a condition is met If the use of a core element depends on a situation, the label “CORE ELEMENT” is followed by a explanation of that situation LC Core+ Library of Congress has defined an additional set of RDA elements that they locally define as Core, meaning, these elements directly support the FRBR and FRAD users tasks Similar to AACR2 full level description NCSU is applying LC Core+ during the RDA test Element choices: RDA is flexible, as a result, there are choices Alternatives: instructions to do something different from the previous instruction Usually allow a cataloger to do something different than the previous instruction Example: Using the label on a DVD rather than viewing the title frame(s) Exceptions: provide instruction on how to apply an RDA instruction when there is an exceptional situation Optional omission or addition: instructions to do less or more than the previous instruction, usually using cataloger’s judgment Example: Rule of 3 – RDA Or: provides a choice on how to apply an RDA instruction, usually using cataloger’s judgment Not labeled as alternatives Most represent local policy decisions Example: When giving the extent of a resource lacking page numbering, give: (1) the exact number of pages, (2) an estimated number of pages with “approximately”, or (3) “1 volume (unpaged)” Agency creating the data: allows for the cataloging agency to make a judgment, choices relate to language, script, transliteration, calendar and numeric system -- Adapted from: Tillett, Barbara B. and Judith A. Kuhagen. American Library Association Midwinter Meeting. Boston, MA. 15 January RDA Test “Train the Trainer” Module 2.

RDA Core Elements (Manifestation and Item)
Title Proper Statement of Responsibility Relating to Title Proper Designation of Edition Numbering of Serials Core If: Production Statement (for unpublished resources) Publication Statement Core If: Distribution Statement Core If: Manufacture Statement Copyright Date Series Statement Identifier for the Manifestation Carrier Type Extent RDA 0.6.2 Why are there Core If’s in the Core Element Set? Date, place and person/organization/institution responsible for the resource’s publication are required So … Production statement is Core If the resource is unpublished. This fulfills the date requirement Publication, Distribution and Manufacture statements work in a cascade effect, which we’ll cover in more detail later Essentially, a resource must have one of these statements So … A Distribution Statement is Core If a Publication Statement is lacking And A Manufacture Statement is Core If both a Publication Statement and Distribution Statement are lacking RDA Core Elements for Work and Expression are at RDA 0.6.3 LC Core+ LC defined additional RDA elements, beyond the RDA Core Elements, which they will be encoding for the test LC Core+ is similar to AACR2 full level record description (blank or I) We are following LC’s policy and encoding at the LC Core+ level Remember RDA Core is a floor, LC is opting to record more data as a service to their patrons LC Core+ represents a consideration of FRBR and FRAD user tasks and what type of data needs to be included in their records to accommodate those needs Training Document 3 – RDA Elements (included in your packet) Lists the RDA Core and Core If Elements Lists additional elements that are considered LC Core+

AACR2 to RDA Vocabulary AACR2 Term RDA Term Heading
Authorized access point Author, composer, etc. Creator Main entry Preferred title + authorized access point for creator Uniform title Preferred title (+ other title information to differentiate) Conventional collective title GMD Media type + Carrier type + Content type Physical description Carrier description Chief source of information Preferred source Multivolume monograph Multipart monograph I already mentioned there is new terminology in RDA. Here you see some of the main concepts expressed in AACR2 and then in RDA. Some of the changes reflect turning away from the catalog card environment and some reflect terminology in the Functional Requirements models and the International Cataloguing Principles. A “heading” (related to its position on a 3x5 card) is really an authorized access point; the author, composer, artist, etc., is a creator. What AACR2 calls the main entry is composed of the preferred title and, if appropriate, the authorized access point for the creator. The AACR2 term “uniform title” applied to multiple different situations. The counterparts in RDA are two: first, the preferred title (much more about that later) and any differentiating information; second, a conventional collective title such as “Works.” The GMD, often an inconsistent presentation of different categories of information, has been replaced by three elements: media type, carrier type, and content type. The second and third are core elements For chief source of information, also note that the change is not only in the term but also that the sources for information have been expanded. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 1.” Microsoft Powerpoint file.

RDA Organization Attributes of an item (RDA Section 1)
Item identifier (e.g. barcode number) Provenance of item Marks/inscriptions Attributes of a manifestation (RDA Section 1) Publisher/distributor Date of publication/distribution Form of carrier Extent of carrier Attributes of an expression (RDA Section 2) Form of expression Language of expression Type of score (musical notation) Scale (cartographic image/object) Attributes of a work (RDA Section 2) Form of work Medium of performance (musical work) Coordinates (cartographic work) RDA is organized by FRBR attributes, not format like AACR2 Instructions for formats, notes, etc. are interspersed throughout the text Rule numbers do not correspond with sections. Rules are numbered by chapter not section. Attributes of an item – specific to piece in-hand Local note Attributes of a manifestation Title proper Statement of responsibility Designation of edition Title proper of series MARC identifier for the manifestation (e.g. ISBN, ISSN or other Standard Number) Attributes of expression Content type Language of Expression Attributes of an work Preferred title for the work (authority record) Creator (authority record) Oliver, Chris. Introducing RDA: A Guide to the Basics. Chicago: American Library Association, Print.

Library of Congress Policy Statements (LCPS)
RDA LCPS are comparable to AACR2 Library of Congress Rule Interpretations (LCRI) Currently available only in Cataloger’s Desktop Cataloger’s Desktop access is one-directional For RDA, we will use LCPS (Library of Congress Policy Statements) much the same way we use LCRI for AACR2 Jacquie and I have reviewed the majority of LCPS’ and made local policy decisions about when we will be following (or in a few select instances not following) an LCPS Like LC, our goal in determining when and when not apply an LCPS was guided by our current cataloging practice – we are not significantly changing our local cataloging policy or procedures for the test LCPS’ are not currently available in RDA Toolkit, only in Cataloger’s Desktop (and the LC RDA Test website) LCPS will be available in RDA Toolkit, we just don’t know when Cataloger’s Desktop access is one-directional: To access and read an LCPS you need to use Cataloger’s Desktop Cataloger’s Desktop will link you to the corresponding RDA rule in RDA Toolkit RDA Toolkit will not indicate there is a corresponding LCPS at an RDA rule All locally reviewed LCPS’ are bookmarked in RDA Toolkit Note: You must be logged into the NCSU Shared account to see them The bookmarks indicate there is an LCPS at the RDA rule and our local policy. To read the LCPS you will need to open Cataloger’s Desktop, find the corresponding LCPS and read it.

RDA Toolkit Login – Twice as Nice Functionality Tabs
Logins available on M&C Confluence pages Functionality Browse Quick Search Advanced Search Tabs RDA Tools Resources Login – Twice as Nice Because the LCPS are not yet in RDA Toolkit, we created a shared profile for M&C with bookmarks in the RDA text to indicate where we are applying local policy The first login gains you access to RDA Toolkit The second login gains you access to the NCSU Shared profile, which includes our LCPS bookmarks Please do not edit or personalize either login! Functionality Browse provides TOC access to all 3 tabs Quick search will perform both keyword and rule number searches Advanced search allows you to define how RDA Toolkit is searched – handy if Tabs RDA: RDA text Tools: Want to know how RDA maps to MARC and vice-versa? Tools > RDA Mappings Looking for a list of Core elements? Tools > Entity Relationship Diagrams Resources: Text of AACR2 Setting up Cataloger’s Desktop to automatically login to RDA Toolkit: Login to Cataloger’s Desktop At the Welcome screen, Select “Preferences” icon from the far left menu (called the “Rail pane”) – the icon looks like a gear At the Preferences screen, Select the “General Preferences” icon from the far left menu – the icon looks like a yellow gear Scroll to the bottom of the window to the RDA section Enter the NCSU Test Login (the first login) into the RDA Username and RDA Password boxes (the login is available on the M&C Confluence site) Select Save

RDA and ISBD RDA is a content standard and does not prescribe encoding schema For the test, we are encoding RDA in MARC, which prescribes ISBD Presentation ISBD Presentation: RDA Appendix D.1

ISBD Conventions in RDA
Ending Punctuation “When punctuation occurring within or at the end of an element is retained, give it with normal spacing. Prescribed punctuation is always added, even though double punctuation may result.” (RDA D.1) 3rd ed.. Not: 3rd ed. Bracketing Each data element is enclosed in a full set of brackets 260 $a [Washington, D.C.] : $b [G.P.O?], $c [2009?] RDA D.1 ISBD Presentation

Ten Things to Remember User needs/user tasks “Take what you see”
Work, Expression, Manifestation, Item Core and Core If Alternatives, optional omissions and optional additions Fewer abbreviations Content, Media and Carrier types No more “rule of 3” Sources of information expanded Controlled vocabularies User needs/users tasks – cataloger’s judgment instructions should be based on this Take what you see – Principle of Representation Work, Expression, Manifestation and Item Core and Core If – speaks to user needs/user tasks Alternatives, optional options and optional additions – speaks to user needs/user tasks Fewer abbreviations – speaks to user needs/user tasks and “take what you see” Content, Media and Carrier types – replacing GMD No more “rule of 3” – cataloger’s judgment is applied Sources of information expanded Controlled vocabularies – closed and not closed -- Adapted from: Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 8.” Microsoft Powerpoint file.

Authorized Access Point: Persons
RDA 8 (General guidelines) RDA 9 (Identifying persons)

Access Points Vocabulary
AACR2 RDA Heading Authorized access point See reference Variant access point Author Creator Uniform title Preferred title or Conventional collective title Main entry Authorized access point for creator + preferred title Creator is core in bibliographic records. Maxwell, Robert. Utah Library Association Annual Conference. St. George, Utah. 7 May RDA in Depth.

Scope of Person RDA = “An individual or an identity established by an individual (either alone or in collaboration with one or more other individuals)” RDA 9.0: Includes fictitious entities Non-human entities (e.g., Miss Piggy, Snoopy) now in scope if presented as having responsibility in some way for a work, expression, manifestation, or item In RDA a person can be an individual or an identity established by one individual alone or an identity established in collaboration with one or more other individuals portrayed as being one individual The scope statement at RDA 9.0 includes fictitious entities as persons. So, non-human entities can now be represented by authorized access points as creators, or whatever role they play., if they are presented on the resource as being responsible in some way for the work, expression, manifestation, or item... Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Preferred Form of Name Retain hyphens between forename and surname
Choose the form most commonly known Variant spellings: choose the form found in the first resource received (RDA ) For names containing a surname, include words, etc., indicating relationships (e.g., Jr., Sr., IV) -- not just to differentiate (RDA ) Marc: encode the term in the 100 $c Retain hyphens between forename and surname Insert space after full stop following initials PCC practice now in RDA Two other changes from AACR2 when determining the form of the preferred name are shown here: 1) if spellings vary, choose the form found in the first resource received, not the predominant spelling; 2) for names containing a surname, words, etc., indicating relationships are part of the preferred name rather than used only as additions to the name to break a conflict. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Preferred Form of Name … Changes from AACR2 Examples
RDA: 100 $a Rogers, Roy, $c Jr., $d AACR2: 100 $a Rogers, Roy, $d RDA: 100 $a Smith, Ann-Marie, $d AACR2: 100 $a Smith, Ann Marie, $d RDA: 100 $a James, P. D. AACR2: 100 $a James, P. D.

Dates Associated with Persons
Months are not abbreviated 1936 December 17 If date is known to be one of two years, each is given in 4 digits, separated by “or” 1735 or 1736 Abbreviations “cent.,” “ca.,” “b.,” “d.,” and “fl.” not used “cent.” becomes “century” “approximately” replaces “ca.” “b.” and “d.” dates can use hyphens instead of words “fl.” becomes “flourished” Abbreviations not used no longer appear in Appendix B. When it doubt, check the appendix. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Changes to AACR2 Practice -- Persons
RDA …, 15th cent. …, ca ca. 1896 …, b. 1825 …, d. 1945 …, fl …, 15th century …, approximately approximately 1896 …, born 1825 or …, …, died 1945 or …, …, flourished Maxwell, Robert. “RDA in Depth.” PDF file.

Title of the Person RDA 9.4: “Word or phrase indicative of royalty, nobility, or ecclesiastical rank or office, or a term of address for a person of religious vocation.” MARC: Give title in 100 $c, preceded by a comma 100 $a Carl $b XVI Gustaf, $c King of Sweden, $d 1946- The core element :Title of the person” is applicable for the categories of persons given in this scope statement. In an access point, this element is given in subfield $c and is preceded by a comma in the previous subfield. There isn’t a separate MARC field for this element. So subfield $c is a mixture of titles and parts of names like junior, senior, and so on. Note that new MARC fields we’ve already discussed reappear as appropriate in subsequent examples. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Core Elements to Distinguish
Core If: The following elements are core if needed to break a conflict with an existing authorized access point Fuller form of name Field of activity of the person Profession or occupation Some elements for persons are ‘core” when they are needed to break conflicts between the same preferred names for different persons. Because RDA is not an encoding standard, it doesn’t prescribe how those distinguishing elements should be recorded. RDA says in that those elements can be given as additions to the authorized access point, as separate elements, or as both. During the RDA Test, these elements should be given as part of the authorized access point; each agency can decide if they will also be given as separate elements. Many of these elements were identified in FRAD. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Fuller Form of Name RDA 9.5:
Full form of a part of a name represented only by an initial or abbreviation in the form chosen as the preferred name, or A part of the name not included in the form chosen as the preferred name Core If: Fuller form of name is core if needed to break a conflict MARC: give the fuller form of the name in 100 $q, recorded within parenthesis 100 $a Smith, Nancy E. $q (Nancy Elizabeth) 100 $a Williams, John $q (John Dudley) The scope of the element “Fuller form of name” has been expanded: it can include a part of the name not included in the form chosen as the preferred name (in AACR2, adding such a part of name was allowed only when breaking a conflict). As a core element, “Fuller form of name” is given only when distinguishing one name from another name. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Field of Activity of the Person
RDA 9.15: “Field of endeavour, area of expertise, etc., in which a person is engaged or was engaged” Core: for a person whose name consists of a phrase or appellation not conveying the idea of a person if needed to distinguish one person from another with the same name MARC: Give field of activity in 100 $c, enclosed in parenthesis: RDA: 100 $a Spotted Horse $c (Crow Indian chief) AACR2: 100 $a Spotted Horse $c (Crow Indian chief) From FRAD, we have “Field of activity” as a core element in two different situations: when the name of the person doesn’t convey the idea of a person; or when this information is needed to distinguish one name from another. MARC: For RDA the field of activity is enclosed in parenthesis. (Note: In AACR2, some were preceded by a comma, which is not RDA practice.) Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Profession or Occupation
RDA 9.16: “A profession or occupation in which a person works or has worked” Core If: only for a person whose name consists of a phrase or appellation not conveying the idea of a person if needed to distinguish one person from another with the same name MARC: record profession or occupation in 100 $c, enclosed in parenthesis RDA: 100 $a Watt, James $c (Gardener) AACR2: 100 $a Watt, James, $c gardener Similarly, “Profession or occupation” is another element with two core aspects: when the name of the person doesn’t convey the idea of a person; when this information is needed to distinguish one name from another. MARC: For RDA the field of activity is enclosed in parenthesis. (Note: In AACR2, some were preceded by a comma, which is not RDA practice.) Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 5.” Microsoft Powerpoint file.

Another Change from AACR2 for Persons
Do not use the following elements when constructing an RDA authorized access point for a person: titles of position or office initials of academic degrees initials denoting membership in an organization AACR2 100 $a Smith, John, $c M.D., $d fl RDA 100 $a Smith, John $c (Doctor) $d flourished RDA RDA follows FRAD for the data elements used to identify persons, families, and corporate bodies. For now, it does not include specific elements for titles of position or office, initials of academic degrees, or initials denoting membership in an organization – which AACR2 included.

Authorized Access Point: Corporate Bodies
RDA 8 (General guidelines) RDA 11 (Indentifying Corporate Bodies)

Scope of Corporate Body
RDA 8.1.2: “An organization or group of persons and/or organizations that is identified by a particular name and that acts, or may act, as a unit” Includes ad hoc events (such as athletic contests, exhibitions, expeditions, fairs, and festivals) and vessels (e.g., ships and spacecraft) For now, RDA includes ad hoc events in the scope of corporate bodies. That may change when the IFLA group developing FRSAD (the conceptual model for subject authority data) finishes its work because events are considered subjects in the Functional Requirements models. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

General Guidelines Capitalization of name – see RDA appendix A.2
Numbers in name in found form Ordinal numeral connected to meeting, etc. -- see RDA Accents in name as found; add if needed Abbreviations in name – see RDA appendix B.2 General guidelines on recording the form of name are given in RDA Most of the guidelines are based on the “Take what you see” principle. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Preferred Name for the Corporate Body
RDA Choose the form most commonly known Variant spellings: choose the form found in the first resource received (RDA ) One change from AACR2 for choosing the form of the preferred name is related to spelling variations: choose the form found in the first resource received, not the predominant spelling. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Location of Conference, Fair, Festival, Congress, etc.
RDA Core Place is given in its authorized access point form No “rule of three” – there is no restriction on the number of places to give (RDA E.2.2.4) If conference held online, location is “Online” The next core element is Location of conference, etc. (the “etc.” includes congresses, meetings, exhibitions, fairs, festivals, and other such events), Listed here are three changes from AACR2: 1) the place is given in its form as an authorized access point; 2) there is no restriction on the number of places to give; 3) when the conference is held online, “online” is given as the place. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

MARC for Location of Conference
Location is given in 110, 111 $c $National and Household Food Security Workshop $d (2003 : $c Lusaka, Zambia) In access points, Location is given in subfield $c. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Date Associate with a Corporate Body
RDA 11.4: “Date(s) of a conference, etc., or date of establishment/termination of a corporate body.” Generally a year or years unless need to be more specific to distinguish Date associated with the corporate body is a core element in two situations: 1) as the date or dates of a conference or similar event 2) as the date of establishment or termination of a corporate body. We discovered while proofreading that there is a discrepancy about the status as a core element for date of establishment or termination: always core or only core if a date is needed to break a conflict. After the JSC clarifies this glitch, this slide will be updated. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Number of a Conference RDA 11.6: “Designation of the sequencing of a conference, etc., within a series of conferences, etc.” Recorded as an ordinal numeral from any source Recorded as $n in access point No separate MARC field for this element Number of a conference is a core element; it is given in subfield $n in an access point. There is not a separate field for this element. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Core Elements to Distinguish
The following elements are Core If needed to break a conflict: Location of headquarters, etc. Associated institution Other designation associated with a corporate body Some elements for corporate bodies are core if they are needed to break conflicts between the same preferred names for different bodies. Because RDA is not an encoding standard, it doesn’t prescribe how those distinguishing elements should be recorded. RDA says in that those elements can be given as additions to the authorized access point, as separate elements, or as both. During the RDA Test, these elements should be given as part of the authorized access point. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Location of Headquarters, etc.
RDA : Country, state, province, etc., or local place of headquarters, or Geographic area of corporate body’s activities Core If: Core if needed to distinguish one corporate body from another with the same name In form as authorized access point Location of headquarters is a core element if needed to break a conflict; it is given in its form as an authorized access point. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

MARC for Location of Headquarters, etc.
Recorded in access point, added in parentheses to the preferred name of the corporate body $a Sociedad Nacional de Agricultura (Chile) In an access point, Location of headquarters is added in parentheses to the preferred name of the corporate body. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

MARC for Date Associated with a Corporate Body
Access point for conference, etc. record date in $d $a Olympic Winter Games $n (21st : $d 2010 : $c Vancouver, B.C.) Access point for other corporate body, added in parenthesis (no subfield) $Gesellschaft fur Musikforschung (1946-) Here are examples showing the dates being added in both the access points. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Associated Institution
RDA 11.5 Core If: for conferences, etc., if the institution’s name provides better identification than the local place name or if the local place name is unknown or cannot be readily determined if needed to distinguish one corporate body from another with the same name Recorded in the form and language preferred by the institution (not the authorized access point) Associated institution is a core element in these two situations: 1) as a substitute for local place for a conference, etc.; 2) if needed to break conflicts. The form of this element is an exception: it is given in its form as a preferred name, not in its form as an authorized access point. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

MARC for Associated Institution
Conference, etc.: record associated institution in a $c for $a International Conference on Georgian Psalmody $n (2nd : $d 1997 : $c Colchester Institute) All other access points: add to the preferred name of the corporate body $a B’nai B’rith Hillel Federation Jewish Student Center (University of Cincinnati) The MARC coding in access points varies: give it in a subfield $c for conferences, etc.; for other access points, add it to the preferred name of the corporate body. Here are two examples showing this element in access points: in subfield $c in the first example; just added to the preferred name in the 2nd example. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Other Designation Associated with the Corporate Body
RDA 11.7: a word, phrase, or abbreviation indicating incorporation or legal status any term serving to differentiate the body from other corporate bodies, persons, etc. Core If: For a body whose name does not convey the idea of a corporate body If needed to distinguish one corporate body from another with the same name The last “Core if” element is Other designation associated with the corporate body. Its use as a core element occurs in two situations: when the preferred name for a body doesn’t convey the idea of a corporate body; when needed to break conflicts. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

MARC for Other Designation Associated with the Corporate Body
Record in access point, add term in parentheses to the preferred name of the corporate body (subfielding may vary) $a Beanpot (Hockey tournament) 151 $a Korea (South) In an access point, this element is added in parentheses to the preferred name of the body. There is no separate MARC field for this element. Beanpot is a hockey tournament involving Northeastern and three other local universities. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

Other Changes for Corporate Bodies
RDA : for conferences, congresses, meetings, exhibitions, fairs, festivals, etc. Retain frequency in the name of a conference, congress, or meeting Omit year of convocation from the name of an exhibition, fair, or festival AACR2: 111 2_ $a Expo $d (1967 : $c Montreal, Québec) RDA: 111 2_ $a Expo 67 $c (Montreal, Québec) Explained on this slide are other changes from AACR2 related to corporate bodies. Having only one RDA instruction means changes from AACR2 in what is retained in the preferred name of these corporate bodies. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 7.” Microsoft Powerpoint file.

MARC Authority Records for TEST Period
AACR2 and RDA forms different, single entity involved. Existing AACR2 authority record, heading not revised: 008/10 c [AACR2] 046 __$f [may be added by PCC tester] 370 __$a Shreveport, La. [may be added by PCC tester] 100 1_$a Williams, Hank, $d 1949- 700 17$a Williams, Hank, $c Jr., $d $2 rda [must be added by PCC tester] Partial Record Examples (for illustration, not all applicable fields are shown) The RDA elements of any authority record may or may not be there before you read the auth record during the test. We can’t add anything, but we want you to see how they may look.

MARC Authority Records for TEST Period
AACR2 and RDA forms different, needed as part of another entity. Existing AACR2 authority record, heading not revised: 008/ c [AACR2] 100 1_$a Brown, George, $c Rev. 700 17$a Brown, George $c (Clergyman) $2 rda [must be added by PCC tester] New RDA authority record: [must be added by PCC tester] 008/ z [other] 040 __$e rda 100 1_$a Brown, George $c (Clergyman). $t Poems 400 1_$a Brown, George $c (Clergyman). $t Complete poems of George Brown RDA says to use profession/occupation since rev. (reverend) is an honorific used for the profession of “clergyman,” we now use clergyman. There is no controlled vocabulary of professions.

Topics We’re Skipping Terms of Address
Names of Saints or Spirits (RDA 9.6) New MARC Authority Record Fields (partial list) 046 37X New subfields for 7XX fields

Relationship Designators
Terms previously known as “relator terms”

Terms Cover Relationships between Resource and Person(s)
Resource and Family or Families Resource and Corporate Body or Bodies Works, Expressions, Manifestations and Items Persons, Families and Corporate Bodies Used in authority records Concepts, Objects, Events and Places Under development RDA Appendix I covers relationships between Resources and Person(s), Family/Families and Corporate Body/Bodies RDA Appendix J covers relationships between Works, Expressions, Manifestations and Itemss RDA Appendix K covers relationships between Person(s), Families and Corporate Bodies RDA Appendix L will cover relationships between Concepts, Objects, Events and Places

Terms v. Codes Spelled out term 700-711 $e 700-730 $i 76X-78X $i
Term or Phrase Code Spelled out term $e $i 76X-78X $i Closed vocabulary Listed in RDA Appendices 3-character code $4 $4 76X-78X $4 Closed vocabulary MARC code list /relaterm.html We use $e in MARC when entering a Relationship designator term (from RDA Appendix I) We use $i in MARC when entering a Relationship designator phrase (from RDA Appendix J)

Resource and Person(s), Corporate Body, or Family Relationships
Not Core Required for Illustrators of Children’s Resources per LCPS I.3.1 RDA Appendix I MARC 1XX, subfield $e Repeatable subfield, separated with comma Try not to be repetitive For example, we’ve seen no use of $e author in a 1XX field for a textual work. Remember, Appendix I contains Relationship designator terms

Resource and Person(s) and Corporate Body Relationship Examples
Edition statement : “Abridged by Ruth Fraser. “ 700 1_ $a Fraser, Ruth, $e abridger. Title statement: 219 days by Kalan Porter. 100 1_ $a Porter, Kalan, $e composer, $e singer. Title statement: Encoding across frontiers, Proceedings of the European Conference on Encoded Archival Description and Context (EAD and EAC), Paris, France 7-8 October Bill Stockting, Fabienne Queyroux, editors. 700 1_ $a Stockting, Bill, $e editor of compilation. 700 1_ $a Queyroux, Fabienne, $e editor of compilation.

Resource and Person(s) and Corporate Body Relationship Examples
Title statement: Tolkien Society home page Varying form of title: Welcome to the Tolkein Society home page 710 2_ $a Tolkien Society (England), $e issuing body. Title statement: For whom the bell tolls, the Spanish Civil War produced by the Hoover Institution and KTEH/San Jose Public Television ; director, Paul Marca. 710 2_ $a Hoover Institution on War, Revolution, and Peace, $e film producer. 710 2_ $a $a KTEH-TV (Television station : San Jose, Calif.), $e film producer.

Work, Expression, Manifestation and Item Relationships
Not Core RDA Appendix J MARC subfield $i Give $i as first subfield MARC 76X-78X subfield $i If the element used to record the relationship (e.g., related work) is considered sufficient for the purposes of the agency creating the data, do not use a relationship designator to indicate the specific nature of the relationship In other words, if the 76X-78X second indicator adequately conveys the relationship, prefer that to use of $i All relationships in Appendix J appear to be covered by second indicator values Remember, Appendix J contains Relationship designator phrases MARC 76X-78X subfield $i Just for the record, the only field we can imagine using these in for continuing resources is the MARC 787 Most other types of relationships are coded in the second indicator

Work, Expression, Manifestation and Item Relationships Examples
We have yet to see relationships designator phrases used in RDA Toolkit so we’re going to make a few up based on the MARBI Proposal … 700 $i parody of (work)$a Austen, Jane, $d $t Pride and prejudice 730 $i prequel $s Star wars, episode I, the phantom menace (Motion picture) 730 $i prequel to $s Star wars (Motion picture) MARBI Proposal was adopted: MARC $i is available for use in 7XX fields as noted in previous slides These are our best guess on how the $i would be implemented

Preferred Title (MARC 130)
RDA 6.2 Core element (RDA 6.2.2) when needed to differentiate an expression of a work from another expression of the same work. MARC 130 field

Authorized Access Points Representing Works and Expressions (RDA 5.5)
When constructing an authorized access point to represent a work or expression, use the preferred title for the work (see RDA 6.2.2) as the basis for the access point If two or more works are represented by the same or similar access points, add to the access point representing the work an element or elements such as form of work, date, place of origin, or other distinguishing term.

Additions to Access Points Representing Works (RDA 6.27.1.9)
Form of work (see RDA 6.3) Date of the work (see RDA 6.4) Place of origin of the work (see RDA 6.5) Other distinguishing characteristic (see RDA 6.6) Four categories of qualifiers, can be used in conjunction with each other as appropriate.

Examples of Form Charlemagne (Play) Charlemagne (Tapestry)
Nutcracker (Choreographic work) NuTCRACKER (Computer file) Animal reproduction science (Online) --as opposed to the print version of Animal reproduction science All of the following examples are taken from

Examples of Date Qualifier
Bulletin (New York State Museum : 1945) Bulletin (New York State Museum : 1976) Dublin magazine (1762) Dublin magazine (1965) Ocean’s eleven (Motion picture : 1960) Ocean’s eleven (Motion picture : 2001)

Place of Origin Advocate (Boise, Idaho) Advocate (Nairobi, Kenya)
Blue book contractors register (New York-New Jersey- Connecticut edition) Blue book contractors register (Southern California edition)

Other Distinguishing Characteristic
Scottish History Society (Series) To distinguish the access point for the work from the access point for the corporate body of the same name Guillaume (Chanson de geste) To distinguish the access point for the work from the access point for the 13th century person known as Guillaume For instructions on additions to access points representing special types of works, see RDA (musical works) and (legal works).

What We’re Skipping Preferred titles: Parts of the Bible
There are two changes from AACR2 for the preferred title for parts of the Bible: not using abbreviations for the testaments; and omitting the testament for individuals books or groups of works.

Preferred Title (MARC 240)
RDA 6.2

Preferred Title RDA 6.2.2 Do not name the compilation by the first work in the compilation as AACR2 does in some situations, because doing so misidentifies the aggregate work. Give the appropriate authorized access point for each work/expression in the aggregate work. If no collective title, alternative is to devise a title proper AACR2 says to base the main entry for some compilations on the first work in the compilation; that is a problem because that choice misidentifies that aggregate work. RDA doesn’t have the comparable instructions to those AACR2 rules. Instead, give the appropriate authorized access point for each work/expression in the aggregate work. Sometimes such compilations lack a collective title; there is an RDA alternative to devise a title proper in such situations. General instructions in RDA 6.2 Specific instructions: parts (RDA 6.2.2) compilations (RDA 6.2.2) some musical works (RDA ) some legal works (RDA ) some religious works (RDA ) some official communications (RDA )

Changes from AACR2 No longer routinely omit introductory phrases (e.g., “Here beginneth …”) and statements of responsibility Preferred title based on first manifestation received If later manifestations have different forms, determine the most common form of the preferred title -- it may not have such a phrase or statement “Selections” not used alone as the preferred title -- instead, “Works. Selections” For simultaneous publications with different titles: choice based on first resource received RDA changes the AACR2 rule on omissions from the title of the work. Don’t omit introductory phrases or statements of responsibility from a title UNTIL there is evidence of more than one form of title and the most common form can be determined. “Selections” is no longer to be used by itself as a preferred title. We’ll come back to this topic when we look at conventional collective titles. When simultaneous publications have different titles, the choice of preferred title is now based on the first resource received. An example is on the next slide. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

Preferred Title for Compilations of One Person, Family or Body
RDA Categories: Complete works = use “Works” Complete works in a single form = use term chosen by cataloger Other compilations of two or more works in same form or different forms = give preferred title for each work If the compilation has works by a single person, family, or corporate body, the basic instruction for preferred titles says that the preferred title for the compilation may be one of two possible conventional collective titles: 1) Works if the compilation represents the complete works of the creator; 2) A term chosen by the cataloger if the compilation contains the complete works of a single form. No longer will a cataloger need to determine what AACR2 requires: knowing if the creator created works only in a single form. For any other compilation, preferred titles are given for each separate work. Note that there are some additional instructions about conventional collective titles in the section for musical works. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

Alternative for “Other Compilations”
Instead of or in addition to giving the preferred title for each work, use a conventional collective title, e.g.,: Works. Selections Posters. Selections Orchestra music. Selections However, there is an alternative for the last category on the previous slide: instead of giving separate preferred titles for each work, you can use one preferred title consisting of either “Works” or a term for a single form + the term “Selections.” Or you can give this single conventional collective title in addition to the preferred titles for the separate works. (These points are illustrated on the following slides.) Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

Compilation of Two Works by the Same Creator
AACR2 100 $a Miller, Arthur, $d $a Archbishop’s ceiling 245 $a Two plays / $c Arthur Miller. 505 $a The Archbishop’s ceiling – The American clock. Now let’s look at some compilation examples. This first one shows how a compilation of two works by the same creator would be cataloged according to AACR2, using the title of the first work as the uniform title. [If asked: AACR2 rule 25.7] Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

RDA with alternative for conventional collective title 100 $a Miller, Arthur, $d 240 $a Plays. $k Selections $a The Archbishop’s ceiling; and, The American Clock : $b two plays / $c Arthur Miller, with an introduction by the author. 700 $a Miller, Arthur, $d $t Archbishop’s ceiling. 700 $a Miller, Arthur, $d $t American clock. The basic RDA instruction says to name the works separately (shown here in the 700 fields). An alternative says a conventional collective title shown here in the 240 field can be used in addition to the 700 field. The alternative also says the 240 field can be used in lieu of the 700 fields. According to RDA , the title proper is still transcribed as found (and it gives rules on where a title can be constructed from if none is found on piece). Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

AACR2 100 $a Miller, Arthur, $d $a Archbishop’s ceiling 245 $a [Two plays] / $c Arthur Miller. 505 $a The Archbishop’s ceiling – The American clock. This example is showing the way we’d have devised a title proper in AACR2 when no title page for the collection existed, but where there was information on the titles elsewhere in the text. Give note, brackets or both. RDA 2.2.4 Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

RDA with alternative for conventional collective title 100 $a Miller, Arthur, $d 240 $a Plays. $k Selections 245 $a [The Archbishop’s ceiling ; The American clock] / $c Arthur Miller. 700 $a Miller, Arthur, $d $t Archbishop’s ceiling. $a Miller, Arthur, $d $t American clock. This is an example in RDA of devising a title proper based on information in the manifestation. The titles of the plays are probably on a TOC, or have individual heading pages, but no title page per se. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

Compilation of Works by Different Creators
AACR2 100 $a Polk, Sharon. 240 $a Community band concerts 245 $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson. 700 $a Swanson, Terri. $t Fall harvest festivals. When a compilation lacks a collective title, AACR2 says to use the first work as the main entry for the compilation. [If asked: AACR2 21.7C. With collective title, enter under title: AACR2 21.7B.] Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

Compilation of Works by Different Creators
RDA with alternative for devised title 245 $a Community band concerts / $c Sharon Polk. Fall harvest festivals / Terri Swanson. 700 $a Polk, Sharon. $t Community band concerts. 700 $a Swanson, Terri. $t Fall harvest festivals. Applying the basic RDA instruction results in 700 fields for each work. Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.

RDA Training: Day One Christee Pascale, Associate Head, Metadata & Cataloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina.

Similar presentations

Presentation on theme: "RDA Training: Day One Christee Pascale, Associate Head, Metadata & Cataloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

RDA Training: Day One Christee Pascale, Associate Head, Metadata & Cataloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina.

Similar presentations

Presentation on theme: "RDA Training: Day One Christee Pascale, Associate Head, Metadata & Cataloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina."— Presentation transcript:

Similar presentations

About project

Feedback