RDA Checkpoint - Where we are and where we're heading

RDA Checkpoint -- Where We Are and Where We're Heading

Presented by

Troy LinkerPublisher, ALA Digital Reference

American Library Association

Poll Questions

During the webinar you will have the chance to participate in several poll questions.

You should see a poll question appear on the right near the chat box.

The poll will be active for five minutes. The presentation will move on, but you will have

access to the live results as they come in.

Poll Question #1

How many people are watching the webinar at your location?

Session Agenda

• U.S. RDA Test Announcement• Virtual User Group• Recent RDA Toolkit Enhancements• Getting Access to RDA Toolkit• Questions

U. S. RDA Test Announcement

• Reports• Overall recommendations• Specific recommendations to ALA Publishing

regarding RDA Toolkit

U.S. RDA Test Reports

• Statement from the Executives of the Three National Libraries -- released June 13, 2011

• Executive Summary of the Report and Recommendations of Committee -- released June 13, 2011

• Full report -- released June 20, 2011• http://www.loc.gov/bibliographic-future/rda/

Overall Recommendations

Test Committee made nine recommendations to the following groups: – LC / NAL / NLM– Joint Steering Committee for Development of RDA

(JSC)– ALA Publishing (Co-Publishers)– Cataloging Community (including PCC)– Vendor Community

1. Rewrite the RDA instructions in clear, unambiguous, plain English. • Work with JSC to prioritize which chapters

should be addressed and completed first. Prioritization should be based on comments gleaned during the U.S. RDA Test as identified by the U.S. RDA Test Coordinating Committee.

• Identify and engage, in collaboration with JSC and the Committee of Principals, a writer to undertake rewrites.• Rewrite chapters identified as priorities.• Confirm readability of initial chapter

rewrites.• Timeframe for completion: within 18

months.

2. Define process for updating RDA in the online environment. • Timeframe for completion: within three

months.

3. Improve functionality of the RDA Toolkit. • Forward to ALA Publishing enhancements

needed as gleaned during the U.S. RDA Test and work with ALA Publishing on a timeline for changes.

• Working with ALA Publishing, identify a process for ongoing usability testing of RDA Toolkit enhancements.

• Timeframe for completion: within three months.

4. Develop full RDA record examples in MARC and other encoding schemas. • Work with ALA Publishing to integrate

examples into the RDA Toolkit. • Include examples for special communities

(e.g., serials, rare books, music). • Timeframe for completion: within six

months.

5. Announce completion of the Registered RDA Element Sets and Vocabularies. Ensure the registry is well described and in synchronization with RDA rules. • Timeframe for completion: within six

months.

6. Demonstrate credible progress towards a replacement for MARC. • Announce planning statement. (Done; see

Appendix M.)• Identify the stakeholders, key players and

experts needed.

• Identify tasks and timeline for development.

• Ensure development is underway.• Timeframe for completion: within 18 24 ‐

months.

7. Ensure and facilitate community involvement. • Prioritize needed updates to practices,

decisions, and documentation.• Prioritize and submit changes to JSC for

RDA content.

• Determine community involvement in the process, e.g., the role of Program for Cooperative Cataloging (PCC), OCLC, special interest communities, etc.

• Determine best method(s) to share decisions with community.

• Timeframe for completion: within 12 months.

8. Lead and coordinate RDA training. • Prioritize training focus and schedule led by

LC.• Engage PCC, Association for Library

Collections and Technical Services (ALCTS), and other bodies.

9. Solicit demonstrations of prototype input and discovery systems that use the RDA element set (including relationships). • Identify groups/organizations/vendors that

could provide models. • Determine availability of funding to support

prototype efforts. • Engage and produce initial prototypes.

• Utilize demonstrations in education and training efforts about the library community’s new metadata infrastructure.

Recommendations to ALA Publishing

Full report details four recommendations to ALA Publishing regarding RDA Toolkit.

1. Enhance and further develop the functionality of RDA Toolkit.– Workflows– Search– Performance

Workflows

• Develop an interactive wizard to assist with the creation of workflows.

• Allow for users/institutions to suppress certain workflows even if made public by the creators (e.g., only show PCC workflows).

