| Page Properties | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Collection Development: The cooperative approach between EAR and SDLC for researching new e-resources, setting up trials, acquiring new shared e-resources will continue and will now also include at least two members of the Electronic Resources Management (ERM) Team to work with EAR. (NEED A POST-MIGRATION TEAM-DOESN'T NEED TO BE THE SAME MEMBERS). It is recommended the ERM Team, in conjunction with EAR, work with Analytics to generate reports displaying sufficient overlap of e-resources to acquire a new shared e-resource or provide data that may mitigate the removal of a shared e-resource from the ECC. (WORK ON HOW TO COMMUNICATION BETWEEN ALL GROUPS)
Licenses: Our goal is to help simplify management of shared resources and that included licenses for the ECC and Opt-in shared e-resources. Managing licenses for shared e-resources will be a joint effort between SDLC and the Alma Network Zone (NZ) administrator.
...
- See Alma documentation for details on how to manage License Terms and add License Terms. Recommended that user have Acquisitions Manager role to edit License Terms. The list of recommended license terms can be found in Appendix B. (IS THERE A DIFFERENCE IS DISPLAYING LICENSES IN ALMA vs PRIMO? -include a separate list of public license terms and BackOffice recommendations?) Refer to the ONIX-PL documentation as a guide for standard license fields.
- It is recommended to track perpetual access titles in the license. See Appendix B for license term field. There will be more information about licenses as the 360 Migration Project continues.
Procedures in Alma
Collection Development
...