(Go-Live) Configuration of E-Resources/Discovery Settings in Alma (AEFG MVP 014)

Legend: not started IN PROGRESS STALLED decided

Status	decided
Scope	Go-Live
Description	Collaboration for Primo results of electronic-resources related configuration in Alma. This is in the Fulfillment area of Alma configuration and includes Display Logic Rules, General Electronic Services, and Direct Linking. Beyond systemwide recommendations (e.g., the change for Melvyl), many of these settings may be at campus discretion. Related to AEFG-MVP items 006 and 008.
Decision	AEFG is providing guidance and information in this page rather than a systemwide recommendation. AEFG recommends cross-functional discussion and coordination at the campus level involving relevant Discovery and Electronic Resources Management subject matter experts for configurations related to the items below in the Display Logic Rules, General Electronic Services, Direct Linking and other areas of Alma configuration for Primo functionality. AEFG recommends further testing and development of configuration settings and effects on Primo results post-go-live.
Owning group	AEFG + lcspagnolo [at] ucdavis.edu
Approver	PPC
Stakeholders	R = AEFG, CDL A = PPC C = Discovery FG, Fulfillment FG, CDL I = ICs, End-User Outreach
Decision-making process	AEFG discussion and comparison of already-Alma configuration; scope definition and consultation with Discovery and Fulfillment FGs via PPC; AEFG development of page and approval; PPC review with any additional input from other FGs; PPC approval; Distribution.
Priority	High
Due date	Jun 11, 2021

Recommendation

While a large part of the configuration in the Fulfillment area of Alma related to Discovery is under the purview of the Fulfillment and Discovery FGs, there are a few items that intersect with electronic resources management along the continuum of the electronic resources lifecycle. AEFG does not have any recommendations for harmonization at this time, but would like to call out particular areas of this configuration, and recommends that campus implementation teams thoroughly consult across functional areas depending on local roles and expertise. AEFG recommends additional testing of Display Logic Rules pertaining to specific resources after go-live.

DISPLAY LOGIC RULES

Out of scope for AEFG: configuration in the Fulfillment area such as hold requests and bookings; configuration for broad services in the Discovery area, such as those related to WorldCat.

AEFG recommends employing the rule to Hide the Purchase Request service in Alma at this time, unless otherwise configured by Already-Alma campuses as described below, [See: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/020Purchasing/020Creating_PO_Lines/070Patron_Purchase_Requests This service involves a particular workflow within Alma for reviewing and managing these requests. Current Alma campuses (D, R, SB) have not yet adopted this workflow and have other paths for purchase requests from patrons. Note: UCSC is using a combination of CSS and Display Logic Rules to only show the Purchase Request link if the item is a monograph without inventory. They are using a Display Logic Rule to indicate “Hide Service Purchase Request if exist GES=Not a Book”.

Ex Libris documents several examples of applying Display Logic Rules to cases in which a service page may be delivering full text from a particular resource (see https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/080Configuring_Delivery_Services_for_Primo_VE/Configuring_Discovery_Interface_Display_Logic_for_Primo_VE#Display_Logic_Rule_Examples-33266). . This is likely an area of post-go-live testing.

A Note about Alma Link Resolver Augmentation
It is possible to enhance the link resolver functionality for DOI, OAI, and PubMed through an Integration called Augmentation: documented on the Ex Libris site here: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/210Alma_Resolver_Augmentation This is in Alma under Configuration>General>Integration Profiles>Augmentation. After consultation with Alison Ray, it was confirmed that this area has been handled through the configuration done within the Implementation Coordinators group.

This Augmentation item surfaced in AEFG’s review of the Already-Alma settings and noting that UC Davis has some additional Display Logic Rules related to PubMed and Request. The necessary configuration for the consortial migration should be sufficiently covered via IC’s work.

GENERAL ELECTRONIC SERVICES

There are only a couple of items that AEFG would like to call out among these services.

Feedback Form/ Report a Problem: This is where a campus can set up a Report a Problem service to appear within the Get It and View It areas of Primo. Often this is integrated with a library ticketing system, but can also be implemented to go to an email address. See the AEFG Decision Page on Troubleshooting (008).

Ex Libris: https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/How_to_add_%22Report_a_Problem%22_link_for_the_GetIt_or_ViewIt_menu%3F

The ProQuest Dissertation Service is enabled at some of the already-Alma Campuses:

DIRECT LINKING
Most Already-Alma campuses have this turned off in their local instances. Direct linking enables a patron to go directly from a link to the target resource, bypassing the Primo View It intermediary page. At least one campus who did not enable this reported this working well for items the library had access to, but did not work as well when there was no access - the user would not get routed to the Primo page that contained links to appropriate services like ILL, etc.

See Ex Libris Idea Exchange item on this topic: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/10016226-failsafe-links-to-databases-if-when-direct-linking. AEFG has not yet determined the development outcome.

Reasoning

Following the Primo VE sessions in May, general understanding was established regarding the configuration areas of Alma that touched on electronic resources in some way. AEFG decided that the already-Alma campuses could provide insight into current configuration, and considerations for consortial settings. Several of the settings either have a wider scope, such as the phasing out of Melvyl-related settings, relate to Fulfillment or Discovery services and display more directly, or are up to local discretion.

Out of scope for AEFG: configuration in the Fulfillment area such as hold requests and bookings; configuration for broad services in the Discovery area, such as those related to WorldCat.

Background

For the Configuration pages for Display Logic Rules, General Electronic Services, and Direct Linking, AEFG consulted the current configuration of the Already-Alma Campuses as well as Ex Libris and peer consortia documentation.

Resources from Other Consortia:
CSU:
OpenURL, Proxy, and Discovery Interface Display Logic in the IZ:
General Electronic Services:

CARLI:
Display Logic Rules for Electronic Resources:

SUNY:
Link Resolver & General Electronic Services:

Action Log

Action/Point Person	Expected Completion Date	Notes	Status

Action/Point Person	Expected Completion Date	Notes	Status
Lisa S. raised to PPC as collaborative issue after Primo VE workshops.	May 21, 2021		Done
AEFG gathering configuration screenshots from Already-Alma campus members.	May 27, 2021	In AEFG Collaborations subfolder for this topic.	Done
Follow-Up at PPC	May 28, 2021	Determining that AEFG would focus on items related to e-resources management and not broader services (like Melvyl) or services out of functional scope (like citation linkers).	Done
Cross-FG collaboration/review/ discussion.			In progress
Finalize recommendations.			Done
AEFG approval	June 9, 2021		Done
PPC approval	June 11, 2021	Revisions noted to Display Logic Rules section to refine UCSC use of Purchase Request; and Blue Info Block on Augmentation sufficiently covered in ICs per Alison Ray.	Done
Distribution to ICs for campus review of local configuration during remainder of Test Environment availability.	June 11, 2021 - no later than AM June 14, 2021.		Pending