• Allow for workflows and other tools to be open simultaneously through the use of separate windows.

Workflows

Search

• Allow for use of wildcards in searching.• Allow for searching of resources in the Tools

section. • Arrange the search results by RDA number.

Search

• Normalize search terms and results. • Resolve the problem that the existing search

labeled as “Core” retrieves instructions beyond “Core” and “Core Plus” elements.

Search

• Normalize search terms and results. • Resolve the problem that the existing search

labeled as “Core” retrieves instructions beyond “Core” and “Core Plus” elements.

RDA Toolkit Performance

• Further improve the table of contents features.• Refine/enhance the local annotations and

bookmark features to allow for updating and sharing.

• Increase the time allowed before the system times out; leave users on their current page after timing out rather than returning to the introductory screen.

• Improve response time possibly by not loading entire chapters each time a link is selected.

• Resolve connectivity issues related to institutional firewalls and network security.

Loading Full Chapters

• Loading entire chapter was requested by users during focus groups; they wanted more context in an online environment.

• Users didn’t like the way AACR2 displayed in small sections 1.1, 1.2, 1.3, etc.

• Unfortunately the size and complexity of many of the full chapters caused slow loading speeds.

Paging Chapters

• We are testing a solution that breaks each chapter into chapter pages, at the X.X level but not every X.X level.

• Each chapter will be broken into manageable sections based on the size of the particular chapter page.

• For example Chapter 1 is broken into two pages 1.1 – 1.6 on page one and 1.7 – 1.11 on page two.

• Improve response time possibly by not loading entire chapters each time a link is selected.

• Resolve connectivity issues related to institutional firewalls and network security.

2. Work with JSC to add additional features to RDA Toolkit.

Additional Content & Features

• Develop a single search for only “Core” and “Core if” elements.

• Integrate full examples into RDA Toolkit, including examples for special communities (e.g., serials, rare books, music resources).

• Provide mapping of RDA elements to other metadata schemes, e.g., MODS, MADS, METS, Dublin Core.

3. Develop mechanism for updating the text of RDA in a timely manner including notification to users as to which chapters/rules have been updated.• Include a mechanism for updating the

print version.

4. Publicize and continue to develop free training on various aspects of RDA Toolkit that were underutilized during the test including RDA: Element Set View and show/hide examples.

Session Agenda

Virtual User Group

The U.S. Test process has been invaluable to us. We did beta testing and other testing, but it wasn’t until users actually tried to use RDA Toolkit in their everyday work that some really useful comments emerged.

Virtual User Group

Certainly the U.S. community is very important to us, but the U.S. community is not the only user community of RDA Toolkit.

We need a virtual forum to get feedback that helps us set our priorities, to communicate our development plans out to RDA Toolkit users, and to demo recent changes.

Virtual User Group

• Format – webinar format but with smaller groups and more bidirectional communication.

• Audience – National Libraries and power users in many countries. Open meeting, everyone is invited.

• Agenda – demo recent release(s), describe plans for next release(s), and brainstorm ideas for future releases.

Virtual User Group

• Frequency – to be determined; please answer the post-webinar poll question about frequency.

• Time zone – offered in rotating time zones so users outside the U.S. also have a chance to participate live (considering three rotating times zones: 9:30 AM CST, 3:30 PM CST, and 8:00 PM CST)

Poll Question #2

To the best of your knowledge, what is your institution’s plan for RDA implementation?

Session Agenda

Recent RDA Toolkit Enhancements

• Index• Table of Contents• MARC Linking Service• RDA Instruction Linking• RDA Toolkit Blog

RDA Index

• Book-style index added to RDA Toolkit• Included in search to supplement full-text

search by including additional terms not in RDA

• Printable PDF for offline use• Free to everyone

Table of Contents

• Book-style RDA TOC added to RDA Toolkit• Each entry is hyperlinked to RDA• Printable PDF for offline use• Not included in search• Free to everyone

MARC Linking Service

• Create links based on specific MARC information to the relevant instruction(s) in RDA: Element Set.

