Related product I-Share

Alma/Primo VE Known Issues

Updated: September 9, 2024

General Alma Troubleshooting and Problem Reporting

expand / collapse all

We expected that the “Holdings Call Number” search would search only the data found in the Holdings records call number fields in the MARC 852 of the library’s Alma IZ. However, searches are presenting results in a library’s Primo VE where the matching call number data are not found in the Holdings records 852 field of the library’s IZ, but rather are found in the Holdings records of other I-Share libraries in the network.

Ex Libris reports "When records were held by multiple IZs, records with call numbers that did not start with the specified term were returned in search results." This issue is scheduled to be fixed in the November 2023 release on Nov. 5, 2023.

If a local I-Share library has full text access to an electronic title, Primo VE will not provide the I-Share request link for a user to request the physical copy of the title from an I-Share library, even when it displays information about physical copies at those libraries. This is not CARLI’s preferred behavior; we'd prefer that Primo VE provide the I-Share request link for the physical copy and I-Share libraries could choose to hide it using a Display Logic Rule. The current workaround for this issue is for library staff to place the request for the user in Alma for the physical copy at another I-Share library.

  • CARLI staff and the CARLI Resource Sharing Committee have completed testing a new feature released in August 2022 that will disable the Submit button on the I-Share Request Form if there is no item available to request.  A webinar about the options was held 12/6/2022; for the recording and more information, see Primo VE: I-Share Resource Sharing "Availability" Options

Users on Mac computers may have issues with hidden .DS_store files being added to their customization packages. These hidden .DS_store files will prevent successful upload of the customization package in Alma.

To zip and also remove the .DS_store files from a customization package on a Mac:

  • Open the Mac's Terminal application under Applications > Utilities.
  • Move to the parent directory of the folder that you want to compress. For example:
    cd /Users/<user name>/<parent folder>
  • Enter the following command to compress the file and remove any .DS_store files within:
    zip –r <target file>.zip <My_View> -x "*.DS_Store"

Your users may see a change in Primo VE request behavior, see the “Notice for library staff” section below.
No configuration changes need to be completed by your institution; CARLI staff have made the configuration changes described below.

Reported issue:
Following the February Alma/Primo VE update, there was an increase in patron I-Share requests being automatically cancelled, when copies of the title should have been available to request.

Background:
The problem was caused by a change to how the Primo VE Resource Sharing Request form is pre-populating the “Preferred Local Pickup Location” field:

  • If an institution has more than one pick-up location for patron requests, the default pickup location that is set in Alma was not always prepopulating the box on the form in Primo VE like it used to. Users were able to submit requests without this necessary information; these patron requests were automatically cancelled by Alma.
  • If an institution only has one Local Pickup Location, that pick-up location is correctly prepopulating the Preferred Local Pickup Location form as expected. These patron requests were not affected as they contained the correct pick-up location information.

Configuration changes:
As a workaround to this issue, CARLI staff have updated all Resource Sharing Request forms for all I-Share institutions to make the “Preferred Local Pickup Location” be a mandatory field.
This will prevent patrons from inadvertently submitting requests with this field blank.

We have ticket 06711072 open with Ex Libris for investigation into why the default pick-up location field no longer pre-populates with the default pick-up location. A fix anticipated by December 2022 was not effective; CARLI checked in with Ex Libris in April 2023.

Notice for library staff:
Due to the workaround in place, if an I-Share patron is choosing to pick up their requests at an I-Share library that is not their home library, they may now be prompted to also set a “Preferred Local Pickup Location” in the request form.

This may cause confusion as the “Preferred Local Pickup Location” field contains the list of circulation desks at their home institution, not at their desired pick-up institution.
However, selecting the “Preferred Local Pickup Location” at their home institution will not affect their request; the requested item will still be delivered to their chosen I-Share institution.

