I have an Alma or Primo VE problem, what do I do?

From July 26th - August 27th: please follow the instructions below to report a SILS Alma or Primo VE problem.

For the first month of SILS Go-Live, problems will primarily be triaged and resolved by our Ex Libris implementation team. Future iterations of “report a problem” processes aim to have a robust UC SILS review component so that we can identify and resolve systemwide issues internally. 

In the meantime, please follow these steps if you encounter any problems (local or suspected systemwide) in Alma or Primo VE.

STEP 1: Due diligence

Spend no more than an hour making sure the problem is not user error and is replicable:

• Log out and back in; try another browser; clear browser cache

• Check with your local colleagues and get someone else to reproduce the problem

• Check the Ex Libris Status page: https://status.exlibrisgroup.com/system_status

• Check the Ex Libris documentation: 

  • Ex Libris Knowledge Center for Alma or Primo VE topics.

  • Ex Libris LibGuides for Alma or Primo VE topics.

• Check the SILS Alma / Primo VE Known Issues page

STEP 2: Report the problem

First, follow your local procedure for reporting problems. This may include:

• Contact your supervisor

• Contact your local Implementation Coordinator

• Contact your local SILS group

Then, as appropriate, let Ex Libris and the SILS Teams know you’re having a problem:

• Report to Ex Libris through their support portal

  • Note: this requires a SalesForce account. Contact your Implementation Coordinator for details.

• If you think your issue is worth sharing widely, or you want consultation with the wider SILS teams, report it through existing mechanisms:

  • Contact your local Implementation Coordinator

  • Have local SILS reps check with their functional groups via Slack or email

STEP 3: Escalate as needed

If at any time you want extra attention on your issue, please contact the SILS Operations Center CDL Team: sils-sysops@ucop.edu. Don’t hesitate! Reasons could include but are not limited to:

• You found a showstopper of a problem

• You suspect this is a systemwide issue, or NZ issue

• You are not getting timely attention from Ex Libris

• You are getting poor or confusing communication from Ex Libris

• You just have a gut feeling that you need extra help

Other problems: 

I have a problem with Alma-VDX integrations:

• If you suspect a problem with the Alma-VDX integration (extra-consortial ILL), please report it to CDL (ResourceSharingHelp@cdlib.org) for triage, as the problem might be in the CDL adapter, or in the OCLC configuration, which is outside of the Ex Libris Alma / Primo VE service scope. 

• For VDX problems, you may also contact OCLC directly by using the “Report a Problem” link located on the left hand navigation bar in VDX to report any issues with VDX/ZPORTAL (aka “My ILL Requests). The link is available as long as VDX is online and the staff member is logged into VDX.

I have a licensed resource problem:

Follow your local campus practices for reporting problems with electronic resources. A new systemwide Electronic Resources Consultation subgroup composed of CDL and campus staff with electronic resource expertise has been created to consult on issues after Go-Live. Reporting directly to CDL may also be appropriate.

Please check the following links for more information:

• E-Resources Troubleshooting: Best Practices for Reporting Broken Links in CDL/SCP Records, etc. (SILS wiki)

• Report a Problem (CDL website, including CDL Helpline access) 

I want to request a new feature or enhancement, or, I want to talk about feature harmonization:

• Systemwide feature requests or enhancements should be brought up through the appropriate SILS Functional Group before going to Ex Libris. 

• Individual campus feature needs can be discussed in your local SILS group.

• Harmonization discussions should be handled in the appropriate SILS Functional Group.