Many settings and configurations must be managed centrally or distributed from the Network Zone to enable Alma functionality in each Institution Zone.

For example:

• Distribute letter/notice templates, role profiles and assignments

• Resource sharing configurations in the NZ with the peer-to-peer model in Alma. These include The identification of Partner Libraries, Sending Borrowing Request Rules, Locate Profiles, and Determining Rota.

With a centralized perspective, OCLS is in the optimal position to review product updates, perform testing in sandbox, coordinate testing with colleges, report to and roll out to participating colleges.

Some colleges may not have the staff capacity or expertise to make configuration changes in their IZ or Primo VE instance. OCLS, by request, can make those changes on behalf of the college.

For example:

• configuring loan, booking and request policies

• configuring changes to how links, items and holdings display in Primo VE

• self-check kiosk integration

• troubleshoot an issue with Ex Libris while college library staff can focus on other tasks

• college library staff who do not have capacity to do preliminary research on a function in Alma or Primo VE, ask OCLS to figure it out, in some cases test in Sandbox and implement

This builds capacity and expertise across the consortia with staff who are positioned to develop and share that knowledge and expertise for all members big and small to benefit. The work can also be replicated across IZs when recommended by CLO and requested by individual members.

It is possible to create reports containing information from the Network Zone and to share reports created in the Network Zone. OCLS can be responsible for configuring analytics for the network zone, identify existing reports in the Alma Analytics Community Folder that can be used by Page 1+ libraries, create and maintain shared reports as needed, or assist individual colleges in the creation of reports for their own purposes.

Sandboxes are the Alma/Primo VE test environments. Library staff and OCLS may use these sandboxes for training and experimenting with different configurations or integrations. OCLS can manage these sandboxes and develop guidance on how the Page 1+ colleges can use the Alma and Primo VE sandboxes.

For example,

• Develop sandbox policies and procedures

• Manage testing credentials in sandboxes

• Manage Developer Network credentials for sandboxes and create API keys for the sandbox environments on demand

• Review and test new releases and enhancements in the sandbox environments and introduce them to colleges

• Manage the refresh of sandboxes. This includes requesting the refresh, requesting extra features to be turned on as needed, and testing after the refresh

• Resolve sandbox problems as identified

• Assist colleges with LIT program training. This may include creating accounts, assigning roles, troubleshooting, and data cleanup

• Coordinate with LIT program training colleges to manage sandbox refresh

Out of Scope Activities

• Perform testing in sandboxes for colleges

• Remove college-created testing data

• Restore college-created testing data

• Retain college-created testing data during the sandbox refresh

OCLS is the expert on the Page 1+ consortium, it’s consortial services, and shared data that are embedded in the system (eResource Management, Remote Access, CLEAR, Metadata Management, the Network Zone). With this customized expertise and admin access to the NZ and IZs, OCLS is in a unique position to provide hands-on support to the colleges.

For example:

• Assist in troubleshooting an issue or a question that requires familiarity with consortial decisions and shared services.

• Compare system settings and provide examples of what other colleges have done (ex: what language have other colleges used in their letters).

• Further research and identify issues that can be resolved with OCLS support or a consortial initiative.

• Formulate questions for Ex Libris.

• Troubleshoot an issue to determine if the issue is OCLS service-related or is an issue for ExLibris to address.

Out of Scope Activities

• Escalate a support ticket with Ex Libris.

OCLS is in a position to act as a strategic resource in support of consortial decision-making and planning. As a central service, OCLS can identify dependencies resulting from the work of different committees as well as OCLS services. In this way, we avoid duplication of effort and leverage the advantage of collaboration in the Page 1+ Consortium and college efforts.

For example:

• Provide research and analysis to help library leadership identify options and implement solutions to business or operational problems.

• Prepare information in advance of meetings so that committees and working groups can easily consider consequences and come to decisions.

• Coordinate, support, and facilitate committees, working groups and Communities of Practice (COPs).

• When the consortium has made decisions that impact IZ configurations not covered by ExLibris documentation, OCLS will support communication, and share expertise and knowledge.

• OCLS can also manage documentation that is shared across colleges such as a consortial “List of Suppressed Terms” and instructions on how to implement the list in a college Primo VE.