On the I-Share Request Form in Primo VE, the "Preferred Local Pickup Location" and "Preferred Pickup Institution" of the user's home library are displayed. If the user chooses a different Institution from the list, then the "Preferred Pickup Location" appears beneath the Institution for the user to choose the location at that other Institution. (originally posted 8/24/2020 on Fulfillment pages)

  • If the user chooses a different Institution, the "Preferred Local Pickup Location" field does continue to display above the Institution, but, the "Preferred Pickup Institution" field controls where the item will be sent.
  • At this time, we do not have a way to make the "Preferred Local Pickup Location" disappear if the user chooses a different Institution that is not the user's home Institution.  As such, you'll want to educate your users about how to use the request forms with this in mind.
  • This is the same for the "Resource Sharing Request" form used by staff in Alma to place a request on behalf of a patron.

Problem: Although signed-in Primo VE users can add tags to items, if a user clicks on the tag link on the Full Details page for an item or if they click the link for a tag on the tags list via the Tags link in the Links Menu, a search for the term will run but no results will be provided.

At this time, Ex Libris does not provide the tag functionality for consortial users. CARLI recommends libraries turn tags off/do not enable the tag function. Directions on how to turn the tag function off can be found on the following page: Tags in Primo VE.

Problem: Primo VE-generated APA citations are omitting the author’s first initial for records with single authors/creators and the first initial of the first author for records with multiple authors/creators. For example,
instead of:
Payne, S. G., Sorkin, D. J., & Tortorice, J. S. (2004). What history tells George L. Mosse and the culture of modern Europe . University of Wisconsin Press.
the generated citation is:
Payne, Sorkin, D. J., & Tortorice, J. S. (2004). What history tells George L. Mosse and the culture of modern Europe . University of Wisconsin Press.

CARLI has opened Case 06044300 with Ex Libris. Ex Libris is aware of this problem, and it is affecting all customers. This issue dependent on citation style language (CSL) files which are controlled by a third party. Ex Libris staff are working with those developers to get this addressed.

