• the Type_6_header label is missing in the Values where labels are to be configured for the Query to Patron Letter

• St Lawrence and Conestoga both noticed this issue with their letters: https://clo-collaboration-spaces.atlassian.net/wiki/x/FoB2Yw

• OCLS and St Lawrence have opened cases with Ex Libris

• September 27: issue seems to have been resolved for Conestoga

  • the following code is in the label for Type_6_subject = Regarding Your Article Request – Complete Form %reqId%

• Ex Libris Development has fixed your issue regarding the query_6 display issue and you should see the fix with the April 2025 release.

• They advised that as a workaround you can fill in the XSL. Instead of '@@Type_6_header@@' you can add any other text.

• Loyalist is was unable to search Seneca’s catalogue using their deep search configurations

• the local search profile P_NH_SY was not defined as a search slot in the view configuration for the view that Seneca College provided access to through the Primo VE Deep Search Configuration; the issue was resolved after Seneca is able to search Loyalist, the NZ OCLS has opened a case with Ex Libris adjusted the configurations for their view and search profile

• colleges were unable to send borrowing requests to Seneca

• a trailing space in the Partner information for Seneca, on the Parameters tab, the server information (na02.alma.exlibrisgroup.com) was causing issues with the delivery of ISO messages. Updating that field in the NZ and distributing the update resolved the issue.

• Fleming and Conestoga successfully tested sending borrowing requests and completing the request process with Seneca

Summary of issue from Ex Libris ticket opened by Loyalist College:

We are not part of a consortium, so we are only able to search our institution for titles in Primo.
We are using the Blank ILL form in Primo (testing stage), which sends the borrowing request to Alma.
When the "locate" function is run on the borrowing request in Alma, it does not give a warning message that it is owned by the institution.
When a borrowing request is created manually in Alma, and the "locate" function is run, it does provide a warning message that the title is owned by the institution.

We have two "sending borrowing requests rules" - 1. Do not send request automatically - no input parameters, output parameter = False, and 2. Do not send if owned by institution - input parameters "Self-ownership = True, output parameter = False.

Ex Libris Support resolution of the ticket:

Our development team has confirmed that Alma is currently not designed to provide this functionality on the blank ILL form, so the next step is to pursue this as an enhancement.

We strongly recommend that you pursue this enhancement through the ELUNA Product Working Group enhancement voting process. On a periodic basis the ELUNA Alma Product Working Group does an open call for enhancement suggestions that are voted on by the ELUNA Alma user community and presented to Ex Libris Development. This is the best way to have your enhancement request heard. Please see the article linked below with common Q&A's regarding the IGeLU and ELUNA enhancement process.

