1 / 29

WHY NEW ERMS?

CORAL: UConn’s Implementation and Use of an Open Source Electronic Resources Management System Chenwei Zhao University of Connecticut Libraries. WHY NEW ERMS?. Homegrown ERMS Old & outdated Rigid Access No uploading. New ERM Team.

franz
Download Presentation

WHY NEW ERMS?

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. CORAL: UConn’s Implementation and Use of an Open Source Electronic Resources Management SystemChenwei ZhaoUniversity of Connecticut Libraries

  2. WHY NEW ERMS? Homegrown ERMS • Old & outdated • Rigid • Access • No uploading New ERM Team

  3. CORALCentralized Online Resources Acquisitions and Licensing

  4. CORAL

  5. CORAL Interoperable

  6. CORAL Highly Flexible Image source: http://justcreative.com/2012/01/11/how-to-get-better-clients/

  7. INSTALLATION Designated virtual machine: IT: CORAL documentation: (https://erm.library.nd.edu/documentation)

  8. IMPORTING Resource IDs in CORAL

  9. INSTALLATION + IMPORTING Total time spent: (Sporadic efforts. Back and forth for adjustments) 3-4 weeks

  10. USE Three types of accounts /users • Administrator • ERM Team • Other Library Staff

  11. USE: ADMINISTRATOR • Manage user accounts • Set up user privileges • Update settings (Customizations within CORAL) …

  12. USE: ADMINISTRATOR

  13. USE: ERM TEAM Add/edit data

  14. USE: OTHER LIBRARY STAFF View Only Licensing terms for ILL, E-reserve, Course Packets

  15. CUSTOMIZATION Everything is documented: • Within CORAL by Administrator • Technical backend by local IT • Major changes by CORAL community

  16. CUSTOMIZATION: WITHIN CORAL

  17. CUSTOMIZATION: WITHIN CORAL

  18. CUSTOMIZATION: WITHIN CORAL

  19. CUSTOMIZATION BY IT

  20. CUSTOMIZATION: MAJOR FEATURES

  21. CUSTOMIZATION: MAJOR FEATURES

  22. CUSTOMIZATION: MAJOR FEATURES

  23. NEXT STEP: WORKFLOW

  24. NEXT STEP: WORKFLOW

  25. NEXT STEP: MANAGEMENT MODULE Live now: https://github.com/ndlibersa Image source: http://www.mrhandymanfranchise.co.uk/next-steps/

  26. CORAL SUPPORT • https://erm.library.nd.edu/ • Github: https://github.com/ndlibersa Technical docs. Updates, latest versions.

  27. Free • Easy to install and maintain • Flexible • User-friendly • Support

  28. “There is no fully implemented ERMS, because the world of electronic resources is always changing.” --Galadriel Chilton ERM Librarian at UConn

  29. chenwei.zhao@lib.uconn.edu http://www.linkedin.com/in/chenweizhao http://www.slideshare.net/ChenweiZhao http://s.uconn.edu/czhao Questions? ChenweiZhao Electronic Resources Coordinator University of Connecticut Libraries Special thanks to Nicholas Eshelman, Galadriel Chilton, and Jennifer Eustis for their help with this presentation.

More Related