As I mentioned in my last post, I am excited to explore the applicability of ERMes as an e-resource management system at the University of Connecticut. While I have yet to determine if ERMes is the right ERM for the long-term, I am planning an immediate implementation of ERMes because:
- UConn Libraries’ existing home-grown ERM is primarily used to generate an A-Z list and subject pages.
- The existing ERM does not have reports and the reports in ERMes are integral to my work!
- Though UConn has a great ITS team and a programmer to support the existing ERM, I do not have the skills to quickly customize it on my own.
- The existing ERM does not include cost information, but does include nearly all of the data entry fields listed in the DLF ERM Initiative’s Electronic Resource Management System Data. Structure. This means that the system is quite complex and includes more unused fields than used fields.
- I need to quickly gain an understanding of UConn’s e-resource collection and using a system I already know will save time.
- If ERMes is not appropriate as a long-term ERM, I will have all the e-resource data in one place which will make it much easier to migrate to another ERM.
With that said, I will be documenting my implementation process with hopes that doing so will help other users!
The following installment is short, but shows how I have a back-up instance of ERMes, and how I customize the Preliminary Information tables for Access and Source.
The Access table is intended identifies which campuses, locations, or groups that have access to an e-resource while the Source table identifies who is paying subscription and purchase fees. But of course, because it is ERMes, these fields can be customized and changed to match your needs!
Implementing ERMes Video: Part 1
Note: For more detailed instructions and information about implementing ERMes, please see the instructions and release notes on the ERMes website.