Ex Libris has also made available sharing ideas directly with our product managers using the Ex Libris Idea Exchange website (http://ideas.exlibrisgroup.com ). We welcome you to sign in to the site and share your ideas with us . Additional information can find on the website’s FAQ.

Here is the article - https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Enhancement_Process_-_Common_QandA

• Loyalist College has added "view local resources" as a first step in their managing borrowing requests workflow to address this issue

• Colleges can address this partially through Display Logic Rules that hide specific resource types (see sections and by limiting the New_Discovery_Network search profile to physical materials (see sections ;

• However, some colleges have noticed that requests can still be placed if patrons access the resource from databases outside of Primo VE, through related resources link, bypassing the DLRs: https://clo-collaboration-spaces.atlassian.net/wiki/spaces/RSIP/pages/1369243679/Humber+-+Discussion+Page?focusedCommentId=1513291777; Page 1+ Study Group Session 86 (at approximately 41 minutes); Resource sharing appearing when clicking on "Check for fulltext" in EBSCO databases. These requests for electronic resources should be automatically cancelled in Alma (“cancelled by staff” status) and patrons will receive the Ful Cancel Request letter.

• DLRs that hide the RS Request Link based on Resource Type are based upon the "recordtype" tag in the Control section of the PNX record for a Primo result. The PNX pulls this information from a record's associated bibliographic information. When this is properly populated in a PNX record, you will see this resource type show up at the very top of a Primo page, right above the resources title (e.g. https://app.screencast.com/3JqKPjqEergnB). But this does rely on the PNX being able to pull information from a full bibliographic record. For Network-catalogued resources, as well as CDI records, this is not an issue. However, it can be a problem with OpenURL records.

When users find an article in a database which then redirects them to a Primo page, this redirection from an outside service/database is done using OpenURL protocol. The problem with that is there's no guarantee that the information sent in the OpenURL will contain all of the necessary information for your DLRs to work as expected. If the service/database sends an OpenURL without a proper resource type, there's no way for Primo (the PNX) to properly populate the recordtype tag, and so the DRL cannot be applied.

You can see this using the example URL: https://humber.primo.exlibrisgroup.com/discovery/openurl?institution=01OCLS_HUMB&vid=01OCLS_HUMB:HUMB&date=20240501&issue=2&isbn=&spage=75&title=Critical%20Education&atitle=Connecting%20the%20Dots%20Between%20Extreme%20Ideologies,%20%22Parent%20Choice,%22%20and%20Education%20Privatization%20in%20Alberta%20and%20Canada.&sid=EBSCO:Education%20Research%20Complete:177504579&volume=15&pages=75-83&issn=19204175&au=Ganshorn,%20Heather&genre=article&ID=doi:10.14288%2Fce.v15i2.186885

First, add &displayCTO=true to the end of the URL, and then load the page again. Once you do, you'll see the button to Display CTO. Clicking on this will open a new tab with the CTO information, which will include a PNX section. If you review this section in the above link, you'll see that the recordtype tag has "bibliographic" for a value, which does not match what's configured in the DLR. This means that the RS Request link will appear for this OpenURL-generated record.

Meanwhile, compare that to the same article but if it was discovered via Expanded Search Results when searching directly in Primo: https://humber.primo.exlibrisgroup.com/discovery/fulldisplay?docid=cdi_erudit_primary_1111308ar&context=PC&vid=01OCLS_HUMB:HUMB&lang=en&search_scope=MyInst_and_CI&adaptor=Primo%20Central&tab=Everything&query=any,contains,Connecting%20the%20Dots%20Between%20Extreme%20Ideologies,%20%22Parent%20Choice,%22%20and%20Education%20Privatization%20in%20Alberta%20and%20Canada.&pcAvailability=true

When searched for in Primo, this instead pulls up the CDI record (instead of the OpenURL). Because it's CDI, the PNX can properly apply the record type and the DLR will work as designed. You can see this by adding &showPnx=true to the end of the URL for the CDI record.

In summary: this is an unfortunate situation that can arise when working with Primo records generated via OpenURLs. Primo and the Link Resolver can only work with the information provided in the OpenURL, so if that information is inadequate it can lead to this occasional request that "slip through the cracks."

Alma currently lacks a direct method to prevent Resource Sharing Requests on OpenURL-generated records.

• Ex Libris has recommended a workaround that involves creating a dummy GES/DLR to hide the RS request option for each college:

  View file
  name ResShar-OpenURLWorkaround_DRAFT_20240912.docx

• Colleges have also chosen to address this by redirecting the requests to their ILL departments to locate the resources with other partners, sending queries or direct e-mails to users, customizations of their RS Request Form, and using Libwizard form (subscription) or Google Forms (free) for ILL requests for these records: see Primo VE settings for Resource Sharing (RS) - best practices?; https://clo-collaboration-spaces.atlassian.net/wiki/x/AYAUWw ; Resource sharing appearing when clicking on "Check for fulltext" in EBSCO databases; Add a Libwizard ILL form to the Primo VE full record (can also add a Google Form instead of Libwizard)

• adding CSS code for in links to the customization package is another potential solution that could be explored