Alma post-implementation at the Colorado School of Mines
dc.contributor.author | Guy, Laura | |
dc.date | 2016-06 | |
dc.date.accessioned | 2016-06-27T22:01:59Z | |
dc.date.accessioned | 2022-02-08T14:55:11Z | |
dc.date.available | 2016-06-27T22:01:59Z | |
dc.date.available | 2022-02-08T14:55:11Z | |
dc.identifier.uri | https://hdl.handle.net/11124/170306 | |
dc.identifier.uri | http://dx.doi.org/10.25676/11124/170306 | |
dc.description.abstract | Implementing a library services platform such as Alma with Primo can be a major undertaking. Replacing an ILS, link resolver, ERM, and possibly other systems with a unified platform calls for rethinking workflows, retraining staff, cleaning up and migrating data, and an array of other potential areas of analysis. These can range from rethinking what patron services are offered to reviewing collaboration opportunities between or within libraries. Planning to make all of these changes within the duration of the implementation project is a challenge--both because of the scope of the changes, and because improvements in library services should continue on the new library platform. Instead, implementation can be viewed as one activity in the evolution of library services, with continuous advances before and after the implementation project. This eases the transition and allows the library to plan future improvements based on opportunities afforded by the new systems. In this session, two libraries that implemented Alma and Primo will share their perspectives on the lifecycle of system implementation. From planning, preparing, and implementing the platform to post-implementation analysis of workflows, come hear how an implementation project fits into the broader process of improving library services. | |
dc.format.medium | presentations (communicative events) | |
dc.language | English | |
dc.language.iso | eng | |
dc.publisher | Colorado School of Mines. Arthur Lakes Library | |
dc.relation.ispartof | Faculty Presentations - Library | |
dc.rights | Copyright of the original work is retained by the author. | |
dc.subject | Alma | |
dc.subject.lcsh | Libraries | |
dc.title | Alma post-implementation at the Colorado School of Mines | |
dc.type | StillImage | |
dc.type | Text |