FLICC RDA webinar 09222011


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • By now, there’s been a lot of information about the test process and report so in this presentation, rather than repeating previous presentations; e.g. ALA, BW webinar, we want to focus on the present and future, that is “where do we go from here.” To do that we will examine the recommendations in the report, specifically those recommendations that include action items in the report that need to be completed before implementation. We will then provide the findings from the report that led to that recommendation including some quotes from tester surveys, and the status of the activities. I will present the first half and in the second half, Barbara will also include some specifics on how your institution can plan for implementation and training. We’ll leave time for questions at the end
  • This was the first large-scale application of evidence-based decision making for a change in a cataloging code. These are the factors—the things we wanted to know about-- that the CC used to construct the test and gather and analyze evidence.
  • Our two primary sources of data were the over 23,366 bibliographic + authority records created for the test, especially the ca. 1200 records from the sets all testers did in common, plus the 8509 surveys received that collected information not only from record creators but also from record users and library administrators.
  • The findings—which the Coordinating Committee analyzed in depth over a 5 month period, led the CC to this overall recommendation.
  • Costs of implementing RDA occur in various areas: subscription to the RDA Toolkit , development of training materials and creation/revision of documentation, production time lost due to training and the learning curve, and impact on existing contracts. Many institutions indicated they did not yet have information to know the costs. Freely-available training materials and documentation would reduce some of the costs.   Institutions noted various benefits to be weighed against the costs. These included a major change in how characteristics of things and relationships are identified, with a focus on user tasks; a new perspective on the use and re-use of bibliographic metadata; and the encouragement of new encoding schemas and better systems for resource discovery.
  • Note the word “infrastructure” in this quote; the CC’s belief that a new infrastructure was needed for the future was key to our recommending implementation of RDA. Just as highways of concrete and bridges of steel were needed to replace dirt roads and wooden bridges once automobile traffic increased, so, too a new metadata infrastructure is needed to support appropriate metadata discovery and access for the 21 st century.
  • Concern for meeting the needs of the user was an important part of the test and findings. Test institutions were asked to show records to internal staff users and patrons. Results showed that RDA records overwhelmingly met needs and also that RDA records were either easier to use or as easy to use as AACR2 records.
  • Users noted both positive and negative features of RDA records. Interestingly some features, e.g., omission of GMDs and spelling out of abbreviations were found to be positive by some and negative by others, for the GMD, in almost equal numbers. There were those in favor of and not in favor of most of the changes.
  • A majority of test partner institutions anticipate some negative impact on local operations in acquisitions, copy cataloging, original cataloging, and bibliographic file maintenance. Nevertheless, a majority of test partner institutions felt that the U.S. community should implement RDA .   One unanticipated result of the test was that at least three institutions trained all or most of their cataloging staff in RDA and decided to continue creating RDA records after the test. This result increased the impact of a mixed RDA and AACR2 rule environment.
  • The national libraries will not implement RDA until there is assurance the tasks described above are completed or well underway. The CC is facilitating some of the action items and monitoring others.
  • Comments about MARC emerged from the survey data in surprisingly large numbers. The test made very clear that MARC was not a good vehicle for RDA—there were many coding difficulties—but even more importantly, many survey respondents expressed doubt that RDA changes would yield significant benefits without a change to the underlying MARC carrier. Most felt any benefits of RDA would be largely unrealized in a MARC environment. MARC may hinder the separation of elements and ability to use URIs in a linked data environment.
  • This quote is representative of many of the comments expressed in survey data.
  • Although discussion of exploring a transition from MARC was already under discussion at LC, the test findings demonstrated the importance and level of community realization of the need for a transition. An announcement was made by Deanna Marcum on May 13, 2011 that work was underway. Quote from the statement:”Spontaneous comments from participants in the US RDA Test show that a broad cross-section of the community feels budgetary pressures but nevertheless considers it necessary to replace MARC 21 in order to reap the full benefit of new and emerging content standards.” 
  • The importance of training cannot be underestimated.
  • Many training methods were available to RDA test participants. All of the institutions that responded to the question regarding training methods presented their staff with at least three different types of training methods. The staff at five institutions offered as many as seven different training methods.   Of the institutions responding to a question about creating or modifying local documentation for use with RDA, less than half had created documentation to record local policy decisions although some provided information about the test itself and/or about RDA. Some participants noted that any local documentation written in the context of AACR2 or any other content standard would need to be revised if RDA is implemented or even if the library only accepted for purposes of copy cataloging any RDA records created by others. Some participants noted the opportunity to simplify their local documentation.   Although 75% of those responding said that updating documentation would have a “large” or “very large” impact, only 12% of those responding to a question asking if updating documentation would be a benefit or a barrier to implementing RDA said that it would be a “major barrier.”   The three national libraries indicated that they had extensive local documentation to be reviewed and revised; much of LC’s local documentation is also national documentation. Various specialized cataloging communities and the utilities were considering their documentation plans.
  • Thanks to extensive training documentation and presentations, LC already has made a substantial start on training and will continue to lead in this area. However, LC plans to coordinate closely with PCC, ALCTS and other relevant bodies to avoid duplication of effort and to avoid to the extent possible confusing or conflicting information. One of the training needs that emerged from the test results is that more training is needed on the APPLICATION of FRBR concepts to record creation. Our sense is that while catalogers are certainly very familiar with the WEMI vocabulary and concepts in the abstract, the have problems when it comes to knowing when and how to provide access to work or expression manifested, as for example, when a resource contains more than one work. Likewise, there are many points about Toolkit use where further training would be helpful.
  • Perhaps one of the recommendations that got the most attention was the statement to “Rewrite RDA instructions.” In retrospect, we should have said, “Reword” because our intention was not to change the result of following the rules, but to have the rules reworded to ensure that catalogers would all have the same understanding of what was meant by the rule and all achieve the same outcome from following the rule. Work with JSC to prioritize which chapters should be addressed and completed first (based on testing comments). Identify and engage a writer in collaboration with JSC and Comm. Of Principals. Confirm readability of initial chapter rewrites Ensure registry is well described and in synch with RDA rules. Important point as much focus on RDA has been on the “cosmetic” changes (INSERT COSMETICS) and not on defined elements and vocabularies that will allow much more machine manipulation and linking of the data.
  • Findings showed that not only were catalogers using the new authority record fields in RDA records but in AACR2 records as well. The most used new field was the 046 for coded date information. Other commonly used fields included 370, 374, and 375. Confusion between field of activity and occupation. One way to try to distinguish these elements is that 372 should be activity or specialty (art, music, cardiology, etc.) 374 should be term for the profession/people term (artist, composer, surgeon, etc.)
  • Subjective reactions to the RDA content were mixed. Some participants liked the emphasis on transcription, cataloger judgment, and the new content/media/carrier types, as well as the elimination of abbreviations. A larger number of participants reported confusion about the structure, organization, and vocabulary in RDA and commented that the order of the rules in RDA did not match current cataloging workflows.  
  • The purpose of the readability analysis was to perform an objective test to determine an approximate readability score for RDA. A sampling of sentences from 86 random pages of the text RDA was compared with random sentence samples from AACR2, ISBD, and the CONSER Cataloging Manual using two common readability tools (Flesch Reading Ease and Flesch-Kincaid Grade Level). The comparison indicated that RDA text was the least readable (college graduate level) while the three other manuals were rated for college students (13 th -16 th grade level).   Survey responses relating to difficulties encountered indicated that over time participants gained a better understanding of RDA. There was little difference reported in difficulties encountered by different levels of staff. However, participants working in non-textual formats reported a much higher number of difficulties.
  • The Coordinating Committee identified chapters 6, 10, 11, and 17 to be priorities for “rewording” which has been approved by the JSC. These 5 chapter will be completed no later than June 2012. Potential writers have been identified although a selection has not been made. The Coordinating Committee may call on our former test partners to review any chapters that have been re-written and also rerun the chapters, both the original and revised versions, though the readability analysis tools to compare the results.
  • First bullet according to an announcement from the JSC on Aug. 8, 2011. From the JSC Summary of Progress on US RDA Test Recommendations posted Sept. 5, 2011 JSC is working with ALA Publishing to establish robust processes by which RDA will be updated and changes will be communicated to users . It is anticipated that major updates to RDA will be made not more than twice annually; It is anticipated that the frequency of minor updates will be no more than monthly; JSC is finalizing a “fast track” process which will allow low impact proposals, including: correction of typographical errors; addition or removal of examples; addition of terms to vocabularies to be accelerated; Users will have a single place (accessible through the RDA Toolkit or in the RDA Toolkit) to stay informed of RDA changes and product changes.
  • There were several positive comments related to the RDA Toolkit. However, the overall impression from the comments was that users struggled to use the Toolkit effectively. Many respondents found the Toolkit to be clunky and difficult to navigate. Respondents were not pleased with the organization (although it was at times unclear if this was the organization of the rules themselves or how they were presented in the Toolkit). Attempting to navigate to particular rules in the text via the table of contents confused many users. Many commented on having difficulty locating all of the relevant rules and that the hit list did not include enough context to decide which is the one with the needed information. There were comments that it was difficult to determine the order of results of a keyword search and suggestions were to display the results in rule order or have links to the rules first followed by links to the definitions.   The workflows present in the Toolkit were seen as useful in creating initial records because they are written in straightforward language and ease the burden of the FRBR-based arrangement of RDA by ordering the rules by MARC/ISBD area. The potential for development of specific workflows at the local level and by format-specific cataloging communities was noted. There were comments that a longer timeout period is needed and when the RDA Toolkit does timeout, some users would appreciate, if it would not wipe out the screen but rather leave the user where they are.
  • From listening to ALA Publishing Webinars on the RDA Toolkit, these are a few upcoming enhancements. They are planning on having a virtual user group that will discuss upcoming enhancements and suggestions for future development. Chapter loading is being improved. Users will be able to select their time-out length as part of their profile. A MARC linking service is/will be available which allows users to link directly to the rules in the Toolkit from their local system and/or documentation. (Piloted by OCLC). Information about these and future enhancements is available on the RDA Toolkit Blog.
  • What still remains unclear is to what extent the specialist communities will adopt RDA, or continue to use their existing manuals as is, or adapt their current guidelines to be more compatible with RDA. If the generalist who uses RDA for the occasional special item in his or her collection follows one set of descriptive practices and the music, AV, or rare book specialist follows a different set, what is the impact on identification and retrieval? While specialized communities can develop best practices for use within their groups without submitting rule change proposals to the JSC, the community as a whole will not realize the full benefit of applying a common standard unless the standard itself is changed. In today’s environment, where use of existing copy is an essential efficiency for many institutions, incorporating desired changes into RDA will help ensure that copy from a variety of sources will be as useful and usable as possible.
  • RDA Decisions Needed Task Group was charged to review a document entitled “PCC RDA Policy and Practice Decisions Needed if RDA is Adopted” and to recommend to the Policy Committee next steps, including how the decisions on each item should be made. Task Group on AACR2 & RDA Acceptable Heading Categories was charged to categorize the different types of headings currently existing within the authority file (LC NAF) and provide suggestions for handling these categories of records (batch updating vs. manual, leave alone, etc.) The Task Group on Hybrid Bibliographic Records was charged to investigate the use of hybrid records and make recommendations for best practices. The three PCC task groups have a Sept. deadline for submitting their reports and all information regarding these task forces is available on the PCC website. Task Group on AACR2 & RDA Acceptable Heading Categories report already available. The music/moving image communities are submitting one proposal via ALA and The Canadian Committee on Cataloging has submitted five proposals related to music. These proposals are available on the JSC website.
  • The Coordinating Committee made available to the library community the corpus of RDA test records for examination and experimentation. Unfortunately we received few responses from those who looked at or manipulated the records. We hope that future development work will occur using these records. The data carrier is just one of the RDA‐related issues that systems vendors must face. We cannot speculate on what new tools and services will be produced and realized with the implementation of RDA. However, If the library community does not move forward in some key areas, we will continue to be behind the development and innovation of other communities utilizing linked data and the semantic web. The Coordinating Committee continues to be in communication with vendors regarding developments in this area.
  • Quote from one the survey respondents
  • As part of the analysis process, the Coordinating Committee hosted a visit and presentation from eXtensible Catalog Organization Co-Executive Directors Jennifer Bowen and David Lindahl to discuss their partial implementation of RDA. Sample quotes from their presentation. A full written report from XCO is included as an appendix in the Report and Recommendations. The visit and statement proved quite valuable in helping the Coordinating Committee envision the current and future potential of RDA.
  • There were no reported problems in systems ingesting and storing RDA records. While existing systems can import and store RDA-based MARC 21 records, respondents indicated that substantial local configuration changes would be needed for indexing and record displays for the public. In particular, much concern was expressed about title differentiation in public displays with the loss of the 245$h (GMD). While we tried to gather RDA records produced in schemas other than MARC, very few records were received.
  • The final section of the presentation will focus on the future – what you can expect to see happening between now and implementation and what you can do to prepare for implementation at you institution. LC will have a small group of catalogers (comprised of former testers) that will resume creating RDA cataloging records in order to provide information, training, and suggestions for change. LC will use the next 18 months to train staff and update existing documentation following this anticipated timeline.
  • NLM expects to work closely with ALCTS and the PCC to develop training materials and policies that make sense for the US community and our constituents.
  • Next few slides are just examples of issues that individual institutions should be thinking about/considering during the next 12-18 months prior to implementing RDA.
  • LC Test training materials site no longer being maintained but documentation and training materials used for the test will still be available.
  • LC RDA planning website has information on LC’s RDA implementation planning activities as well as updated training documents produced during this period. Updates from the Committee will be available as a section of the LC RDA planning website
  • FLICC RDA webinar 09222011

    1. 1. Recommendations from the RDA Test: Where do we go from here? Barbara Bushman National Library of Medicine, NIH, DHHS Regina Romano Reynolds Library of Congress FLICC September 22, 2011
    2. 2. Webinar agenda <ul><ul><li>Evidence-based decision-making: evaluative factors </li></ul></ul><ul><ul><li>Recommendations: basis in findings, current status </li></ul></ul><ul><ul><ul><li>To the national libraries </li></ul></ul></ul><ul><ul><ul><li>To the JSC </li></ul></ul></ul><ul><ul><ul><li>To ALA Publishing </li></ul></ul></ul><ul><ul><ul><li>To the community (including PCC) </li></ul></ul></ul><ul><ul><ul><li>To vendors </li></ul></ul></ul><ul><ul><li>Implementation preparations </li></ul></ul><ul><ul><ul><li>LC timeline; NLM & NAL plans </li></ul></ul></ul><ul><ul><ul><li>How institutions can prepare for implementation </li></ul></ul></ul><ul><ul><ul><li>Approaches to training/documentation </li></ul></ul></ul><ul><ul><li>Sources for more information </li></ul></ul><ul><ul><li>Questions </li></ul></ul>FLICC September 22, 2011
    3. 3. Evaluative factors <ul><li>Record creation </li></ul><ul><li>Record use </li></ul><ul><li>Training and documentation needs </li></ul><ul><li>Use of the RDA Toolkit/RDA content </li></ul><ul><li>Systems and metadata </li></ul><ul><li>Technical feasibility </li></ul><ul><li>Local operations </li></ul><ul><li>Costs and benefits </li></ul>Later merged FLICC September 22, 2011
    4. 4. Primary data vehicles Records + Surveys 23, 366 bibliographic + authority records 8509 surveys FLICC September 22, 2011
    5. 5. Overall recommendation <ul><li>“ Contingent on the satisfactory progress/completion of the tasks and action items below, the Coordinating Committee recommends that RDA should be implemented by LC,NAL, and NLM no sooner than January 2013. The three national libraries should commit resources to ensure progress is made on these activities that will require significant effort from many in and beyond the library community.” </li></ul>Report, Executive Summary, p.2 FLICC September 22, 2011
    6. 6. Findings: Costs and Benefits <ul><li>Benefits </li></ul><ul><ul><li>Change in how characteristics of things are identified </li></ul></ul><ul><ul><li>Focus on user tasks </li></ul></ul><ul><ul><li>New abilities to use and re-use bibliographic metadata </li></ul></ul><ul><ul><li>Encouragement of new encoding schemas and better systems for resource discovery </li></ul></ul><ul><li>Costs </li></ul><ul><ul><li>Subscription to the RDA Toolkit </li></ul></ul><ul><ul><li>Development of training materials </li></ul></ul><ul><ul><li>Creation/revision of documentation </li></ul></ul><ul><ul><li>Loss of production time during initial training and implementation </li></ul></ul><ul><ul><li>Impacts to cataloging contracts </li></ul></ul>FLICC September 22, 2011
    7. 7. “ To achieve a viable and robust metadata infrastructure for the future, the Coordinating Committee believes that RDA should be part of that infrastructure.” Report, p. 13 FLICC September 22, 2011
    8. 8. FLICC September 22, 2011
    9. 9. Findings: user survey <ul><li>Negative Features </li></ul><ul><ul><li>Content/carrier/media elements difficult to understand; No GMD </li></ul></ul><ul><ul><li>Too much information </li></ul></ul><ul><ul><li>Spelling out of universally known abbreviations </li></ul></ul><ul><ul><li>Confusing when publishing and © dates are the same </li></ul></ul><ul><ul><li>Elimination of “sic” in a title indicating a problem on the piece </li></ul></ul><ul><ul><li>FRBR terminology </li></ul></ul><ul><li>Positive Features </li></ul><ul><ul><li>Content/carrier/media elements in place of GMD </li></ul></ul><ul><ul><li>Fuller records </li></ul></ul><ul><ul><li>Spelling out of previously abbreviated words </li></ul></ul><ul><ul><li>Rule of three dropped </li></ul></ul><ul><ul><li>Elimination of Latin terms </li></ul></ul><ul><ul><li>More access points </li></ul></ul>FLICC September 22, 2011
    10. 10. Findings: local operations <ul><li>While 63% of testing institutions anticipate a major or minor negative impact on local operations, 62% favored implementation </li></ul><ul><li>Concern was expressed about the need to work with both RDA and pre-RDA copy in the same workflow </li></ul>FLICC September 22, 2011
    11. 11. Moving Forward <ul><li>The overall recommendation lists contingent tasks and action items involving: </li></ul><ul><ul><li>U.S. national libraries </li></ul></ul><ul><ul><li>Joint Steering Committee (JSC) </li></ul></ul><ul><ul><li>ALA Publishing </li></ul></ul><ul><ul><li>U.S. library community (including PCC) </li></ul></ul><ul><ul><li>Vendors </li></ul></ul><ul><li>Additional specific recommendations to these organizations and groups are in the report </li></ul><ul><li>The Coordinating Committee has been charged with overseeing progress on the contingent tasks and reporting on their status </li></ul>FLICC September 22, 2011
    12. 12. Recommendations relating to the national libraries FLICC September 22, 2011
    13. 13. RECOMMENDATION: Demonstrate credible progress toward a replacement for MARC TIMEFRAME: 18-24 months FLICC September 22, 2011
    14. 14. Findings: MARC <ul><li>MARC was not part of the evaluative factors or testing plan </li></ul><ul><li>Issues and comments about MARC surfaced during the test and analysis </li></ul><ul><li>Most survey respondents believe that the benefits of RDA will be unrealized without a change to the underlying MARC carrier </li></ul>FLICC September 22, 2011
    15. 15. <ul><li>“ The RDA Test has made it concrete for us that the community also very much needs a post-MARC data model and encoding structure.” </li></ul><ul><li>Test participant </li></ul>FLICC September 22, 2011
    16. 16. MARC recommendation status; plan <ul><li>Announcement by Deanna Marcum: “Transforming our Bibliographic Framework” </li></ul><ul><li>Stakeholders being identified—fall 2011 </li></ul><ul><li>Tasks and timetable for development to follow </li></ul>FLICC September 22, 2011
    17. 17. RECOMMENDATION: Lead and coordinate RDA training <ul><li>TIMEFRAME: </li></ul><ul><li>18 months </li></ul>FLICC September 22, 2011
    18. 18. Findings: training and documentation needs <ul><li>Most institutions provided staff with at least 3 different types of training prior to the test </li></ul><ul><li>Fewer than half created documentation for policy decisions during the test </li></ul><ul><li>75% believe updating existing documentation will have a large or very large impact, but only 12% consider that a major barrier to implementation </li></ul><ul><li>More full record and in-context examples are desired </li></ul>FLICC September 22, 2011
    19. 19. Training recommendations <ul><li>LC to lead training efforts </li></ul><ul><li>PCC, ALCTS, other bodies to be engaged </li></ul><ul><li>More training needed on FRBR concepts, toolkit </li></ul><ul><li>Status: </li></ul><ul><ul><li>LC updating test training and documentation </li></ul></ul><ul><ul><li>Coordinating with ALA Publishing about RDA Toolkit </li></ul></ul><ul><ul><li>Coordinating with PCC—2 task group reports now available for comment </li></ul></ul><ul><ul><li>Creating a training/implementation timetable </li></ul></ul>FLICC September 22, 2011
    20. 20. Recommendations related to the JSC FLICC September 22, 2011
    21. 21. <ul><li>RECOMMENDATIONS: </li></ul><ul><li>Rewrite [reword] RDA instructions in clear, unambiguous, plain English </li></ul><ul><ul><li>Within 18 months </li></ul></ul><ul><li>Define process for updating RDA in the online environment (in conjunction with ALA Publishing) </li></ul><ul><ul><li>Within 3 months (JSC had already begun work on this issue) </li></ul></ul><ul><li>Announce completion of registered RDA element sets and vocabularies </li></ul><ul><ul><li>Within 6 months [already underway] </li></ul></ul>FLICC September 22, 2011
    22. 22. Findings: bibliographic record review <ul><li>Textual monographs for translations and literary works included more errors related to FRBR </li></ul><ul><ul><li>Omission of access points for works and expressions manifested (RDA core) </li></ul></ul><ul><li>All resources included frequent errors in publication place, date, copyright date </li></ul><ul><li>Confusion about use of abbreviations was more evident in AV resources </li></ul><ul><li>Seriality was problematic in both RDA and A2; some current online versions cataloged as reproductions </li></ul><ul><li>Integrating resources and serials included mode of access notes (not in RDA); incorrect handling of date information </li></ul>FLICC September 22, 2011
    23. 23. Findings: authority record review <ul><li>New elements used (percent of records): </li></ul><ul><ul><li>coded date information in field 046 (29%) </li></ul></ul><ul><ul><li>associated place information in field 370 (16%) </li></ul></ul><ul><ul><li>occupation and gender in fields 374, 375 (10%) </li></ul></ul><ul><li>Common errors: </li></ul><ul><ul><li>form of place name in 370 </li></ul></ul><ul><ul><li>omission of 670 fields </li></ul></ul><ul><ul><li>incorrect formatting of coded dates in 046 field </li></ul></ul><ul><ul><li>confusion between field of activity and occupation (fields 372 vs. 374) </li></ul></ul>FLICC September 22, 2011
    24. 24. Findings: RDA content <ul><li>Some were positive, e.g., “does well what it aims to do” </li></ul><ul><li>Negatives focused on readability and organization, e.g., style and language as obstacles to understanding </li></ul><ul><li>Catalogers remain confused about distinctions between FRBR entities </li></ul><ul><li>Content should provide more detailed guidance, examples </li></ul>FLICC September 22, 2011
    25. 25. Findings: RDA Readability <ul><li>Readability analysis with other cataloging rules (AACR2, ISBD, CONSER Cataloging Manual) found RDA text to be the least readable </li></ul><ul><li>Reported difficulties in using RDA dropped with record creation experience from 54% to 14.5% </li></ul><ul><li>Participants working in non-textual formats reported higher degrees of difficulty </li></ul>FLICC September 22, 2011
    26. 26. “… difficult to understand … each person may arrive at a different conclusion from the same instruction.” “… the weakness of RDA is the “disorganized vagueness” of the RDA rules.” Test participant Test participant FLICC September 22, 2011
    27. 27. Status: RDA content recommendations <ul><li>“ Re-wording:” 5 chapters have been identified; potential writers identified </li></ul><ul><li>Clarification of the WEMI boundaries and differences in cataloging resources with various modes of issuance is being discussed </li></ul><ul><li>LC, PCC will work with JSC on topics such as new authority elements, issues relating to expressions, specialized communities, etc. </li></ul>FLICC September 22, 2011
    28. 28. Status of tasks relating to JSC <ul><li>Registered RDA element sets and vocabularies </li></ul><ul><ul><li>First group of RDA controlled vocabularies “published” in the Open Metadata Registry http://metadataregistry.org/rdabrowse.htm </li></ul></ul><ul><li>Defining process of updating RDA </li></ul><ul><ul><li>JSC is finalizing “fast track” process for low impact proposals </li></ul></ul><ul><ul><ul><li>Major updates not more than twice annually </li></ul></ul></ul><ul><ul><ul><li>Minor update no more than monthly </li></ul></ul></ul><ul><ul><ul><li>Updates to print will occur less frequently </li></ul></ul></ul><ul><ul><li>Single place in/through RDA Toolkit to stay informed of changes </li></ul></ul>FLICC September 22, 2011
    29. 29. Recommendations to ALA Publishing
    30. 30. RECOMMENDATIONS: Improve functionality of the RDA Toolkit TIMEFRAME: within 3 months (ALA had already begun work on this issue) <ul><li>Integrate complete RDA record examples in MARC and other encoding schema into the RDA Toolkit (in conjunction with JSC) </li></ul><ul><li>TIMEFRAME </li></ul><ul><ul><li>within 6 months </li></ul></ul>FLICC September 22, 2011
    31. 31. Findings: use of RDA Toolkit <ul><li>Users found the Toolkit clunky and difficult to navigate </li></ul><ul><li>Organization of the rules was confusing </li></ul><ul><li>Organization of search results not intuitive </li></ul><ul><li>Many found the workflows useful </li></ul><ul><li>Longer period before timeout is needed </li></ul>FLICC September 22, 2011
    32. 32. Status of tasks relating to ALA Publishing <ul><li>Creation of a virtual user group </li></ul><ul><li>Chapter loading being improved </li></ul><ul><li>Time-out length will be a profile choice </li></ul><ul><li>MARC Linking Service </li></ul><ul><li>RDA Toolkit Blog </li></ul>FLICC September 22, 2011
    33. 33. Recommendations to the community, including PCC FLICC September 22, 2011
    34. 34. RECOMMENDATION: Ensure and facilitate community involvement TIMEFRAME: within 12 months FLICC September 22, 2011
    35. 35. Specific recommendations to the community <ul><li>Prioritize needed updates to practices, decisions, documentation </li></ul><ul><li>Prioritize and submit changes to JSC for RDA content </li></ul><ul><li>Determine the role of PCC, special interest communities </li></ul><ul><li>Determine best methods to share decisions within the community </li></ul>FLICC September 22, 2011
    36. 36. Community involvement: status <ul><li>PCC has established task groups </li></ul><ul><ul><li>RDA-Decisions-Needed Task Group </li></ul></ul><ul><ul><li>Task Group on AACR2 & RDA Acceptable Heading Categories </li></ul></ul><ul><ul><li>Task Group on Hybrid Bibliographic Records </li></ul></ul><ul><li>Representatives from ISBD and ISSN will meet with the JSC at their Glasgow meeting (Nov. 2011) to work on harmonizing divergent practices </li></ul><ul><li>Special format communities submitting proposals for changes to RDA instructions </li></ul>FLICC September 22, 2011
    37. 37. Recommendations to the vendor community FLICC September 22, 2011
    38. 38. RECOMMENDATION to LC and vendor community: Solicit demonstrations of prototype input and discovery systems that use the RDA element set (including relationships) <ul><li>TIMEFRAME : </li></ul><ul><li>Within 18 months </li></ul>FLICC September 22, 2011
    39. 39. Findings: need for systems prototypes <ul><li>Survey comments indicated respondents could not envision how RDA rules and FRBR concepts would provide benefits in future systems </li></ul><ul><li>Entities/funding need to be identified to provide models </li></ul><ul><li>Prototypes to be developed </li></ul><ul><li>Demonstrations to be used in education and promotion </li></ul><ul><li>Status: </li></ul><ul><ul><li>in planning stages </li></ul></ul>FLICC September 22, 2011
    40. 40. <ul><li>“ I understand and welcome the changes that RDA seeks to address but it would be nice to see the tools that will take advantage of what this new standard has to offer.” </li></ul><ul><li>Test participant </li></ul>FLICC September 22, 2011
    41. 41. Findings: eXtensible Catalog <ul><li>“ Use of RDA elements, even within a MARC-based structure will help XC’s metadata cleanup and transformation programs work more effectively than does AACR2 data.” </li></ul><ul><li>“ XC Schema is a foundation for a solid RDA implementation that is usable in real systems, addresses real use scenarios and works with existing integrated library systems and web content management systems.” </li></ul>FLICC September 22, 2011
    42. 42. Specific vendor recommendations <ul><li>Permit users to link out to RDA Toolkit </li></ul><ul><li>Implement all new MARC tags </li></ul><ul><li>Explore enhancements, new features and products, e.g.: </li></ul><ul><ul><li>Display of content, media, carrier data </li></ul></ul><ul><ul><li>Support for a mix of AACR2 and RDA records </li></ul></ul><ul><ul><li>Support for FRBR relationships </li></ul></ul><ul><ul><li>Ingestion of metadata in a variety of formats </li></ul></ul><ul><ul><li>Better support for global update of headings </li></ul></ul>FLICC September 22, 2011
    43. 43. Findings: Systems, Metadata, and Technical Feasibility <ul><li>System vendors have made the changes needed to import and store RDA records encoded in MARC 21 </li></ul><ul><li>Substantial local configuration changes needed for indexing and record displays </li></ul><ul><li>Unable to perform in-depth analysis of non-MARC records since very few received </li></ul>FLICC September 22, 2011
    44. 44. LC Timeline <ul><li>October 2011: RDA catalogers/technicians (former LC testers) prepare for returning to RDA cataloging: classroom sessions and practice record discussions </li></ul><ul><li>November 2011: RDA catalogers/technicians return to creating RDA authority and bibliographic records </li></ul><ul><li>Not sooner than July 2012: LC begins to train remaining catalogers to apply RDA </li></ul>FLICC September 22, 2011
    45. 45. NLM & NAL Plans <ul><li>NLM </li></ul><ul><ul><li>No plans to implement prior to 2013 </li></ul></ul><ul><ul><li>Starting to familiarize staff with FRBR concepts and terminology </li></ul></ul><ul><ul><ul><li>Practical RDA training 3 months prior to implementation </li></ul></ul></ul><ul><ul><ul><li>Testers may begin producing RDA records 4 months prior to implementation to assist with staff training </li></ul></ul></ul><ul><ul><li>Updating documentation for staff and contractors </li></ul></ul><ul><li>NAL </li></ul><ul><ul><li>Monitoring progress of recommendations </li></ul></ul><ul><ul><li>Preparing for coordinated implementation in 2013 </li></ul></ul>FLICC September 22, 2011
    46. 46. Preparing for Implementation: Systems <ul><li>MARC Issues </li></ul><ul><ul><li>Has your ILS implemented all the MARC updates for the new RDA elements? </li></ul></ul><ul><li>Indexes </li></ul><ul><ul><li>Will authorized access points containing relationship designators file properly with the headings lacking them? </li></ul></ul>FLICC September 22, 2011
    47. 47. Preparing for Implementation: Cataloging <ul><li>Authorized access points </li></ul><ul><ul><li>If existing authorized access points are converted nationally to the RDA form, will you convert your records and how? </li></ul></ul><ul><ul><ul><li>Authority records </li></ul></ul></ul><ul><ul><ul><li>Bibliographic records </li></ul></ul></ul><ul><li>Copy Cataloging </li></ul><ul><ul><li>Will you accept AACR2 copy or will you edit to partial or full RDA description? </li></ul></ul><ul><ul><li>Will you convert authorized access points on AACR2 copy to the RDA form? </li></ul></ul>FLICC September 22, 2011
    48. 48. Preparing for Implementation: OPAC <ul><li>Display of content/media/carrier types </li></ul><ul><ul><li>How will the new content/media/carrier types display in your local catalog? </li></ul></ul><ul><ul><li>Will they be displayed on brief as well as full record displays? </li></ul></ul><ul><ul><li>What alternative display options does your local catalog offer, such as icons or alternative text? </li></ul></ul><ul><ul><li>Can they co-exist with existing GMDs? </li></ul></ul>FLICC September 22, 2011
    49. 49. Approaches to Training <ul><li>LC hopes to announce its implementation date approximately 6 months in advance </li></ul><ul><li>Training on terminology and concepts can begin now </li></ul><ul><li>Training on specifics should not begin until approximately 6 months before implementation </li></ul>FLICC September 22, 2011
    50. 50. Documentation Availability <ul><li>LC training materials from the test </li></ul><ul><ul><li>http://www.loc.gov/catdir/cpso/RDAtest/rdatraining.html </li></ul></ul><ul><li>RDA Toolkit Training </li></ul><ul><ul><li>http://www.rdatoolkit.org/training </li></ul></ul><ul><li>ALCTS RDA Webinars </li></ul><ul><ul><li>http://www.ala.org/ala/mgrps/divs/alcts/confevents/upcoming/webinar/cat/rda.cfm </li></ul></ul>FLICC September 22, 2011
    51. 51. Sources for More Information <ul><li>Final Report and Recommendations </li></ul><ul><ul><li>http://www.loc.gov/bibliographic-future/rda / </li></ul></ul><ul><li>LC RDA planning </li></ul><ul><ul><li>http:// www.loc.gov/aba/rda / </li></ul></ul><ul><li>MARC Transition website </li></ul><ul><ul><li>http:// www.loc.gov /marc/transition/ </li></ul></ul><ul><li>RDA Toolkit </li></ul><ul><ul><li>http:// www.rdatoolkit.org / </li></ul></ul><ul><li>JSC </li></ul><ul><ul><li>http://www.rda-jsc.org / </li></ul></ul><ul><li>Regular updates from Committee </li></ul>FLICC September 22, 2011
    52. 52. <ul><li>Thank You! </li></ul>FLICC September 22, 2011 [email_address] [email_address]