4Resource Description and Access (RDA) Succeeds AACR2Based 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 tasksIs a content standardRDA is more than a revision of AACR2Attempts 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 structureRDA was intentionally built on the foundations of AACRMany RDA instructions are derived from AACR2Cataloging records created according to RDA guidelines will be compatible with AACR recordsRDA 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.
5RDA Addresses User Tasks FRBRFindIdentifySelectObtainFRADFindIdentifyContextualizeJustifyThe first objective of RDA is responsiveness to user needsEach section begins with a general chapter where the functional objectives and principles are statedFunctional objectives relate the section’s instructions back to the user tasks“Convenience of the user”—ICP’s highest principle
6Developed for the Future When authority and bibliographic data are packaged separatelyWhen access points can be assembled on the flyWhat data for works and expressions can be reused for multiple manifestationsRDA elements are independent, separate units of bibliographic or authority dataRDA moves away from the concatenation of different units of information into one long string of charactersEmphasis on data elements opens the possibility:For using any element as a search term or search limitFlexibility in displaying dataRecording data in defined, unambiguous elements prepares for RDA to move into a formally registered metadata element setAACR2 “other physical details” records information ranging from illustrative content to details about base material or projection speedRDA segments the data into separate elementsDiscrete 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.
7Organization AACR2, part 1 is organized by ISBD area RDAAACR2, part 1 is organized by ISBD areaSeparate chapters for classes of materials, e.g. books, continuing resource, etc.Print resource intended to be read linearlyRDA is organized by FRBR entities and relationshipsSections that contain separate elements based on the identify and relate goalsOnline resource not intended to be read linearlyRDA is a product of thorough deconstruction of AACR2During collective deconstruction of Part I of AACR2 all individual rules:Were taken out of chaptersRemoved from “class of material” structureReworded from AACR2 to fit RDA’s vocabularyEliminatedChangedGeneralizedAdded-- 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 searchTable of content paneFollowing linksRDA Toolkit TipAdvanced 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 onlyTillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 1.” Microsoft Powerpoint file.
8RDA Construction New terminology Controlled vocabularies Closed – example: Media typeNot closed – example: FrequencyNew concepts (FRBR, FRAD)New structureSome new instructionsSome changed instructionsRDA uses FRBR and FRAD conceptual model vocabularyRDA Controlled Vocabularies: “Closed” and “Not Closed”Not Closed = cataloger assigns a term from an open list, or, if no term applies, cataloger supplies termFrequencyClosed = cataloger assigns a term from a closed list.Media typeComplete list summarized in the RDA Controlled Vocabularies: “Not Closed” and “Closed” document
9RDA Structure Functional organization Core, Core If, LC Core+ Element choices:AlternativesExceptionsOptional omissions & additionsOrAgency creating the dataLocal policies & decisionsRDA is the application of FRBR and FRAD conceptual modelsRDA itself is not a conceptual model – it’s a set of instructions based on the FRBR & FRAD modelsVocabulary reflects FRBR and FRAD languageCore 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 tasksCore is a floor, not a ceiling“Core If”Instructions that are core if a condition is metIf the use of a core element depends on a situation, the label “CORE ELEMENT” is followed by a explanation of that situationLC 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 tasksSimilar to AACR2 full level descriptionNCSU is applying LC Core+ during the RDA testElement choices:RDA is flexible, as a result, there are choicesAlternatives: instructions to do something different from the previous instructionUsually allow a cataloger to do something different than the previous instructionExample: 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 situationOptional omission or addition: instructions to do less or more than the previous instruction, usually using cataloger’s judgmentExample: Rule of 3 – RDAOr: provides a choice on how to apply an RDA instruction, usually using cataloger’s judgmentNot labeled as alternativesMost represent local policy decisionsExample: 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.
10RDA Core Elements (Manifestation and Item) Title ProperStatement of Responsibility Relating to Title ProperDesignation of EditionNumbering of SerialsCore If: Production Statement (for unpublished resources)Publication StatementCore If: Distribution StatementCore If: Manufacture StatementCopyright DateSeries StatementIdentifier for the ManifestationCarrier TypeExtentRDA 0.6.2Why are there Core If’s in the Core Element Set?Date, place and person/organization/institution responsible for the resource’s publication are requiredSo … Production statement is Core If the resource is unpublished. This fulfills the date requirementPublication, Distribution and Manufacture statements work in a cascade effect, which we’ll cover in more detail laterEssentially, a resource must have one of these statementsSo … A Distribution Statement is Core If a Publication Statement is lackingAndA Manufacture Statement is Core If both a Publication Statement and Distribution Statement are lackingRDA Core Elements for Work and Expression are at RDA 0.6.3LC Core+LC defined additional RDA elements, beyond the RDA Core Elements, which they will be encoding for the testLC Core+ is similar to AACR2 full level record description (blank or I)We are following LC’s policy and encoding at the LC Core+ levelRemember RDA Core is a floor, LC is opting to record more data as a service to their patronsLC 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 needsTraining Document 3 – RDA Elements (included in your packet)Lists the RDA Core and Core If ElementsLists additional elements that are considered LC Core+
11AACR2 to RDA Vocabulary AACR2 Term RDA Term Heading Authorized access pointAuthor, composer, etc.CreatorMain entryPreferred title + authorized access point for creatorUniform titlePreferred title (+ other title information to differentiate)Conventional collective titleGMDMedia type +Carrier type +Content typePhysical descriptionCarrier descriptionChief source of informationPreferred sourceMultivolume monographMultipart monographI 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 elementsFor 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.
12RDA Organization Attributes of an item (RDA Section 1) Item identifier (e.g. barcode number)Provenance of itemMarks/inscriptionsAttributes of a manifestation (RDA Section 1)Publisher/distributorDate of publication/distributionForm of carrierExtent of carrierAttributes of an expression (RDA Section 2)Form of expressionLanguage of expressionType of score (musical notation)Scale (cartographic image/object)Attributes of a work (RDA Section 2)Form of workMedium of performance (musical work)Coordinates (cartographic work)RDA is organized by FRBR attributes, not format like AACR2Instructions for formats, notes, etc. are interspersed throughout the textRule numbers do not correspond with sections. Rules are numbered by chapter not section.Attributes of an item – specific to piece in-handLocal noteAttributes of a manifestationTitle properStatement of responsibilityDesignation of editionTitle proper of seriesMARC identifier for the manifestation (e.g. ISBN, ISSN or other Standard Number)Attributes of expressionContent typeLanguage of ExpressionAttributes of an workPreferred title for the work (authority record)Creator (authority record)Oliver, Chris. Introducing RDA: A Guide to the Basics. Chicago: American Library Association, Print.
13Library of Congress Policy Statements (LCPS) RDA LCPS are comparable to AACR2 Library of Congress Rule Interpretations (LCRI)Currently available only in Cataloger’s DesktopCataloger’s Desktop access is one-directionalFor RDA, we will use LCPS (Library of Congress Policy Statements) much the same way we use LCRI for AACR2Jacquie 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 LCPSLike 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 testLCPS’ 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 whenCataloger’s Desktop access is one-directional:To access and read an LCPS you need to use Cataloger’s DesktopCataloger’s Desktop will link you to the corresponding RDA rule in RDA ToolkitRDA Toolkit will not indicate there is a corresponding LCPS at an RDA ruleAll locally reviewed LCPS’ are bookmarked in RDA ToolkitNote: You must be logged into the NCSU Shared account to see themThe 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.
14RDA Toolkit Login – Twice as Nice Functionality Tabs Logins available on M&C Confluence pagesFunctionalityBrowseQuick SearchAdvanced SearchTabsRDAToolsResourcesLogin – Twice as NiceBecause 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 policyThe first login gains you access to RDA ToolkitThe second login gains you access to the NCSU Shared profile, which includes our LCPS bookmarksPlease do not edit or personalize either login!FunctionalityBrowse provides TOC access to all 3 tabsQuick search will perform both keyword and rule number searchesAdvanced search allows you to define how RDA Toolkit is searched – handy ifTabsRDA: RDA textTools:Want to know how RDA maps to MARC and vice-versa? Tools > RDA MappingsLooking for a list of Core elements? Tools > Entity Relationship DiagramsResources: Text of AACR2Setting up Cataloger’s Desktop to automatically login to RDA Toolkit:Login to Cataloger’s DesktopAt the Welcome screen, Select “Preferences” icon from the far left menu (called the “Rail pane”) – the icon looks like a gearAt the Preferences screen, Select the “General Preferences” icon from the far left menu – the icon looks like a yellow gearScroll to the bottom of the window to the RDA sectionEnter 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
15RDA and ISBDRDA is a content standard and does not prescribe encoding schemaFor the test, we are encoding RDA in MARC, which prescribes ISBD PresentationISBD Presentation: RDA Appendix D.1
16ISBD 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.BracketingEach data element is enclosed in a full set of brackets260 $a [Washington, D.C.] : $b [G.P.O?], $c [2009?]RDA D.1 ISBD Presentation
17Ten Things to Remember User needs/user tasks “Take what you see” Work, Expression, Manifestation, ItemCore and Core IfAlternatives, optional omissions and optional additionsFewer abbreviationsContent, Media and Carrier typesNo more “rule of 3”Sources of information expandedControlled vocabulariesUser needs/users tasks – cataloger’s judgment instructions should be based on thisTake what you see – Principle of RepresentationWork, Expression, Manifestation and ItemCore and Core If – speaks to user needs/user tasksAlternatives, optional options and optional additions – speaks to user needs/user tasksFewer abbreviations – speaks to user needs/user tasks and “take what you see”Content, Media and Carrier types – replacing GMDNo more “rule of 3” – cataloger’s judgment is appliedSources of information expandedControlled vocabularies – closed and not closed-- Adapted from: Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 8.” Microsoft Powerpoint file.
19Access Points Vocabulary AACR2RDAHeadingAuthorized access pointSee referenceVariant access pointAuthorCreatorUniform titlePreferred title or Conventional collective titleMain entryAuthorized access point for creator + preferred titleCreator is core in bibliographic records.Maxwell, Robert. Utah Library Association Annual Conference. St. George, Utah. 7 May RDA in Depth.
20Scope of PersonRDA = “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 entitiesNon-human entities (e.g., Miss Piggy, Snoopy) now in scope if presented as having responsibility in some way for a work, expression, manifestation, or itemIn 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 individualThe 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.
21Preferred Form of Name Retain hyphens between forename and surname Choose the form most commonly knownVariant 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 $cRetain hyphens between forename and surnameInsert space after full stop following initialsPCC practice now in RDATwo 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.
22Preferred 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.
23Dates Associated with Persons Months are not abbreviated1936 December 17If date is known to be one of two years, each is given in 4 digits, separated by “or”1735 or 1736Abbreviations “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.
24Changes 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 …,…, flourishedMaxwell, Robert. “RDA in Depth.” PDF file.
25Title of the PersonRDA 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 comma100 $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.
26Core Elements to Distinguish Core If: The following elements are core if needed to break a conflict with an existing authorized access pointFuller form of nameField of activity of the personProfession or occupationSome 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.
27Fuller 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, orA part of the name not included in the form chosen as the preferred nameCore If: Fuller form of name is core if needed to break a conflictMARC: give the fuller form of the name in 100 $q, recorded within parenthesis100 $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.
28Field 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 personif needed to distinguish one person from another with the same nameMARC: 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; orwhen 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.
29Profession 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 personif needed to distinguish one person from another with the same nameMARC: record profession or occupation in 100 $c, enclosed in parenthesisRDA: 100 $a Watt, James $c (Gardener)AACR2: 100 $a Watt, James, $c gardenerSimilarly, “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.
30Another 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 officeinitials of academic degreesinitials denoting membership in an organizationAACR2100 $a Smith, John, $c M.D., $d flRDA100 $a Smith, John $c (Doctor) $d flourishedRDARDA 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.
32Scope 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.
33General Guidelines Capitalization of name – see RDA appendix A.2 Numbers in name in found formOrdinal numeral connected to meeting, etc. -- see RDAAccents in name as found; add if neededAbbreviations in name – see RDA appendix B.2General 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.
34Preferred Name for the Corporate Body RDAChoose the form most commonly knownVariant 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.
35Location of Conference, Fair, Festival, Congress, etc. RDACorePlace is given in its authorized access point formNo “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.
36MARC 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.
37Date 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 distinguishDate associated with the corporate body is a core element in two situations:1) as the date or dates of a conference or similar event2) 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.
38Number of a ConferenceRDA 11.6: “Designation of the sequencing of a conference, etc., within a series of conferences, etc.”Recorded as an ordinal numeral from any sourceRecorded as $n in access pointNo separate MARC field for this elementNumber 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.
39Core Elements to Distinguish The following elements are Core If needed to break a conflict:Location of headquarters, etc.Associated institutionOther designation associated with a corporate bodySome 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.
40Location of Headquarters, etc. RDA :Country, state, province, etc., or local place of headquarters, orGeographic area of corporate body’s activitiesCore If: Core if needed to distinguish one corporate body from another with the same nameIn form as authorized access pointLocation 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.
41MARC 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.
42MARC 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.
43Associated Institution RDA 11.5Core 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 determinedif needed to distinguish one corporate body from another with the same nameRecorded 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.
44MARC 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.
45Other Designation Associated with the Corporate Body RDA 11.7:a word, phrase, or abbreviation indicating incorporation or legal statusany 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 bodyIf needed to distinguish one corporate body from another with the same nameThe 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.
46MARC 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.
47Other Changes for Corporate Bodies RDA : for conferences, congresses, meetings, exhibitions, fairs, festivals, etc.Retain frequency in the name of a conference, congress, or meetingOmit year of convocation from the name of an exhibition, fair, or festivalAACR2: 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.
48MARC 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.
49MARC 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 rda100 1_$a Brown, George $c (Clergyman). $t Poems400 1_$a Brown, George $c (Clergyman). $t Complete poems of George BrownRDA 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.
50Topics We’re Skipping Terms of Address Names of Saints or Spirits (RDA 9.6)New MARC Authority Record Fields (partial list)04637XNew subfields for 7XX fields
51Relationship Designators Terms previously known as “relator terms”
52Terms Cover Relationships between Resource and Person(s) Resource and Family or FamiliesResource and Corporate Body or BodiesWorks, Expressions, Manifestations and ItemsPersons, Families and Corporate BodiesUsed in authority recordsConcepts, Objects, Events and PlacesUnder developmentRDA Appendix I covers relationships between Resources and Person(s), Family/Families and Corporate Body/BodiesRDA Appendix J covers relationships between Works, Expressions, Manifestations and ItemssRDA Appendix K covers relationships between Person(s), Families and Corporate BodiesRDA Appendix L will cover relationships between Concepts, Objects, Events and Places
53Terms v. Codes Spelled out term 700-711 $e 700-730 $i 76X-78X $i Term or PhraseCodeSpelled out term$e$i76X-78X $iClosed vocabularyListed in RDA Appendices3-character code$4$476X-78X $4Closed vocabularyMARC code list -- /relaterm.htmlWe 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)
54Resource and Person(s), Corporate Body, or Family Relationships Not CoreRequired for Illustrators of Children’s Resources per LCPS I.3.1RDA Appendix IMARC 1XX, subfield $eRepeatable subfield, separated with commaTry not to be repetitiveFor example, we’ve seen no use of $e author in a 1XX field for a textual work.Remember, Appendix I contains Relationship designator terms
55Resource 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.
56Resource and Person(s) and Corporate Body Relationship Examples Title statement: Tolkien Society home pageVarying form of title: Welcome to the Tolkein Society home page710 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.
57Work, Expression, Manifestation and Item Relationships Not CoreRDA Appendix JMARC subfield $iGive $i as first subfieldMARC 76X-78X subfield $iIf 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 relationshipIn other words, if the 76X-78X second indicator adequately conveys the relationship, prefer that to use of $iAll relationships in Appendix J appear to be covered by second indicator valuesRemember, Appendix J contains Relationship designator phrasesMARC 76X-78X subfield $iJust for the record, the only field we can imagine using these in for continuing resources is the MARC 787Most other types of relationships are coded in the second indicator
58Work, 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 prejudice730 $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 slidesThese are our best guess on how the $i would be implemented
59Preferred Title (MARC 130) RDA 6.2Core element (RDA 6.2.2) when needed to differentiate an expression of a work from another expression of the same work.MARC 130 field
60Authorized 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 pointIf 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.
61Additions to Access Points Representing Works (RDA 126.96.36.199) 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.
62Examples 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 scienceAll of the following examples are taken from
63Examples 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)
64Place 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)
65Other 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 nameGuillaume (Chanson de geste)To distinguish the access point for the work from the access point for the 13th century person known as GuillaumeFor instructions on additions to access points representing special types of works, see RDA (musical works) and (legal works).
66What 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; andomitting the testament for individuals books or groups of works.
68Preferred TitleRDA 6.2.2Do 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 properAACR2 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.2Specific 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 )
69Changes from AACR2No longer routinely omit introductory phrases (e.g., “Here beginneth …”) and statements of responsibilityPreferred title based on first manifestation receivedIf 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 receivedRDA 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.
70Preferred Title for Compilations of One Person, Family or Body RDACategories:Complete works = use “Works”Complete works in a single form = use term chosen by catalogerOther compilations of two or more works in same form or different forms = give preferred title for each workIf 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.
71Alternative for “Other Compilations” Instead of or in addition to giving the preferred title for each work, use a conventional collective title, e.g.,:Works. SelectionsPosters. SelectionsOrchestra music. SelectionsHowever, 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.
72Compilation 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.
73Compilation of Two Works by the Same Creator RDA with alternative for conventional collective title100 $a Miller, Arthur, $d240 $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.
74Compilation 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.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.4Tillet, Barbara B. and Judith A. Kuhagen. “RDA Test ‘Train the Trainer’ Module 4.” Microsoft Powerpoint file.
75Compilation of Two Works by the Same Creator RDA with alternative for conventional collective title100 $a Miller, Arthur, $d240 $a Plays. $k Selections245 $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.
76Compilation 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.
77Compilation 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.