Downloaded 68 times
![Key changes: General
Spelling out of abbreviations
p. pages
ill. illustrations
cm is not an abbreviation, it is a symbol, like ©
Latin terms no longer used
[S.l. : s.n.] [Place of publication not identified] :
[publisher not identified]
[et al.] [and # others]
[sic] 245 has title as appears on piece; 246 contains
corrected form of title
Adjacent bracketed elements are bracketed
separately](https://image.slidesharecdn.com/rda-20for-20original-20catalogers-130903113133-/85/RDA-for-Original-Catalogers-37-320.jpg)
![Key changes: Serials
300 field is core for currently published, tangible non-print
formats
Carrier type changes (338)
RDA 3.1.6.1: Create a new description if there is a change in
the carrier type of a serial to online resource from another
computer carrier, or vice versa
Transcription exceptions:
Omit numbering from title proper or parallel title (use mark of omission
wherever in title)
Some alternatives allow some conversions and some omissions for some
elements
No more manifestation level differentiation
[Reminder]: ISSN key title (222) is at manifestation level, NOT
work or expression title, so key title and authorized access
point for the work may not match
45](https://image.slidesharecdn.com/rda-20for-20original-20catalogers-130903113133-/85/RDA-for-Original-Catalogers-45-320.jpg)
Uploaded byShana McDanold
RDA for Original Catalogers
This document provides an overview of a two-day training course on RDA for original catalogers. Day one will cover the background and history of RDA, FRBR concepts, authority records, and cataloging monographic materials using RDA. Day two will cover cataloging serials, audiovisual materials, online resources, and provider-neutral records using RDA, as well as relationships. The document outlines the course, provides context on the development and testing of RDA, and previews some of the key changes and concepts in RDA compared to AACR2.
More Related Content
Similar to RDA for Original Catalogers
RDA for Original Catalogers
- 1. RDA for OriginalCatalogers Shana L. McDanold Head, Metadata Services
- 2. Introductions and Acknowledgments Who am I and why am I teaching this? Attendees intro Slide content credits: Adam Schiff (University of Washington) Library of Congress Barbara Tillett, Judy Kuhagen, the staff of the Cataloging & Acquisitions Cooperative and Instructional Programs Division Jacquie Samples (Duke U.) Kathy Glennan (U. of MD) Joint Steering Committee for the Development of RDA And many more who have contributed bits and pieces
- 3. Course outline Day1 RDA – where did it come from? FRBR – the core concepts Authorities aka Authorized Access Points Hybrid records Bibliographic records - print monographs (with practice) Day 2 Bibliographic records – serials (with practice) Bibliographic records - A/V (with practice) Bibliographic records - online and Provider Neutral (with practice) What’s next? Relationships! Wrap-up
- 4. Day 1 Background, GeneralRDA, and Monographic Materials
- 5. Cataloging brief history Early cataloging codes No “one” set for US libraries 1940s: ALA cataloging rules 1961 IFLA’s Paris Principles Cutter’s Rules for a Printed Dictionary Catalog 1967: Anglo-American Cataloging Rules (AACR) 2 versions!: North American text and a British text 1969: ISBDs (consolidated in 2007) 1978: Anglo-American Cataloging Rules Revised (AACR2) Revisions: 1988, 1998, 2002 1960s: MARC developed (Henriette Avram) Work completed 1969 US standard by 1971; international standard 1973 Several “flavors” of MARC
- 6. So why RDA?And why now? AACR2 is based on a card environment, thus it is limited by that 3x5 inch boundary RDA is designed for the web and online communication, making use of how intertwined the web is to share information From RDA 0.0 Purpose and Scope: “RDA provides a set of guidelines and instructions on formulating data to support resource discovery.” “RDA provides a comprehensive set of guidelines and instructions covering all types of content and media.”
- 7. So why RDA?And why now? RDA Objectives (RDA 0.4.2): Responsiveness to user needs Cost efficiency Flexibility Continuity RDA Principles (RDA 0.4.3) Differentiation Sufficiency Relationships Representation Accuracy Attribution Common usage or practice Uniformity
- 8. So why RDA?And why now? Specific RDA Goals Easy to use and interpret Applicable to an online, networked environment Provide effective bibliographic control for all types of media Encourage use beyond library community Compatible with other similar standards Have a logical structure based on internationally agreed-upon principles Separate content and carrier data, and separate content from display Examples – numerous and appropriate
- 9. RDA – thebirth story 2005: Final update of AACR2 2002 ed. 1997: International Conference on the Principles & Future Development of AACR 2002: AACR3 development begins 2003-2007: meetings of the International Cataloguing Principles (ICP) 2005: AACR3 renamed RDA: Resource Description and Access 2006, 2007: drafts of RDA chapters and appendices 2008: first full draft of RDA 2009: delivered to the publishers 2010: first published in the RDA Toolkit 2010/2011: testing, testing 2012: re-writing by an editor, other tasks designated by U.S. Test Coordinating Committee March 31, 2013: RDA implementation!
- 10. RDA – testing,testing Goal: assure the operational, technical, and economic feasibility of RDA Who: U.S. RDA Test Coordinating Committee Test participants: Library of Congress, National Agricultural Library, National Library of Medicine, 23 partner institutions Timeline: June-Sept. 2010: training Oct.-Dec. 2010: record creation Jan.-Mar. 2011: analyze results Apr.-June 2011: report and decision
- 11. RDA – testing,testing Questions answered by the test and the reports Does RDA meet the stated goals? What is user reaction to the records? What is the economic impact? How was the data being assessed and collected? Review and analysis of records Surveys Statistics on time Record use and impact in shared environment (OCLC, SkyRiver) to ensure RDA/AACR2 compatibility
- 12. RDA – testing,testing CONCLUSION! Finally. Decision published June 13, 2011 Overarching conclusion: “Contingent on the satisfactory progress/completion of the tasks and action items below, the Coordinating Committee recommends that RDA should be implemented by LC,NAL, and NLM no sooner than January 2013. The three national libraries should commit resources to ensure progress is made on these activities that will require significant effort from many in and beyond the library community.”
- 13. FRBR family? Family: FRBR: Functional Requirements for Bibliographic Records FRAD: Functional Requirements for Authority Data FRSAD: Functional Requirements for Subject Authority Data Conceptual model used as the foundation for RDA FRBR: WEMI attributes/elements (resource) FRAD/FRSAD: entitles (persons, corporate bodies) and subjects (concepts) associated with the resource Focus: user tasks and relationships
- 14. FRBR User Tasks Find to locate either a single entity or a set of entities as the result of a search using an attribute or relationship of the entity Identify to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar characteristics Select to choose an entity that meets the user's requirements with respect to content, physical format, etc., or to reject an entity as being inappropriate to the user's needs Obtain to acquire an entity through purchase, loan, etc., or to access an entity electronically through an online connection
- 15. FRBR Structure Group1 (WEMI): products of intellectual of artistic endeavor Work Expression Manifestation Item Group 2: entitles responsible for Group 1 production/creation Person Corporate Body Family Group 3: subjects for works (Group1) Concept Object Event Place
- 16. 16 Work Expression Manifestation Item is realized through isembodied in is exemplified by Inherent Group 1 Relationships FRBR Structure – Group 1
- 17. Original Work - Same Expression SameWork – New Expression New WorkCataloging Rules Cut-Off Point DerivativeEquivalent Descriptive Facsimile Reprint Exact Reproduction Copy Microform Reproduction Variations or Versions Translation Simultaneous “Publication” Edition Revision Slight Modification Expurgated Edition Illustrated Edition Abridged Edition Arrangement Summary Abstract Digest Change of Genre Adaptation Dramatization Novelization Screenplay Libretto Free Translation Same Style or Thematic Content Parody Imitation Review Criticism Annotated Edition Casebook Evaluation Commentary Family of Works
- 18. FRBR Structure -Relationships 18 Work Expression Manifestation Item is owned by is produced by is realized by is created by Person Corporate Body Family Relationships Between Groups 1 and 2
- 19. FRBR exercise Whatare the identifying elements of the: Work Expression Manifestation Item Relationship(s) Other Group 1 entities? Group 2 (person, family, corporate body)?
- 20. An important distinction FRBR conceptual model RDA/AACR2: content standard ISBD display format/standard MARC/MARC21 communication format other communication formats: ONIX, Dublin Core
- 21. RDA Toolkit Tabs RDA – text of RDA Tools RDA element set RDA mappings (MARC-RDA; MODS-RDA) RDA record examples Workflows – can be global (public) or local Maps – Metadata Application Profiles Entity Relationship Diagrams (FRBR, FRAD, etc.) Schemas – element sets Resources AACR2 LC-PCC PS (policy statements) Other (various links)
- 22. RDA Toolkit Updates “When there is a new release for RDA Toolkit, it is made on the second Tuesday of the month. Releases typically contain updates to content and metadata, enhancements to RDA Toolkit functionality, and fixes to existing bugs.” (RDA Toolkit blog) May 14, 2013 Next: July 9, 2013 Training RDA Toolkit Essentials - FREE
- 23. Authorities Based onattributes and relationships identified in FRAD Person Family Corporate body Place Authorized/variant access points and elements will for now continue to be documented in authority records
- 24. Authority records -vocabulary changes AACR2 RDA Heading Authorized access point See reference Variant access point See also reference Authorized access point for related entity
- 25. Authority records –new MARC fields 046 : associated dates (Work, Expression, Person, Family, Corporate Body) 336 : content type (Work, Expression, Person, Family, Corporate Body) 370 : associated place (Work, Expression, Person, Family, Corporate Body) 371 : address (Person, Family, Corporate Body) 372 : field of activity (Person, Family, Corporate Body) 373 : affiliation (Person, Family, Corporate Body) 374 : occupation (Person, Family, Corporate Body) 375 : gender (Person) 376 : family information (Family) 377 : associated language (Person, Family, Corporate Body entities)
- 26. Authority records –new MARC fields 380 : form of work (Work) 381 : other distinguishing characteristic of work or expression (Work, Expression) 368 : additional corporate body attributes 378 : fuller form of personal name 382 : medium of performance (Work) 383 : numeric designation of a musical work (Work) 384 : key (Work)
- 27. Key changes forAuthorities Authorized access point is based on *usage* or preferred name Date of birth/death are required (if known) Spell out born, died, approximately, use – (hyphen) for open dates Include titles or terms associated with surnames Such as Junior (Jr.), Senior, etc. Separate guidelines for royalty, nobility, religious persons
- 28. Key changes forAuthorities Families Fictitious persons and real non-human entities can now be authors Treatment of pseudonyms – separate identities If pseudonym is preferred and real name is not used, establish under pseudonym; otherwise establish each identity separately
- 29. Key changes forAuthorities Undifferentiated names – avoid creating Options: Dates Qualifiers Titles/designations Profession/field of activity And more! Conferences, Congresses, other events with dates Include frequency in the name Include number, date, and location
- 30. Key changes forAuthorities Uniform titles Language: Polyglot no longer used Separate authorized access points for each language of translation Works always present Selections. Works. Selections. Bible: removal of O.T. and N.T. Bible. O.T. Genesis Bible. Genesis. AND Bible. Old Testament. (for the whole) Koran Qur’an
- 31. RDA authority recordexample(s) Identification: 040 |e rda 008/10 (Rules) = z (other)
- 32. Bibliographic records RDAis fundamentally different in it's approach to describing materials/resources/things Focus on content *first* and carrier/format second RDA cultivates relationships “Guidelines and instructions” rather than rules Cataloger’s judgment – one size does not fit all MARC record contains a mix of Group 1 WEMI attributes as well as Group 2 and Group 3 entities.
- 33. Bib records –vocabulary changes AACR2 RDA Heading Authorized access point Author, composer, artist, etc. Creator Main entry Preferred title, and, if appropriate, authorized access point for the creator Uniform title Two RDA counterparts: 1. Preferred title + differentiating information 2. Conventional collective title like “works” Physical description Carrier description General material designator (GMD) Three elements: 1. Content type 2. Media type 3. Carrier type Chief source Preferred source(s)
- 34. Bib records –new MARC fields 336 – content type 337 – media type 338 – carrier type 344 – sound characteristics 345 – projection characteristics of moving image 346 – video characteristics 347 – digital file characteristics 264 – production, publication, distribution, manufacture, and copyright notice New subfields for relationships New subfields to parse 502 Dissertation information
- 35. Bib records -vocabularies Registered and controlled Vocabularies are included in the Open Metadata Registry http://metadataregistry.org/ The vocabulary lists for the content, media, and carrier types, as well as the relationship terms, are considered *closed* lists You MUST use a term from those lists There is a petition process to add new terms
- 36. Key changes: General Transcription – record what’s there! Source(s) Relationships for authorized access points *Required* for the creator Rule of three – gone! Be liberal in recording alternate titles Related works are no longer in a general note field, but rather traced so they can be linked (prefer linking fields 76x-78x (and some 70x-75x) to 5xx notes) GMD replaced by 336 (content type), 337 (media type), 338 (carrier type)
- 37. Key changes: General Spelling out of abbreviations p. pages ill. illustrations cm is not an abbreviation, it is a symbol, like © Latin terms no longer used [S.l. : s.n.] [Place of publication not identified] : [publisher not identified] [et al.] [and # others] [sic] 245 has title as appears on piece; 246 contains corrected form of title Adjacent bracketed elements are bracketed separately
- 38. Standard Records Theserecords are FLOOR records – add additional content as identified and needed they provide the essential elements to meet the FRBR User Needs BIBCO Standard Record (BSR) The BIBCO Standard Record (BSR) metadata application profile based on RDA includes elements applicable to archival materials, audio recordings, cartographic resources, electronic resources (if cataloged in the computer file format), graphic materials, moving images, notated music, rare materials, and textual monographs. The RDA BSR is arranged along a baseline for RDA elements. CONSER Standard Record (CSR) The CONSER RDA cataloging checklist and core elements document CONSER decisions reconciling AACR2 based CSR elements with RDA core elements for serials and serves as the primary source for CONSER RDA descriptive elements and practices.
- 39. RDA or AACR2? Hybrid records? What: A record that contains elements from more than one content standard Why: add things that will enhance and contribute to the user tasks What can I edit? You can safely add or edit any element that does NOT impact the transcription based descriptive fields When do I re-describe? When you need to edit the descriptive fields that are based on transcription (e.g. core elements)
- 40. Hybrid records Guidelinesavailable on LC website RDA records: http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelin es/Serial-RDA.doc Pre-RDA records: http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelin es/Hybrid-Guidelines-Serials-Post-Impl.docx Remember: Goal: enhancing the record to improve user access (user tasks: find, identify, select, and obtain) DO NO HARM: If it's not wrong, leave it alone Be nice: avoid editing just for style 40
- 41. RDA bib recordexample(s) Identification: 040 |e rda LDR/18 (Desc) = i (ISBD), c (ISBD not included), blank (non-ISBD)
- 42. PRACTICE Monographic printmaterials Pay particular attention to the 264 field dates and the 33x fields
- 43. Image created by: JenniferYoung Northwestern University
- 44. Day 2 Special Formatsand Linked Data
- 45. Key changes: Serials 300 field is core for currently published, tangible non-print formats Carrier type changes (338) RDA 3.1.6.1: Create a new description if there is a change in the carrier type of a serial to online resource from another computer carrier, or vice versa Transcription exceptions: Omit numbering from title proper or parallel title (use mark of omission wherever in title) Some alternatives allow some conversions and some omissions for some elements No more manifestation level differentiation [Reminder]: ISSN key title (222) is at manifestation level, NOT work or expression title, so key title and authorized access point for the work may not match 45
- 46. Key changes: Serials:new description 46
- 47. Key changes: Audio/Visualmaterials SOUND RECORDINGS 2.2.2.1 – Preferred source general guidelines When choosing a preferred source of information, treat as part of the resource itself: the storage medium (e.g., paper, tape, film); any housing that is an integral part of the resource (e.g., a cassette, a cartridge). When describing the resource as a whole using a comprehensive description, treat accompanying material as part of the resource itself. When preparing an analytical description of one or more components of a resource, treat accompanying material as a source outside the resource itself (i.e., as a related resource). Treat a container issued with the resource (e.g., a box in which a game or kit is issued, a clamshell box containing compact discs in individual jewel cases or cardboard sleeves) as part of the resource itself. Treat a container that is not issued with the resource (e.g., a box or case made by the owner) as a source outside the resource itself. Always give phonogram date RDA 3.16 – Sound characteristic
- 48. Key changes: Audio/Visualmaterials SOUND RECORDINGS – New MARC fields 344 – Sound characteristics 347 – Digital file characteristics 380 – Form of work 381 – Other distinguishing characteristic 382 – Medium of performance 383 – Numeric designation of musical work 384 – Key
- 49. Key changes: Audio/Visualmaterials VIDEO 2.2.2.3: Preferred source – Moving images 1st choice: use the title frame or frames, or title screen or screens, as the preferred source of information BUT, if the title frames or title screens only list the titles of the individual contents and another source forming part of the resource has a formally-presented collective title, use as the preferred source of information the first applicable source with a formally-presented collective title. RDA 3.16 – Sound characteristic RDA 3.18 – Video characteristic
- 50. Key changes: Audio/Visualmaterials VIDEO – New MARC fields 344 – Sound characteristics 346 – Video characteristics 347 – Digital file characteristics 380 – Form of work
- 51. PRACTICE Serials andAudio/Visual materials
- 52. Key changes: Online Integrating Resources 2.1.2.4 Basis for description: When preparing a comprehensive description for an integrating resource (e.g., an updating Web site), choose a source of information identifying the current iteration of the resource as a whole. If there is no source of information identifying the current iteration of the integrating resource as a whole, treat the sources of information identifying its individual contents as a collective source of information for the whole. Make a note identifying the latest iteration consulted in making the description (goes in a 588 field)
- 53. Key changes: Integrating:new description 53
- 54. Provider Neutral andRDA What? How is that possible? Identification: 040 |e rda |e pn The provider-neutral model (in contrast to RDA) specifies that if the e-resource being cataloged is an online reproduction of a tangible resource, usually the Production, Publication, Distribution, Manufacture and Copyright notice information will come from the original tangible source record 588 field – source of description is REQUIRED
- 55. PRACTICE Online materials Integrating resource Provider Neutral Book or serial – your choice
- 56.
- 57.
- 58.
- 59.
- 60. What’s next? BIBFRAME Linked Data and the Semantic Web Tools Bibframe.org RIMMF – RDA in Many Metadata Formats VTLS Sandbox (subscription) – “FRBRize” records Linkeddata.org Schema.org
- 61.
- 62. Image created by: JenniferYoung Northwestern University
Editor's Notes
- #3 Introduce yourself. Recommend including committee/task force work, general cataloging background/experience, any other teaching/workshop experience, RDA experience/involvementGroup intros: name, library, RDA experience, and: “If you could be any vegetable, what would you be and why?”
- #6 Multiple sets – different communities had their own sets – Law, serials, medical, etc.1940s the ALA cataloging rules emerged as more primary, but various rules had existed for many years (Cutter’s dictionary arrangement, etc.)AACR – North America and UK couldn’t agree on certain approaches (corporate bodies – US entered some under place instead of under the name itself)Resulted in the famous AACR2 migration and de-superimposition of headingsMARC flavors: UKMARC, USMARC, MARC21, MARCXML, etc.
- #7 AACR2 – based on cards; limited by that 3x5 environment (ex: rule of 3, abbreviations) – cards are expensive, data is cheap also limited to print world have to “shoehorn” non-print formats into MARC and AACR2 structure intertwined with MARC and ISBD tied to bibliographic *library* world – data in a siloRDA – designed for the web and online, looks to future of web interactions open our data up to be used and transferred and connected toRead RDA Toolkit 0.0 Purpose and Scope and 0.1 Key Features
- #9 Used during RDA development and testing for evaluation and guidance on future development/changes
- #10 ICP meetings outcome: IFLA Statement of International Cataloguing Principles (published Feb. 2009): http://www.ifla.org/publications/statement-of-international-cataloguing-principlesRDA tasks from U.S. Test Coordinating Committee: http://www.loc.gov/bibliographic-future/rda/source/rda-execsummary-public-13june11.pdfRe-writing RDA in clear, unambiguous, plain English ; RDA Toolkit improvement ; RDA updating process ; full set of examples ; BIBFRAME development ; training plan ; documentation/toolsRDA: for awhile jokingly called “Recently Delayed Again” due to delays in drafts, reviews, publishing, etc.
- #11 RDA testWho: national libraries other institutionsOther groups also participated informally, submitting their records to be analyzed with the formal test created records, such as the ALCTS Continuing Resources Section Cataloging Committee, other groups for specialized formats (OLAC for audio-visual, etc.)
- #12 What is the economic impact?What is the impact on library operations?What are the direct costs?What are the training impact and costs?
- #13 There are four possible outcomes: Do not implement RDA Postpone implementation until certain changes are made Implement RDA Implement RDA with specific recommended changes or policy decisions for US libraries
- #15 Exemplifies why we do what we do – end goal: we make stuff findable!
- #16 Group 1 – products of intellectual of artistic endeavorGroup 2 – entitles responsible for Group 1 production/creationGroup 3 – serve as subjects for the workThese groups correspond to the user tasks: Find – work/expression – what I want – matches my search Identify – work/expression – this version of the work (recording, text, etc.) Select – manifestation – this is the format/language I want/need Obtain – item – how to I get it?Example? (suggestion from group)
- #20 Don Quixote – book ; video/DVD ; play ; English translationUse a white board and ask the group to identify how many works, expressions, manifestations, and items there are (circle using different colors to differentiate):Group 1: Print book (2 copies), ebook HTML, ebookePub, ebook Overdrive, ebook Kindle, audio book on CD, audio book on MP3, English translation in print, 2nd edition of the book, abridged version of the book [2 works (original print, 2nd ed.); 3 expressions (original, translation, abridged); 10 manifestations (4 print, 4 ebook, 2 audio); 11 items]Group 2: ask for an example from group
- #21 Communication format: just the “container” to hold the content of the description; a “wrapper” for the dataISBD tells us how to display that contentRDA/AACR2 tells us how to identify and enter the contentFRBR conceptual model tells us how to structure the content and what content needs to be includedExample: creator =/= 1xx field; creator can be entered any authorized access point e.g. the creator of the resource you are describing may have a creator role such as editor
- #22 Primary tool for using/accessing text and content of RDA
- #23 Updates content and metadata: updates both major and “fast track” changes and corrections May 14 – all reworded chapters are now released/publishedRDA Toolkit Essentials – archives available on RDA Toolkit Teaching and Training page; new sessions held regularly
- #24 RDA 0.3.3 – Alignment with FRADNow called authorized access points
- #26 MARC documentationSome are for Group 1 and Group 2, some only apply to Group 2 entities
- #28 READ the LC documentation on changes to the authority file both for names and subjects sent out over various lists also posted on PCC website
- #29 Families – subject and name authorities – separate records, one in each file; can’t use a family in the name authority file as a subject and vice versaExamples – as class Miss Piggy Kermit Millie the dog Socks the cat
- #30 Many more options to qualify a name to differentiate itAuthority – whole *identity* of a person; not just the heading itselfConferences, congresses, etc. separate records for each individual conference also a record for the “generic” version for use with serials/multi-part if needed
- #32 Printouts of RDA Authority records personal names corporate bodiesPull up sample record in OCLCOrder of fields in 040: |a |b |e |e |c |d |d
- #33 Essentially “flipping AACR2 on it’s head” in terms of approachRDA starts with the content, describing the elements of the WORK first, then the EXPRESSION and MANIFESTATIONAACR2 is organized by format (carrier) – the tangible comes firstI largely work with web resources. So I have online books. Online videos. Online videos that are issued as serials. All of these things require me to review and cross reference and flip back and forth like an insane woman in AACR2 from chapter to chapter. The first and second examples both require using 2 chapters. The third example requires I use THREE distinct chapters in AACR2 to fully describe the thing I'm looking at since the format determines how the thing is described. This is not efficient.But core goal of making things findable (uniquely identifiable) is still the same
- #35 MARC documentation
- #36 Registered – what does that mean? – in the metadata registry for the webControlled: *Closed* lists for content, media, and carrier types *Closed* lists for relationship terms can petition to add new terms as identified
- #37 Transcription – appearance on the piece is important in RDA; record what you see (capitalization is an appendix!) use for titles, statements of responsibility in their entirety, place and publisher, etc. abbreviate ONLY if found on the source itselfSource – the resource itself, including accompanying material, container, storage, presentation, etc. if taking information from something outside the resource itself or supplying data, enclose data in square brackets
- #39 USE these; they offer a nice summary of the core RDA elements and map to the appropriate MARC fieldsThese records are FLOOR records, as in you can add and build on them; they provide the essential elements to meet the FRBR User Needs
- #40 What is a hybrid record? A record that contains elements from more than one content standard e.g. AARC2 record with 33x fields or relationship terms can safely add as many elements as you desire that don’t impact the transcription based descriptive fields – those form the “bibliographic integrity” of the record e.g. add notes, change the authorized access points, add authorized access points, but don’t edit the publisher or title informationWhen do you re-describe? When you need to edit the descriptive fields that are based on transcription (generally the “core” elements of a record)Why hybrid records? goal is to support access – add things that will enhance and contribute to the user tasksOn PCC website: http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Post-RDA-Implementation-Guidelines.html
- #41 Come to the cult of the hybrid record; we have cookies
- #42 Circulate sample recordsPull up examples on OCLC and walk through fields ; “What do you see that’s different?” printed monograph: 838124078 ; 842392618 (240 field) ; 811004727 ; 826382429 (multipart mono); 842256261 (130 field) serial: 830844725 ; 833139957 (130 field)Order of fields in 040: |a |b |e |e |c |d |d
- #43 264 field dates: publication date is the required element; if no publication date is present, you may infer the publication date from the copyright date, but MUST enclose it in square bracketsrecommendation: if there is no publication date and you are inferring the date, also include the 264 _4 field with the copyright date33x fields: only the TERM is required; you must include the |a and the |2; the |b (code) is optional
- #46 Manifestation level: e.g. (Online) in 130/240Differentiation is at work and expression levelSo same work but different carriers = same preferred title
- #47 Some manifestation changes do require a new description (e.g. new record) but NOT a new preferred title1.6.2.1: M1.6.2.2: M1.6.2.3: W – new preferred title1.6.2.4: W – new preferred title1.6.2.5: M
- #49 The 344, 347, and 380 are used for ALL sound recordings381-384 are particular to MUSIC
- #50 You can use the container! Without having to use square brackets; the container, disc label, etc. can be used for description
- #53 Key question: pay attention to granularity – what part of the website are you describing? Ensure that ALL elements, especially transcription, come from the same part you are describing
- #54 Some manifestation changes do require a new description (e.g. new record) but NOT a new preferred title1.6.3.1: M1.6.3.2: M1.6.3.3: M orW – new preferred title1.6.3.4: W – new preferredtitle
- #55 Provider neutral is a “defined approved set of exceptions to RDA”
- #56 Make sure you include the 300 field AND the 588 field(s)
- #57 OCLC #811140443AACR2, added 33x fields
- #58 OCLC #822230423RDA – early test record so has additional RDA fields (testers often applied every applicable option to fully test all possibilities/options in RDA)Repeating 33x fields
- #59 OCLC# 50469952HYBRID 260, use of brackets careful with 222 – ISSN still qualifies by manifestation
- #60 #823260252HYBRIDLook at 130 – qualified by manifestation, not expressionUniform titles are only at the *expression* level
- #61 BIBFRAME?Linked Data/semantic web? – based on relationshipsLinked open data: http://lod-cloud.net/ - focus on upper right quadrant – lots of libraries/library related groups participatingMetadata map: http://www.dlib.indiana.edu/~jenlrile/metadatamap/Tools: Handout of resources links books