1. RDA: thinking globally, acting
globally
Gordon Dunsire
Presented at International Developments in Library
Linked Data: Think Globally, Act Globally – Part Two: an
ALCTS Program,
ALA Annual, Las Vegas, USA, 28 Jun 2014
2. Overview
Failure of top-down approach
RDA tools
Case: intended audience
Mapping the focus of description
Top-down, bottom-up issues
8. Top-down
Examine local schema
Identify the common elements
Create a common/global element set (RDF)
Refine the global element set to connect down (map)
to specific local elements
Issues
Common elements may not cover the same space as local
elements
Refinement not possible
Common elements have to be augmented
Favours the global over the local
Encourages a good-enough approach
9. Bottom-up
Publish the local schema(s) in RDF
Map local elements from different schema to
lowest common (dumber) elements – add new
elements if necessary
Continue until all local schema have been
mapped
Issues
Multiplicity of RDF element sets
Frequent overlap and redundancy
Local management resources
The relationships between entities from different data models that focus on essentially the same thing, a bibliographic resource, are not straightforward.
* RDA provides relationship properties for the WEMI/IMEW stack – only the direction of the cardinality constraints is shown for clarity.
* The ISBD and FRBR Review Groups have agreed to provide properties to relate the single ISBD entity Resource with the FRBR WEMI entities. These were added to the ISBD namespace with “New-proposed” status in 2013.
* BIBFRAME provides relationship properties to link BIBFRAME Work and Instance entities.
* BIBFRAME also provides a property to “connect Works under FRBR/RDA rules”; that is, to link two BIBFRAME works.
* Where does MARC 21 fit in? Can we assume that the domain of MARC is a single entity similar to, if not the same as, ISBD’s Resource? That is certainly the case with UNIMARC. What are the relationships between the BIBFRAME entities and Resource?
* What should the relationships between BIBFRAME and RDA entities look like? It seems only necessary to related a BIBFRAME Work to an RDA Expression, because the constraint locks it to a single RDA Work. That is, a BIBFRAME Work is directly related to RDA Expression, not an RDA Work.