RDA Resource Management: Insights on Metadata and Descriptions in Knowledge Management
This commentary explores the concept of "resources" within RDA, discussing how diverse items such as books, events, and persons are categorized and described. It emphasizes the importance of the one-to-one DC principle, advocating for clear and effective data models to enhance metadata creation. The text questions traditional notions of metadata, considering different user perspectives, including librarians and content producers. It argues that monolithic specifications are insufficient, proposing application profiles as a flexible solution to better serve various domains and users.
RDA Resource Management: Insights on Metadata and Descriptions in Knowledge Management
E N D
Presentation Transcript
Mikael Nilsson mini@nada.kth.se The Knowledge Management Research Group Royal Institute of Technology, Stockholm http://kmr.nada.kth.se Comments on RDA
“Resource” • What's a resource? • Book, person, publisher, Location, Event, etc, etc, etc • Most current formats clump many together • The DC one-to-one principle • One resource, one description • Needs a good data model
“Description” • Describing • “assisting those who create metadata” • Descriptions • What do we think metadata is? • Objective? • Produced once? • Contained? • Just labeled text? • index?
“access” • Who's accessing? • Librarians, users, software? • Who's RDA for? • Librarians? • Implementers? • Content producers? (Teachers, students, etc)
One spec? • Monolithic specs in this field doomed to failure • Take too long to produce • Won't take into account important needs of domains • Application profiles a good idea • Needs framework to be “specializable”