• Links are based on MARC-to-RDA Mappings of RDA Toolkit.

• Link URLs contain only MARC information so they will not need updating if MARC Mappings change in RDA Toolkit.

MARC Variables

Users can link to relevant instruction(s) in RDA: Element Set based on:• Record Type – either Authority or a

Bibliographic record• MARC Field - (e.g., “100”)• Indicator - (e.g., “1st” or “2nd”)• Subfield – (e.g., $c)

MARC Based URL

The syntax to create a link to the relevant RDA instructions for MARC Bibliographic 100 1# $C

http://access.rdatoolkit.org/?encode=marc&rec=Bib&tag=100&indpos=1st&ind=1&subfld=c

Direct Links to RDA Instructions

In addition to the MARC links there may be times when users want to simply link to an RDA instruction.

To create these links use the following syntax:

Direct Links to RDA Instructions

1. Begin with the root URL of http://access.rdatoolkit.org/

2. Add the RDA number e.g., for RDA 3.1.4, add the 3.1.4 to the root URL http://access.rdatoolkit.org/3.1.4

3. Finally, add “.html” to the end http://access.rdatoolkit.org/3.1.4.html

Session Agenda

Getting Access to RDA Toolkit

• 30-day Free Trial• Post-Event Access• Double-User offer extended• Subscribe or renew online

30-day Free Trial

• Solo or Institutional trials• Full access to RDA Toolkit to evaluate and try

out the software (printing is disabled)• Open to anyone who has not already had a

free trial. June 2010’s open access and post-event access are not considered a free trial

• Sign up online at www.rdatoolkit.org/trial

Post-Event Access

• Provides free 30-day solo-user access to anyone attending an RDA training event

• RDA training instructors apply for access and give attendees a PDF (supplied to them by ALA Publishing) containing a special offer code and information on activating the offer.

• www.rdatoolkit.org/posteventaccess

Double-User Offer Extended

All new and renewing institutional subscribers (does not apply to solo–user subscriptions) before August 31, 2012 will receive double the requested users at no additional charge.

Subscribe or Renew Online

RDA Toolkit e-commerce • Subscribe (www.rdatoolkit.org/subscribe)• Renew (www.rdatoolkit.org/renew)• Calculates Double-User offer discounts• Accepts multiple currencies• Multiple payment options– PO / Invoice, Credit Card, PayPal, e-Check (ACH),

International Wire

Poll Question #3

Has anyone watching the webinar at your location accessed RDA Toolkit through one or more of the following methods? (Check all that apply.)

Session Agenda

Questions?

• With the time left during this live event, we will answer as many questions as possible.

Thank You!

After the webinar ends, you will be redirected to a post-webinar survey. We appreciate any feedback you can give us.

For more information please visitwww.rdatoolkit.org .

RDA Checkpoint - Where we are and where we're heading

Education

Transcript of RDA Checkpoint - Where we are and where we're heading

The GeorgiaGov Platform Roadmap: Where We've Been, Where We Are, Where We're Going

Container Security: How We Got Here and Where We're Going

Where We've Been, Where We're Going

Where We're Headed with the 2019 Standards

Agile Testing: Where We Are, Where We're Heading #PHTestCon2017

Adopt OpenJDK - Lessons learned and Where we're going (FOSDEM 2013)

Open: Where We're Going Next

Books? Where we're going we don't need (physical) books!

Open data: Where We've Been, Where We're Going

2011 - Where we're been, where we're going

The Future Workplace: Where we are, and where we're heading.

Construction Technology Trends - Where We're at and Where We're Headed

IN@IU - Who We Are & Where We're At

Understanding Where We're Headed by Examining Where We've Been by Athan Stephanopoulos

The Social State - What's Happening & Where We're Going

A Century of Research on Mnemonics: We're Back Where We Started

Dashboards: Where We've Been and Where We're Going (166372999)

Student Poetry: Where We're From

HTML5 Multimedia: where we are, where we're going

PART ONE: WHERE WE'RE GOING - Faculty Information … Music-3... · PART ONE: WHERE WE'RE GOING ... " Speaking Through Noise: ... I will lead us through an exploration of how it is