Authority data for objects currently described as Corporate bodies

Slides:



Advertisements
Similar presentations
Resource description and access for the digital world Gordon Dunsire Centre for Digital Library Research University of Strathclyde Scotland.
Advertisements

Future of Cataloging RDA and other innovations Pt. 2.
Future of Cataloging RDA and other innovations pt.1a.
RDA Test “Train the Trainer” Module 6: Identifying Families [Content as of Mar. 31, 2010]
RDA & Serials. RDA Toolkit CONSER RDA Cataloging Checklist for Textual Serials (DRAFT) CONSER RDA Core Elements Where’s that Tool? CONSER RDA Cataloging.
Module B: Identifying works User task = identify.
RDA: A New Standard Supporting Resource Discovery Presentation given at the CLA conference session The Future of Resource Discovery: Promoting Resource.
LC Training for RDA: Resource Description & Access Module 6: Authorities II Part 1: Identifying Families Cooperative and Instructional Programs Division.
Teaching RDA Train-the-trainer course for RDA: Resource Description and Access Presented by the National Library of Australia September – November 2012.
University of Adelaide Library Life Impact The University of Adelaide The well connected catalogue Patricia Scott, Denise Tobin and Helen Attar.
LC Training for RDA: Resource Description & Access
RIMMF, or, Cataloguing without MARC Céline Carty, University of Cambridge Linked Data: what cataloguers need to know #cigld CIG Event, 25 November 2013.
RDA, FRBR & MARC RDA Cataloguing Seminars September 2012.
RDA AND AUTHORITY CONTROL Name: Hester Marais Job Title: Authority Describer Tel: Your institution's logo.
RDA Test “Train the Trainer” Module 7: Identifying Corporate Bodies [Content as of Mar. 31, 2010]
Module C: Identifying expressions User task: identify.
7: Basics of RDA Relationships for Serials Relationships in RDA Relationship designators Creators and other corporate bodies related to works Corporate.
LC Training for RDA: Resource Description & Access Module 6: Authorities II Part 4: FRBR Group One and NARs Cooperative and Instructional Programs Division.
The European Manuscript & Hand Press Book Heritage The role of the Consortium of European Research Libraries (CERL) Manuscript Collection in the National.
FRAD: Functional Requirements for Authority Data.
Linking resources Praha, June 2001 Ole Husby, BIBSYS
Jenn Riley Metadata Librarian IU Digital Library Program New Developments in Cataloging.
Module 8 Series in AACR2 and RDA: What’s the same? What’s different?
DACS Describing Archives: A Content Standard. The Background  Archives, Personal Papers & Manuscripts, 1980s –New Technologies with Web, XML, EAD –Revision.
From AACR2 to RDA: An Evolution Kathy Glennan University of Maryland.
RDA: Resource Description and Access A New Cataloging Standard for a Digital Future Jennifer Bowen RDA Forum ALA Annual Meeting, New Orleans, June 24,
RDA in NACO Module 6.a RDA Chapter 11: Identifying Corporate Bodies—Overview Recording the Attributes.
RDA Toolkit is an integrated, browser-based, online product that allow user to interact with a collection of cataloging-related documents and resources.
The Future of Cataloging Codes and Systems: IME ICC, FRBR, and RDA by Dr. Barbara B. Tillett Chief, Cataloging Policy & Support Office Library of Congress.
1 herbert van de sompel CS 502 Computing Methods for Digital Libraries Cornell University – Computer Science Herbert Van de Sompel
1 Making Changes to Personal Name and Corporate Body Authority Records Module 7. Making Changes to Existing Name and Work/Expression Authority Records.
RDA in NACO Module 4.a Module 4.b Module 4.c RDA Chapter 9: Identifying Persons— Overview Recording the Attributes.
 Why do we catalog?  Why do we classify?  What aspects are important?  What aspects can we let go of?
RDA Update MARC Change Summary Sally McCallum RDA Update Forum June 23, 2012 Library of Congress.
Evidence from Metadata INST 734 Doug Oard Module 8.
Module 9: Attributes of [concept, object, event], place (RDA Section 4) Adapted from: Teaching RDA: Train-the-trainer course RDA: Resource description.
RDA Compared with AACR2 Presentation given at the ALA conference program session Look Before You Leap: taking RDA for a test-drive July 11, 2009 by Tom.
RDA, the Next Phase Joy Anhalt Marjorie Bloss Richard Stewart.
RDA DAY 1 – part 2 web version 1. 2 When you catalog a “book” in hand: You are working with a FRBR Group 1 Item The bibliographic record you create will.
Building blocks for RDA Theory behind RDA ALLUNY Annual Meeting September 28-30, 2012.
RDA in NACO Module 3 RDA Toolkit and where you find the instructions you need: Name entities and attributes.
Functional Requirements for Bibliographic Records The Changing Face of Cataloging William E. Moen Texas Center for Digital Knowledge School of Library.
LC Training for RDA: Resource Description & Access Module 5: Authorities I Part 4: RDA Toolkit Cooperative and Instructional Programs Division Library.
Future of Cataloguing: how RDA positions us for the future for RDA Workshop June, 2010.
RDA: a new cataloging standard for a digital future RDA Update Forum ALA Midwinter Meeting Philadelphia, PA January 13, 2008 John Attig ALA Representative.
Teaching RDA Train-the-trainer course for RDA: Resource Description and Access Presented by the National Library of Australia September – November 2012.
Sally McCallum Library of Congress
The British Library Guide to RDA Name Authority Records © The British Library Board 2014.
Current initiatives in developing library linked data Gordon Dunsire Presented at the Cataloguing and Indexing Group Scotland seminar “Linked data and.
The world’s libraries. Connected. RDA & OCLC Glenn Patton Director, WorldCat Quality Management.
Some basic concepts Week 1 Lecture notes INF 384C: Organizing Information Spring 2016 Karen Wickett UT School of Information.
Information organization Week 2 Lecture notes INF 380E: Perspectives on Information Spring 2015 Karen Wickett UT School of Information.
Information organization Week 2 Lecture notes INF 380E: Perspectives on Information Spring 2015 Karen Wickett UT School of Information.
What is it that cataloguers and librarians fear the most?
LRM-RDA Gordon Dunsire
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Metadata Standards - Types
Authority Control and Alma: A look at change from many Angles
IFLA FRBR-Library Reference Model and RDA
Metadata standards Guidelines, data structures, and file formats to facilitate reliability and quality of description INF 384 C, Spring 2009.
Getting started With Linked Data.
FRAD: Functional Requirements for Authority Data
Attributes and Values Describing Entities.
MARC: Beyond the Basics 11/24/2018 (C) 2006, Tom Kaun.
RDA Terminology Changes -and- Record Display Comparisons
From Big Bang to beta An overview of the 3R Project
Introducing IFLA-LRM Gordon Dunsire, Chair, RSC
RDA Community and linked data
The new RDA: resource description in libraries and beyond
FRBR and FRAD as Implemented in RDA
Presentation transcript:

