Left Menu Right Menu

Systems Open Call
October 14, 2015, 1pm to 2pm

Upcoming testing of non-PDS authentication for Primo

Ex Libris has approached the Alliance about testing a new architecture for Primo authentication that does not rely on the PDS, but instead utilizes direct communication between SAML-based authentication platforms, such as Shibboleth and CAS, and Primo.
A phone meeting will take place on Thursday, October 15 between Wade Guidry and Keith Folsom on the Alliance side, and several people from Ex Libris. The purpose of the call is to plan the testing of this altered authentication mechanism in the University of Puget Sound Primo Standard Sandbox.
Information about the results of the conversation with Ex Libris, and subsequent testing, will be shared with the Alliance systems community via email (sys-discussion).
One question that arose in the open call was whether the new authentication architecture would continue to support the branching authentication (internal vs external users) present in many institutional Primo views. The answer is “yes”.
Comments about Alma October release?
It was noted that Alma had been updated recently with the October release. No questions or comments arose on the call for this topic.
Update on Primo Enhancement voting
Al Cornish provided an overview of this year’s Primo enhancement voting cycle, and next steps and expected schedule for development of the Alliance voting recommendation.
Al expects the working group to have a voting recommendation released on October 14 or 15, leaving institutions with plenty of time to complete their NERS voting by the NERS voting deadline of October 21.
In addition, a round-robin discussion took place, in which a few attendees from the meeting shared their institutional approaches to participating in Alliance internal voting. Some institutions choose to reach internal consensus via email, while other institutions hold face-to-face meetings with participating staff.
Ideas / thoughts about recent listserv activity around letters customization
Following up on a recent thread on the dd-community email list, the group briefly discussed the current state of letters customization. Those on the call expressed some interest in pursuing letters customization, but also expressed that they have not had the time to spend on the topic.
Taken from the aforementioned email thread on dd-community, The following link points to a document started by Lori Hilterbrand from Oregon State University. Through this document, institutions can share screenshots of their own letter customizations and settings.
The idea of organizing a training presentation on this topic for the next Summer meeting was also mentioned.
Other topics, as introduced:
  • Reporting on information gained during a recent Center of Excellence Network Zone meeting, Al Cornish reported that ExL is going to release a new functionality, “Refine Sets”, in the November release. This new functionality allows the creation of sets based on indexed metadata elements, which can then be filtered based on non-indexed fields using Drool statements.

  • Lesley Lowery, Western Washington University, and chair of the Normalization Rules working group, provided an update on the recent Normalization Rules proposed changes and testing cycle. All proposed changes, with the exception of adding newspapers to the Journals A to Z  list, will be moved into production shortly. One of the rule changes, related to publish dates in theses and dissertations, will go into production in modified form, based on testing feedback from institutions. Lesley reported that 50% of Alliance institutions provided normalization rule testing feedback. The Alliance Primo production environment is scheduled for renormalization and reindexing starting October 15, and will continue through October 19th. No Primo updates from Alma will be published during this time, until renormalization and reindexing is complete.

  • Wade followed up on past conversations about the impact of the User Schema Version 2, and its impact on the patron expiration timestamp of users loaded via the new schema. First reported by Reed College in SF 165005, the use of the V2 schema results in variability in the user expiration timestamp. The expiration day is set according to date specified in the loaded XML, but the expiration time currently varies, and is not controllable by the institution. This variability can impact material due dates, when the due date is shortened because of the patron expiration date. Ex Libris has noted in the SF case 165005 that the issue will be resolved in an upcoming Alma release within the next calendar quarter. Ex Libris does not explain how the issue will be addressed, but it is expected that, either through configuration of the load job, or through the XML itself, institutions will be able to exert control over the expiration time, as well as date.
Next Meeting:
Please note, the next Systems Open call will occur on Thursday, November 12 at 1pm, instead of the usual second Wednesday of the month. This change is being made due to November 11, Veterans’ Day, being a holiday at several institutions.