Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie CORAL, NETSL 2014 Spring
Ähnlich wie CORAL, NETSL 2014 Spring (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
CORAL, NETSL 2014 Spring
- 1. CORAL: UConn’s Implementation and Use of an Open Source Electronic Resources Management System Chenwei Zhao University of Connecticut Libraries
- 2. WHY NEW ERMS? Homegrown ERMS • Old & outdated • Rigid • Access • No uploading New ERM Team
- 3. CORAL Centralized Online Resources Acquisitions and Licensing
- 4. CORAL
- 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) …
- 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
- 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
Hinweis der Redaktion
- Info about e resource was messy (file cabinets, emails, heads). Sort things out. Spreadsheet. Limitations.
- Very flexible. Customizable based on your library’s needs. Licensing module was first released in summer 2010. More modules came after.
- Framework, basically the software you need. All open source. MySQL 5: Relational Database Management System. The nature of CORAL is a bunch of relational databases. PhP5: A server-side scripting language designed for web-development. Brings the databases a web interface. Apache: or a picture of a web server?
- Four modules: show UConn’s coral landing page: http://coral.lib.uconn.edu/coral/Example: Resource and Organization module: provider linked (Demo, Demo publishing)
- Easy to customize. Show admin page, add note types, resource types etc.
- RedHat: licensed. Linux server, a type of web server. (Support from the vendor).IT: Networked Services LibrarianDocumentation: online. Each module can be downloaded separately. We installed all four. According to IT, the documentation was not complete, and he had to write to the developer. Not major problems. It took him several hours to install, and the installation succeeded on the first try. I installed all four modules on my own computer. I did a lot of googling and succeeded too.
- We have a master list for all our electronic resources. It’s a spreadsheet. Before we did the importing, we matched the resource IDs in CORAL manually. Information imported included. Php Scripts required.
- The installation was in spring of 2013. We have been using CORAL since then. Admin: set up by IT during installation?
- Who: our Electronic Resources Management Librarian. Can have as many as you want.
- Can’t delete a resource, only the admin. Security featuresNothing’s done accidentally
- Not much in Organizations moduleShow live demo licensing admin screen, live demo resource admin screenDocumentation
- Resource module: most recently added resource type: App.
- Licensing module: show live demo admin screenMost recently added qualifier
- Show our CORAL licensing screenMost recently added note types: serving as institutional memory. Show search this note type (Demo)User feedback: show search this note type, show attachment.
- File upload size: our licensing module. Is IT a must? Yes, that’s something has to be done in PhP. Googling.
- Within CORAL: examples: qualifiers, resource types (app), note type (user feedback)IT: file uploading size limit (show live). 2 mb-10 mb
- Track multiple year costs. Mock up.
- How long does it take for the community to make upgrades and new features?
- A very attractive feature to us in the first place, but since we are a new team, there have been lots of adjustments to our work, we are not there yet. This feature is like an electronic flyer. The administrator sets up workflows for each type of resources, and assign each step to a user group (show live demo admin screen). When a task is active, that group will receive an email. When the task is finished, that user/user group marks it as complete, and the next user group will be notified in emails. (show live demo how to set up user group)
- This summer. Live since this March. Store license templates, terms tools, etc. The word got out in the CORAL user group meeting at the ER&L conference last month.
- Live demo: sandbox, automatically an admin. Explorations. Test things out there.
- Maintain: very little support is needed from IT. Automatic backup daily.Flexible: easy to make changes. can be a stand-alone system or integrated into the newer generation ILS.
- CORAL meets our needs! Robust, solid, flexible. More functional.