Workaround: Ex Libris Primo Product Management has shared that in the meantime, several customers are using apa-cv (https://github.com/citation-style-language/styles/blob/master/apa-cv.csl) in place of apa I-Share libraries can manually adjust the citation format being used in Alma Configuration > Discovery > Other > Citation Styles.  For more information on how to adjust or add new citation styles, see the ExL documentation on Managing Citation Styles for Primo VE, and the May 12, 2022 CARLI Alma Primo VE Office Hours "Lab Reports" where there was a session on citations.

Ex Libris fixed this issue with the November 2023 software release on Nov. 5, 2023.  Ex Libris recommends that customers who used the workaround listed above switch back to apa.csl now that the bug has been fixed.

Problem: In the Citation action in Primo VE, the default label says "APA (6th edition)" but the version is actually the 7th edition of APA.

Primo VE is designed to always use the most recent edition of APA that is available, but the label itself is not updated automatically.  I-Share libraries can correct this display label by changing it from APA (6th edition) to APA (7th edition) in: Alma Configuration > Discovery > Other > Citation Styles > Edit "apa" and change the Label from "APA (6th edition)" to "APA (7th edition)".

We have also learned that this is a problem for all Citations provided in out-of-the-box Primo VE. The most recent version of the citation format is always being used by default, but the label is not automatically updated to reflect the current edition name.  The label must be changed manually in Alma Configuration > Discovery > Other > Citation Styles.  For more information on how to adjust these labels or add new citation styles, see the May 12, 2022 CARLI Alma Primo VE Office Hours "Lab Reports" where there was a session on citations!

Problem: When a user logs into My Library Card through Primo VE, not all the user's loans or requests from all I-Share libraries are listed on one page. The user must click through each institution name to see the loans and requests from that specific library. Many users would like to see all their loans or requests--no matter which institution they are from--listed on one page.

Currently, there is no way to customize the My Library Card to change this behavior; the default is the only option for displaying loans and requests. There is an Ex Libris Idea Exchange topic that requests better design of the My Library Card page, specifically so users can see all their loans/requests from all institutions one one page. Vote and comment on this Idea Exchange topic at: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/40091278-library-card-page

 As a stopgap measure, please also consider voting for and commenting on this Idea Exchange enhancement requesting that the "Has Activity" toggle on the Institutions list be set as the default.

The report from the Fulfillment Job "Loans - Overdue and Lost Item" does not accurately report the number of "Loans Which Notification Was Sent For - by Profile" for Lost profiles.

The notifications do generate/send, but the job report does not include the numbers; even when users are sent a notification letter for a lost profile, the report always lists the "Number succeeded" and the "Number failed" as zero for the lost profiles.

Ex Libris determined in support cases 00976173 and 05303797 that the workaround will need to remain in place for this issue, as it is not a priority for development (10/2022).

Workaround:

Staff can review the area of the report for "Change to Lost - by Profile" and review the list of succeeded or failed status changes. From those lists, staff can review the associated user's Attachments tab to double-check that the letter was sent to the user.

When library staff run any job that affects Purchase Order Lines (POLs), including:

  • Update PO Lines Workflow,
  • Update PO Lines transactions,
  • Update PO Lines Information – Advanced,
  • Update PO Lines Information,
  • Change PO Lines Status

if the set that is used for the job was created prior to 3/7/2021, the job will add ALL POLs from your Alma Acquisitions to the set, rather than only the POLs actually defined in the set you created.

Be sure to pay attention to the number of POLs that will be updated by the job, as stated in the warning given by the job before you submit it. If the job indicates that it will updated a much higher than anticipated number of line items, it is a sign that your job may be affected by this issue. 

Workaround:

Prior to running any of the jobs listed above, create a new set containing the POLs (do not reuse any set you had previously created before 3/7/2021).

Ex Libris hopes to have a fix in place for the problem by May 2021.

CARLI recommends deleting your old sets of POLs to ensure you are not accidentily running these jobs on the incorrect purchase order lines.

Primo VE may display the I-Share request link inappropriately in the Get It section even when there are no other holdings at any other I-Share institution and no "Get It at Other Institutions" section. 

In the August 2022 release, new functionality has been added to Alma that CARLI and the Resource Sharing Committee have tested to remediate this situation. A webinar about the new options was held 12/6/2022; for the recording and more information, see Primo VE: I-Share Resource Sharing "Availability" Options.

The Primo VE Local Request form is showing the institution and library even if the hold shelf is not enabled for the circulation desk.

Background:

From what we understand thus far, turning off all circulation desk hold shelves should fully remove an institution from the list of pick-up institutions/locations visible to the user in Primo VE.

  • We're finding that the behavior is different in the Resource Sharing Request form vs. the Local Request form.
    • The Resource Sharing Request form is behaving as we'd anticipate and not showing the institution or library if the circulation desk does not have a hold shelf.
    • The Local Request form is instead showing the institution and library even if the hold shelf is not enabled for the circulation desk.

CARLI filed Ex Libris support Case 00935915; the development is pending a roadmap plan https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/41579965-allow-fulfillment-network-member-afn-to-lend-res

In Alma, if an institution adds an identifier to the Configuration> User Management> Collaborative Networks> Searchable Identifiers table, then, their patrons can no longer be searched at other I-Share/AFN member institutions by name or by email, even if the user's name/email is unique. Occasionally, library staff have limited the searchable identifiers in a way that prevents searching by barcode or IID as well.

What to do: If you find another I-Share institution's users are not searchable by name or email (when unique), by barcode, or by IID, please email and we can review the configuration and reach out to the institution. 

CARLI has filed Ex Libris support Case 00926943 about name/email identifiers; Ex Libris confirmed this behavior is expected.

The Alma User Purge job is not AFN-aware; it will allow the deletion of a user record from the user's home institution's IZ even when the user has active transactions at another AFN institution.

These "orphaned" linked user records are confusing for both users and library staff. Examples of the confusion we've encountered thus far:

  • If the user's home institution performs a purge and then re-loads records, the orphaned linked user records in the other AFN member institutions do not re-connect to the new version of the user's home record. The user is then confused why they cannot see their AFN-charged material on their account.
  • If the item's home institution contacts the user, the user will often contact their home institution for assistance. The user's home institution cannot see the user's record in their own IZ anymore so they are confused.
  • If the item's home institution is unable to contact the user, they often contact the user's home institution for assistance. The user's home institution cannot see the user's record in their own IZ anymore so they are confused.

CARLI has filed Ex Libris support Case 00933368

Each institution has a daily scheduled job, Publish bibliographic record (DataSync) to OCLC, which sends copies of added, updated, and deleted records to OCLC via secure FTP. Deleted records are sent with the Leader/05 value of "d". OCLC reports that records must include both the correct leader value and a 994 $b containing the OCLC library symbol. I-Share libraries have reported that deletions are not being processed on OCLC's end.

Current Workarounds:

  • Manually delete holdings from OCLC via Connexion or Record Manager when deleting records from Alma.
  • Generate lists of deleted OCLC numbers with their OCLC numbers from Analytics or the Alma Deleted Repository, then process those lists through Connexion client's batch processing or Record Manager's delete holdings function.
  • Change the publication status of the record prior to deletion (Tools > Set Management Tags > Publish to OCLC > Don't Publish). A library would have to wait at least a day before deleting records modified in this way.

Some I-Share libraries are currently closed to the public for in-person access (Library A), but are willing to allow another I-Share library's patrons (Library B) to request their materials for pick-up at another I-Share library (Library B or Library C).

  • If Library A is allowing local requesting of their own materials for their own Library A patrons, it is not possible to prevent Library A from showing in PrimoVE as a pick-up location for other I-Share libraries' patrons.
    • If Library A is NOT allowing local requesting of their own materials for their own Library A patrons, turning off all circ desk hold shelves will fully remove an institution from the list of pick-up locations visible in Primo VE.
  • Ex Libris Support has confirmed there is currently no way to turn prevent Library A from being allowed as a pick-up location.

Please vote and comment on this Idea Exchange for this topic; development is pending!

After running the "Change Bulk Due Date" job for all I-Share libraries (for all I-Share patrons, and for local patrons at the discretion of the library) as part of the Proposal on Alma Bulk Due Date Extension Approved by CARLI Board of Directors, the CARLI Office has received a few reports from library staff that some eligible transactions may not have had their due dates updated.

Current workarounds:

  • Contact with information about the patron and the items that were not renewed. We can evaluate whether renewal was anticipated based on the Bulk Due Date change jobs that we ran as part of the project, and rerun the jobs as needed.

Possible cause, #1:
Alma does not support opening multiple copies of the User Details screen. When the User Details screen is open in one browser tab or window, and another tab contains either the User Details tab or the Register New User screen, clicking save on the edited or newly created user will also save changes over the user in the other tab. CARLI staff have observed this activity in cases where a library staff member opened their own user details screen for reference while also creating or editing a new user in another tab.

CARLI has opened Ex Libris Case 00893658.

Current workarounds:

  • Library staff should create a screen capture or a reference sheet of user details that are needed.
  • If staff need to have multiple screens of the same type open, use different browsers for additional instances, or use a browser's privacy or "in cognito" modes to keep the sessions separate.

Possible cause, #2:
When a library does a SIS synchronization, Alma is matching only on the user's primary ID; it is not taking into consideration if the user is a "linked user" record or not. As such, an I-Share user's linked user record saved to another IZ may be overwritten with a local patron's information if their primary ID is a match. The scope of this issue is minimal, as it only affects linked user records that were migrated from Voyager with an unprefixed Primary ID, where the format matches the primary ID used by the home institution performing the SIS updates for their local patrons.

Background:

  • When Alma imports a new linked user record for an I-Share patron, the linked user record imported in Alma is assigned a random 15 digit number, where the last 4 digits are the item's home IZ's Ex Libris code. This 15 digit number that ends with the Ex Libris code is unlikely to have a match.
  • The issue is that I-Share patron stub records that were migrated from Voyager, sometimes migrated with their Primary ID set as their IID from their home institution, which may have been an unprefixed number. As I-Share libraries began running SIS synchronizations, sometimes that un-prefixed primary ID in the linked user record could match to a local patron's Primary ID.

CARLI has opened Ex Libris Case 00936354.

Primo VE will allow a patron to place an I-Share request for a title, even if no I-Share library can fulfill that request; Alma then updates the request to "Canceled" and notifies the requesting patron via email. (originally posted on Fulfillment pages 7/15/2020)

  • CARLI staff and the CARLI Resource Sharing Committee have completed testing a new feature released in August 2022 that will disable the Submit button on the I-Share Request Form if there is no item available to request.  A webinar about the options is scheduled for 12/6/2022: CARLI Webinar- Improvements in I-Share Requesting- Fixing frustrations

In Alma, when entering or scanning a barcode results in an incomplete barcode number, items at other institutions may be charged to a patron.

  • Some I-Share institutions use sequential barcodes that are unique within the institution only.
  • The Automated Fulfillment Network is able to identify any item across the network by its barcode.
  • If a library scans a barcode, but the scan misses some of the digits--e.g., only the numbers after the library's prefix, or only the last four digits--if the entered number matches an item barcode in the network, that item will be charged.
  • Current Workarounds:
    • When scanning items in the Manage Patron Services screen, if a different item is charged than the item in hand, get the barcode from the screen, and discharge it on the return items screen. Contact the library whose barcode it was errantly scanned to let them know the item is now "in transit" back to their institution.
    • Consider asking systems staff to program barcode scanners to not automatically include a carriage return. Have circulation staff visually compare the barcode entered to the barcode scanned before clicking the OK button.
  • Workflow:
    • Contact the item's home library to inform them of the mis-scan.

Unfortunately, when a patron whose home library is not yours requests to pick up material from another I-Share library at your institution, Alma does not display which institution they belong to.

  • We have an Idea Exchange enhancement request for this issue, but it needs more support before it may be considered for development:
    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/40297720-afn-fulfillment-network-add-patron-s-home-institu
    • Any library staff member can set up an Idea Exchange account to submit ideas for development, vote on ideas already submitted, and add comments to give an idea more weight. Please consider creating an account and voting/commenting on this issue.
  • Workflows:
    • The patron should receive an "on hold" letter from the item's library when you scan it in for hold. Then when the patron arrives to check out the item, they should have their ID with them to let you know which institution they belong to.
      • Steps for checking out material to a patron from another I-Share library are on the How To: Fulfillment in Alma page under the section "How to bring up a patron record and check items out."
    • If you're doing contact-less pickup and need to check the item out to the patron before they arrive, unfortunately, the only way to know which patron has requested the item is to contact the item's library.
      • The item's home library can search for the item by barcode, and then select the "Requests" indicator to see the requesting patron's information.
      • The item's home library should provide your library with the patron's affiliation, so that you, as the pick-up library can complete the charge transaction.
        Screenshot shows an example item retrieved by barcode in the item's home library using a Physical Items search. The field "Requests" is highlighted to show that is what to select for the item's home library to locate the requesting patron.

When a user from one I-Share institution borrows or requests material from another I-Share institution, Alma copies some details in the user record from the patron's home library to the other I-Share library. That copy is called a "linked user record"; in Voyager, we called it a "stub."

  • The linked user record is "refreshed" with a new copy from the patron's home institution when specific scenarios occur:
    • Library staff to do a Fulfillment> Manage Patron Services> Find user in other institution re-import/re-save of the patron's home record.
    • If the user places another request for another item from the institution where the linked user record is saved.
    • In Primo VE, if the user selects the institution from the list of institutions in their account, their linked user record will be refreshed in Alma at that institution. (New with March 2021 release)
  • At the beginning of each month, the CARLI office runs a job to update only the expiration date in the linked user records.
    • The job run by the CARLI Office does not update any other data from the patron's home record, only the expiration date.
  • Please vote on this Idea Exchange for this topic.
  • Materials to be returned to Robert Morris University (RMC) can be returned to Roosevelt University (ROU).
  • Materials to be returned to MacMurray College (MMC) can be returned to the Illinois State Library (ISL).
  • Materials to be returned to Lincoln Christian University (LCC) can be returned to the Illinois State Library (ISL).