Authority data for objects currently described as Corporate bodies The essence of the problem is that Authority data creators are quite often faced with cases when they have to identify and describe entities, such as named historical buildings (palaces, churches, manor houses, specific architectural and historical buildings) as well as man-made things such as named movable objects. Data creators have to analize what type of entity is represented. They understand that there are different entities and in this case different authority records need to be created. In accordance with RDA and IFLA LRM entity model entity class for such kind of immovable objects is Place. In this case more information and clarifications are required. Some considerations on the subject. Maira Kreislere, National Library of Latvia EURIG meeting, Budapest, May 2-3

Long-standing contradiction (AACR2 ; RDA) Current practice – Corporate body (MARC AUTH 110) Entity class – Place Future practice – Geographic name (MARC AUTH field 151) Authority data for such kind of objects are still created as institutions, with the possibility to identify them only as Corporate body. In this case, users who seek information about a particular object are misled. No clearly defined differences between Corporate body (active agent) and Named Object causes problems in entity identification and data linking, especially in metadata creating for digital and visual resources. At present, there is a tendency to create Authority records for churches, palaces and other Named Objects (buildings) as Geographic Names (MARC21 Authority field 151). These objects are more related to geographic names and have attributes as geographic objects connected with place. We would support such solution.

Building of National Library of Latvia Coordinates –56°56′28″N 24°5′48″E Address – Mūkusalas iela 3, Rīga Related agent person – Architect: Birkerts, Gunars, 1925-2017 Related place – Rīga, Latvia Date of construction – 2014 Related term – Library buildings, Latvia Related institution – National Library of Latvia Other forms of name Latvijas Nacionālās bibliotēkas ēka National Library of Latvia building Gaismas pils (Latvijas Nacionālā bibliotēka) Stikla kalns (Latvijas Nacionālā bibliotēka) Castle of Light (Latvijas Nacionālā bibliotēka) Glass mountain (Latvijas Nacionālā bibliotēka) National Library of Latvia has collection of printed resources and digitized visual resources that reflects historical buildings and other objects in Latvia. For example, Corporate body “National Library of Latvia” is not the same as Object – “Building of National Library of Latvia”. They both have different attributes and should be linked as separate entities. Attributes and relationships, which should appear in the Authority record for entity Object: Type of entity – Building - MARC21 Authority Field 075; Date of construction/reconstruction; end date, if object does not exist anymore - MARC21 Authority Field 046 subfield $s; It will be nice to have a possibility to add dates to any variant name of Object, so these objects can be called differently in different periods of time. Related Agents – architect, designer, painter, owner, institution - MARC21 Authority Fields 5XX; Address - MARC21 Authority Field 371; Coordinates - MARC21 Authority Field 034; Other related subjects: architectural style, historical events -MARC21 Authority Field 550. Type of entity – Building

Royal Palace and the National Library of Hungary There is an example for Place entity Royal Palace in Budapest which is house of Corporate body National Library of Hungary. Authority data from Wikidata are placed as Geographic name. Royal Palace and the National Library of Hungary

Future practice for named vehicles and man-made objects ? Work ? (130 Uniform Title) Titanic (steamship) There is even one more controversial type of entity – vehicles like ships, space ships, etc. They are also described as Corporate bodies, but they are mentioned only as subjects never as active agents. They have owners, builders, designers, technical characteristics; they change their names. There is a need to find a solution for this kind of entity in MARC and RDA. In order to have a place for keeping links to world wide known named objects described in other memory institutions, library systems must have an appropriate place in entity model. For example there is a Work Leonardo, da Vinci, 1452-1519. Mona Lisa which is man-made object. So, maybe steamship Titanic or diamond Koh-i-Noor are also Works in this meaning? No need for new entities, no need for new MARC fields. These unique objects are somehow creative works and I think it is possible to describe them in Work level. Koh-i-Noor (diamond)