1 / 11

Next Generation Melvyl Pilot Update to the ULs November 20, 2008

Next Generation Melvyl Pilot Update to the ULs November 20, 2008. Co-chairs of the Implementation Team Patti Martin, CDL Terry Ryan, UCLA. User Assessment. Three streams of information from users Usability testing (UW & UC) and interviews (Ohio State) Online survey results

aiko
Download Presentation

Next Generation Melvyl Pilot Update to the ULs November 20, 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Next Generation Melvyl PilotUpdate to the ULsNovember 20, 2008 Co-chairs of the Implementation Team Patti Martin, CDL Terry Ryan, UCLA

  2. User Assessment Three streams of information from users • Usability testing (UW & UC) and interviews (Ohio State) • Online survey results • Feedback comments

  3. User Assessment Findings What Users Value • The breadth of the service, searching at the international network level • Integration of journal articles • Ease of use, with a single search box and more intuitive searching

  4. User Assessment Findings What Users Find Challenging • Lack of a Request button • Difficulties printing or emailing • Problems accessing materials • Incomplete reclamation and record mismatches • Performance problems • Confusing access to electronic content • Edition merging problems, such as for music

  5. Transitioning to Pre-Production Phase • Assessment shows sufficient promise to prepare for production • Both UC and OCLC have pre-production work to do • We will continue to assess progress

  6. Pre-Production: What OCLC Must Do OCLC deliverables • Complete Request integration • Improve access to electronic resources • Improve response time, including loading and maintenance of LHRs • Support integration of RLF and affiliated libraries • Negotiate more MARC record loads from vendors

  7. Pre-Production: What UC Must Do UC Tasks • Complete reclamation projects, including SCP, RLF, and LHRs • Make policy decisions: RLFs, affiliated libraries, non-UC libraries, on order / in process records • Define the critical mass: how much of the collection is enough for initial production • Implement ongoing maintenance and update processes • Identify alternatives to meet librarian needs • Finalize agreements with OCLC: service levels, payment schedules, future partnership

  8. Pre-Production: What Each Campus Must Do Campus Tasks • Complete reclamation projects, including RLFs and SCP • Develop a process to load and maintain LHRs • Come to agreements with affiliated libraries about being included in the campus view • Keep NGM configurations up to date, reporting local changes to status messages, uptime contacts, Z39.50 addresses, etc. • Assist in troubleshooting and testing • Contribute expertise and information to policy analyses and planning

  9. Timeline for Campus Tasks Before campuses begin their work • The Implementation Team will gather input and layout options • The Executive Team and the ULs will make the final policy decisions • The Implementation Team will issue guidelines and information to the campuses

  10. Production Target: July 1, 2009 When we go to full production, UC will • Move planning, oversight and ongoing support from pilot process to production process • Point to the Next Generation Melvyl as the default union catalog • Set a date for retiring current Melvyl

  11. Questions?

More Related