Skip to end of banner
Go to start of banner

Electronic Resource Management (ERM) Service Proposal

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Service Area: Electronic Resource Management

Summary

Central management of e-resource and vendor records in the Network Zone (NZ) for e-resources acquired through OCLS’s eResource Management service.

Rationale

Managing electronic collections and portfolios centrally:

  • Enables efficient discoverability and access for end users, and – in conjunction with the vendor records – supports the colleges' IZ acquisition data and workflows

  • Reduces duplication of records where multiple colleges license the same content and ensures record quality meets the established standard

  • Reduces duplication of records and the overall record count in our shared environment (a cost component of the software licence).

  • Reduces library staff workload across the system

Managing vendor records:

  • Supports the colleges' use of Alma for managing acquisition and budget data

Access Requirements:

  • To create and maintain the records, OCLS staff will require administrative access to the NZ Alma instance

  • To test and troubleshoot issues with the records, OCLS staff will require:

    • Access to each college’s Primo/Page 1+ discovery (public access is sufficient)

    • User credentials for each college’s:

      • Local user authentication systems (SSO or EZproxy as applicable)

      • Alma (view only access is sufficient)

Dependencies:

  • CLEAR: collection records are required in NZ for CLEAR links to appear in the colleges' Primos

  • LSM team services:

    • Local collection records are prerequisite for creating import profiles as well as publishing bibs for missing e-resources to the colleges' Primos

    • Possibly LSM team will manage the vendors distribution job? TBD

Future Considerations:

  • Manage or support “upload electronic holdings” integration profiles in the NZ

  • Manage trials in the NZ

  • Submit NZ collections to the CZ for use by colleges outside the Page 1+ network

  • Use Alma as a consortial ERMS (manage complete acquisition workflow in NZ, including but not limited to funds, orders, invoices, and licences) or connect Alma with our existing consortial ERMS (ConsortiaManager)

  • Create negotiation licences to further streamline the colleges' acquisition workflow in Alma

  • Include the colleges' independent e-resources in the NZ

Proposed Funding Model

  • Centrally funded:
  • Cost recovery:
  • Professional Service:
  • Under review

Service Activities

Although things may shift as we move forward, the OCLS Activities table outlines the high-level activities that OCLS currently believes will be part of this service.

Activities that we propose that colleges/third parties will need to undertake are noted in the Out of Scope Activities table. These out of scope activities are not meant to be an exhaustive list of all activities for the colleges, but rather to identify activities that OCLS will not be undertaking on behalf of the colleges post Go Live.

OCLS Activities

 OCLS will be responsible for these activities.

Activity

Notes

Activate Community Zone (CZ) electronic collection and portfolios, configure as necessary to support access, and distribute to licensed colleges

Configuration may include, for example, enabling for proxy (remote) access and entering customer linking parameters

Enhance CZ e-resource collection records as needed to support discoverability and access

Enhancements may include, for example, overriding title, description, and URL fields, with a priority focus initially on meeting basic functional requirements

Create local electronic collections where no viable options exist in the CZ

We’re still exploring solutions for these missing e-resources, and this may overlap with other service proposals

Provide the colleges with front-line tech support for NZ e-resources

Including system testing and troubleshooting and liaising with the e-resource vendor and ExLibris

Create vendor records in the NZ and distribute to college IZs

The distribution part may fall under a different service proposal? (Also see my note under “Dependencies”)

Integrate CLEAR permitted uses  in the Page 1+ Alma/Primo environment

Documentation

 

Out of Scope Activities

Colleges/other parties will be responsible for these activities.

Activity

Notes

Creation and maintenance of funds, orders, invoices, and other elements of the Alma acquisition infrastructure not described under “OCLS Activities” above

Colleges are required to create these records if they wish to use Alma’s acquisition functionalities

Maintenance of records for the colleges' independent e-resources

An “independent” e-resource is one acquired by the college in direct communication with the vendor, outside of OCLS’s eResource Management service, and therefore not represented in OCLS’s consortial ERMS (ERMA/CM)

Systematic testing of any colleges' NZ e-resources

OCLS will provide the colleges with information to map their OCLS-acquired e-resources with their NZ e-resource records, as well as tech support in response to college service requests

 Creation of licence records

Licence records may be considered in the future in light of developments in CLEAR and/or in OCLS’s provision of centralized support for acquisition workflows in Alma

 Proposal Details

Drafted on:

 

Prepared by:

 Nicole Morgan

Prepared for:

E-resources/Acquisitions Subcommittee or Implementation Steering Committee?

Reviewed on:

 

Finalized on:

 

Attachments

This service proposal follows upon ExLibris' third or middle model option for collaborative ERM workflows in Alma networks:

The proposed workflow:

  • No labels