1 / 14

“Subject” entities and relationships in RDA

“Subject” entities and relationships in RDA. Committee on Cataloging: Description and Access and Subject Analysis Committee John Attig ALA Representative to the JSC jxa16@psu.edu. “Subjects” in RDA. Why are there “empty” chapters in RDA?

hila
Télécharger la présentation

“Subject” entities and relationships in RDA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. “Subject” entities and relationships in RDA Committee on Cataloging: Description and Access and Subject Analysis Committee John AttigALA Representative to the JSC jxa16@psu.edu

  2. “Subjects” in RDA • Why are there “empty” chapters in RDA? • These chapters covered topics“out of scope” for AACR2 • Need to be written from scratch • Absence does not compromise RDA as a replacement for AACR2

  3. “Subjects” in RDA • Why include these chapters in RDA? • “Subject” entities and relationships are part of the Functional Requirements models • Distinction between “descriptive” and “subject” cataloging is arbitrary • Opportunity to bring both under the same framework

  4. “Subject” entities WORK WORK CONCEPT PERSON OBJECT EXPRESSION FAMILY has as subject EVENT MANIFESTATION CORPORATEBODY PLACE ITEM

  5. “Subject” entities and attributes • RDA Section 4: FRBR Group 3 Chapter 12: General Guidelines Chapter 13: Identifying Concepts Chapter 14: Identifying Objects Chapter 15: Identifying Events Chapter 16: Identifying Places

  6. “Subject” relationships WORK WORK CONCEPT PERSON OBJECT EXPRESSION FAMILY has as subject EVENT MANIFESTATION CORPORATEBODY PLACE ITEM

  7. “Subject” relationships • RDA Section 7: Relationships to Group 3 entities Chapter 23: General Guidelines • Recording subject relationships: Subject analysis

  8. “Subject” relationships • RDA Section 10: Relationships between Group 3 entities Chapter 33: General Guidelines Chapter 34: Related Concepts Chapter 35: Related Objects Chapter 36: Related Events Chapter 37: Related Places • Appendix L: Relationship Designators

  9. “Subjects” in RDA • What will these chapters contain?For the “attributes” chapters: • Definitions of each entity • Definitions of each attribute • Instructions on recording the attributes • Instructions on constructing authorized and variant access points

  10. “Subjects” in RDA • What will not be there? • Specific instructions for recording attributes or for formulating authorized access points • RDA must support any applicable subject heading vocabulary or classification scheme • “Rules” for recording the names of each entity are those of the standard — not RDA

  11. “Subjects” in RDA • For relationships: • Must support all applicable standards, each of which has its own “rules” • Some generally applicable relationships • Broader/Narrower/Related terms • Some basic ways of recording relationships • Identifiers • Authorized access points

  12. Complications • Group 1 & 2 entities can also have a subject relationship • Changes to those instructions • Some Group 3 entities are used in “descriptive” access points • Places • Events

  13. Complications • Single “has as subject” relationship • “Subject” defined flexibly in FRSAD • Might or might not include genre/form • BUT… • Single relationship between subject and WORK entities

  14. Complications • Each of the three Functional Requirements models has a slightly different view of the “subject” entities • FRBR: four entities, each with only one attribute: TERM or Name • FRSAD: one topic entity: THEMAseparate name entity: NOMEN • FRAD: FRBR topical entities, NAME, ACCESS POINT all defined as entities

More Related