Subject entities and relationships in RDA

Report
“Subject” entities and
relationships in RDA
Committee on Cataloging:
Description and Access
and
Subject Analysis Committee
John Attig
ALA Representative to the JSC
[email protected]
“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
“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
“Subject” entities
WORK
WORK
PERSON
OBJECT
EXPRESSION
has as subject
CONCEPT
FAMILY
EVENT
MANIFESTATION
ITEM
CORPORATE
BODY
PLACE
“Subject” entities
and attributes
 RDA Section 4: FRBR Group 3
Chapter
Chapter
Chapter
Chapter
Chapter
12:
13:
14:
15:
16:
General Guidelines
Identifying Concepts
Identifying Objects
Identifying Events
Identifying Places
“Subject”
relationships
WORK
WORK
PERSON
OBJECT
EXPRESSION
has as subject
CONCEPT
FAMILY
EVENT
MANIFESTATION
ITEM
CORPORATE
BODY
PLACE
“Subject”
relationships
 RDA Section 7: Relationships to
Group 3 entities
Chapter 23: General Guidelines
 Recording subject relationships:
Subject analysis
“Subject”
relationships
 RDA Section 10: Relationships
between Group 3 entities
Chapter
Chapter
Chapter
Chapter
Chapter
33:
34:
35:
36:
37:
General Guidelines
Related Concepts
Related Objects
Related Events
Related Places
 Appendix L: Relationship Designators
“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
“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
“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
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
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
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: THEMA
separate name entity: NOMEN
 FRAD: FRBR topical entities, NAME,
ACCESS POINT all defined as entities

similar documents