The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

11
The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

Transcript of The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

Page 1: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

The “Elephant” in the Room: How Will My Library System Vendor

Handle RDA?

Page 2: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

The Promise and Challenge of RDA

Descriptive precision

Data consistencybut…

Systems evolved with AACR2

Libraries need RDA training and conversion

Change is difficult

www.theskyriver.com

Page 3: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

A Cataloging Utility’s Perspective

Millions of legacy records

Customers at all stages of RDA readiness

RDA and the existing cataloging user interface

www.theskyriver.com

Page 4: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

Above All…

…OFFER CHOICE…

www.theskyriver.com

Page 5: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

Design Elements

Extension of ‘Best Record’ policy- Both AACR2 and RDA data elements stored within a single

bibliographic entity; logins set according to the library’s record export and display preferences

RDA and the User interface- 33X templates with drop-down menus of standard RDA

terms; inputting of RDA data elements thus very easy- In-context links to the RDA Toolkit

www.theskyriver.com

Page 6: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

245 subfield h (Medium) will be displayed

RDA fields 336, 337 and 338 will be suppressed

Abbreviated form of the 250 (Edition), 260 (Imprint), and 300 (Description) fields will display

Non-RDA Display

Page 7: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

040 subfield e will be coded as rda to indicate the Description Convention

Unabbreviated form of the 250 (Edition), 260 (Imprint), and 300 (Description) fields will display

RDA fields 336, 337 and 338 will appear

245 subfield h (Medium) will be suppressed

RDA Display

Page 8: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

RDA fields 336, 337 and 338 will appear

040 subfield e will be coded as rda to indicate the Description Convention

245 subfield h (Medium) will be displayed

unabbreviated form of the 250 (Edition), 260 (Imprint), and 300 (Description) fields will display

Hybrid Display

Page 9: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

Implications

Libraries may adopt RDA incrementally

Library systems can incorporate RDA data even if AACR2 data needed

Minimal disruption for library staff

www.theskyriver.com

Page 10: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

Costs

A non-issue for SkyRiver subscribers

RDA development/enhancement is part of the cost of doing business

Unlimited data use, whether RDA or not

www.theskyriver.com

Page 11: The “Elephant” in the Room: How Will My Library System Vendor Handle RDA?

For More Information

Drop by Booth #1722

Write to [email protected]

www.theskyriver.com