Second round Primo Enhancements 21-22

Ability to search My Favorites (VE/BO)

(VE/BO)

We need a way for a user to search their list of Favorites. PROBLEM: When a user has many Favorites and they need to find a single one they have in mind, there is no way to search their list. For example, a user may need to export one of their Favorites to EndNote. If they have a list of 150 Favorites, there is no way to do keyword searching to find that Favorite. Some users try to use Control+F to find the Favorite, but because the page loads 10 at a time, it will not find the favorite that is beyond the tenth in the list. 

A user has 200 saved favorites. They remember they saved an item in the past with the word "dogs" in the title but they don't remember anything else about it. They go to their Favorites and use Control+F to search "dogs" and get zero hits and think the system is not working, or their memory is failing, when in fact the title is in their list but is number #197. 

Users need to find items in their Favorite list to perform certain actions, such as send to EndNote, or navigate to Get It so they can place a request. 

Prevent Autocomplete suggestions from non-activated sources in CDI (VE/BO)

(VE/BO)

In Primo you can activate autocomplete to get suggestions for search queries based on what the end user begins to type in the search box, which is a useful feature for the end user. However, the suggestions from the central index are currently from the entire index and not only the sources the institution has activated. This means that the end user will get suggestions that gives zero results. We would like there to be a configuration option so that the site can choose for the suggestions to be based only on activated sources in CDI for the given institution. Also added to Idea Exchange: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/39435676-limit-autocomplete-suggestions-from-pci-cdi-to-act

Collection Discovery usage in Primo Analytics (VE/BO)

(VE/BO)

Currently, Analytics possibilities for "Collection Discovery" are rather limited. With action "Display a Collection", you can for example see how many times your collections (all together) have been displayed, added to favorites... in a period of time, but you cannot see which collections are the most and the less successful, what materials should maybe be more promoted, which collection should maybe be removed because its content is maybe of too little interest, which collections are added to favorites, etc. Therefore, we would like Collection IDs and Collection Names to be transferred to Primo Analytics. Additionally, if this could also be done for collection items (MMS ID and Title), this would be very useful too!

Expand-collapse functionality in the Full Display's Details section (VE/BO)

(VE/BO)

Bibliographic records often contain fields with lengthy content. E.g. Table of contents (505); Notes (520). This can make the Full Display very long. While the data in these fields are important, they are not necessarily helpful to always show them to every single user. Options to hide/expand fields in the Details section should be available with links like "show table of contents"; "show full description". Institutions should be able to specify how long the field is before collapsed appearance/link applies.
These links would also need to be captured in Primo analytics.

It would improve usability if long fields could be collapsed in the full record view with a link to "show full record", or links like "show table of contents"; "show full description".
Institutions should be able to specify how long the field is before collapsed appearance/link applies. If the fields were always collapsed, then the user might click it only to read a single line of text.
Optionally some institutions might choose to designate which fields (short and long) might be hidden until the user chooses to "Read more" rather than apply this only to long fields. These might be fields that are typically less relevant to all users, but important for some.
These link options would also need to be captured in Primo analytics. 

Improved user experience
See also the Idea Exchange:

1. https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/34665802-add-show-more-show-less-options

2. https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/43041189-let-patrons-collapse-elements-of-the-full-title-di

Better UX for placing requests (VE/BO)

(VE/BO)

Our patrons struggle with different aspects of the requesting workflow. 1) When a book is available on the shelf in open stacks, our on shelf request policies do not allow pickup locations anywhere, but are restricted to different library or campus. This limits the pickup locations that are offered for selection, but there is no explanation for the user as to why they are limited. In our older discovery system there was a pop-up note informing the patrons that they should fetch this item in the open stacks themselves. We'd like to show such a note again (by form or pop-up). This note should appear only when the item is not on loan, after a user clicks on the request option link. The existing possibilities via labels do not meet this request as they appear on all hold request forms regardless of the on shelf request policy. 2) When a book can only be requested to the reading room of the owning library, the interface skips a step and pre-selects this as the pickup location. The intention may be good (save the patron some clicks), but the result is very confusing because it is inconsistent with the usual steps and the patron places a request  without understanding that a pickup location was assigned automatically. 3) The choice for home delivery needs to be parallel to pickup location. The two are mutually exclusive. 

This has two annoying aspects for our patrons: a) in the milder case, it only costs them time, because they pick another pickup library and then have to wait for the book to arrive there. b) it can also cost them money that they could save: we know of cases where patrons did a request to have a book sent home because the interface does not explicitly let them know that they can just fetch it from the shelf themselves.
Yes, the location is called "... open stacks", but not everybody understands what this means.
And we can't rename the location "... open stacks, fetch it yourself", because this is only true if the book is not on loan. 

Make the requesting workflow less confusing/frustrating for the patrons.

Better UX for changing number of titles per page (VE/BO)

(VE/BO)

It's good that we now can see more than 10 titles per page. But when switching from 10 to 25 or 50, a) the display should neither jump to the top of the page nor jump anywhere else in the list: when I switch from 10 to 50 titles, the titles that I see next have to be title 11 ff.; b) the display of the titles should not 'slide in' because the icons load later and need more space. This is not happening when the setting is 10 titles per page. c) Switching from 10 to 25/50 should also be possible at the top of the page, not only at the bottom. // Number of titles per page should be a setting in the patron's account. // Setting the default number of pages to at least 25 (rather 50) should be doable per view. 

Display item policy in item record (VE/BO)

(VE/BO)

It would be useful if item policy could be configured as a field to display in either the brief or full item display. Currently, the loanable indicator is defined by the fulfillment terms of use, which is dependent on users signing in in order for Primo to calculate the loan policy specifically for that user.  
Having the option to display the item policy from Alma as a field in Primo would be beneficial as this does not change dependent on the user type or fulfillment rules. 
It would also provide more information to users irrespective of whether they are able to sign into Primo (e.g. users not affiliated to the institution will be unable to sign in) and makes it clearer and easier for staff to explain to customers why a particular item can/cannot be borrowed.

Requesting Flexibility in Local Resource Type Configuration (VE)

(VE)

Local resource type configuration was much more flexible in Primo Back Office than it is in Primo VE. We are requesting a restoration of that flexibility under Primo VE via the following three components:

1. Remove the limit on number of locally defined resource types. Local resource types allow us to configure additional resource types for our users to discover and represent our holdings more accurately. However, we can only define a maximum of 20 local resource types. We request that the limit on number of locally defined resources be removed or substantially increased.

2. Ability to assign multiple resource type facets and/or pre-filters to a single record. Under Primo VE, we can assign only one resource type facet and/or pre-filter to a record, which is very limiting for resources that fall into multiple categories (conference proceedings on ebook, dissertations on audio CD, collections of archival materials that consist of images, etc.). We request the ability to assign multiple resource type facets and/or pre-filters to a single record, like we could in Primo Back Office. We want to be able to do this for both records with a local display resource type and those using an OTB display resource type. Our related idea exchange proposal is at

3. Ability to edit the OTB resource type rules in Primo VE in order to include or exclude certain types of records from said rules. For example, for certain textual integrating resources that users are likely to think of as books (such as some open textbooks), we use conditions based on the presence of form/genre headings to add them to the OTB "book" display type in Primo Back Office. Some institutions would like to exclude monographic series from the OTB "book" rule. Others would like to be able to remove conditions related to 007, since these often refer to accompanying material. Providing flexibility in this way will allow institutions to categorize materials to meet the needs of their local users. Our related idea exchange proposal is at

For example, for certain textual integrating resources that users are likely to think of as books (such as some open textbooks), we use conditions based on the presence of form/genre headings to add them to the OTB "book" display type in Primo BO. Some institutions would like to exclude monographic series from the OTB "book" rule. Others would like to be able to remove conditions related to 007, since these often refer to accompanying material.

Providing flexibility in this way will allow institutions to categorize materials to meet the needs of their local users.

Extend lateral links for Relation, Is Part Of, and Uniform Title beyond local records (VE/BO)

(VE/BO)

Clickable lateral links for the ispartof, relation, and unititle fields were introduced in 2017, for NERS #5291 as part of "Enhanced Hypertext Linking". These new fields joined existing lateral links for creator, contributor, and subject. However, a key difference for the three newer fields is that they are only clickable lateral links for local records and while they are found displayed in CDI records, they are not clickable. The restriction of some lateral links to only local records causes confusion, with questions as to why some records are missing these links, which lead so helpfully into Advanced Search showing all records with this data in one cohesive results set. This is a disappointing inconsistency in our blended scope environment, especially when we see through our Primo Analytics data that lateral links are a popular feature, with thousands of clicks every week. An example use case are Relation fields for works in a series, where there may be local book records and book chapter records from CDI (example: Advances in Biochemical Engineering/Biotechnology). The outcome of this enhancement request would be for the Relation, Is Part Of, and Uniform Title lateral link fields to be consistently clickable in the full record display for all records, regardless of data source.

Enable patrons to check 'Keep me signed in' (VE/BO)

(VE/BO)

Our patrons are frustrated that they get logged out after a relatively short time.  It is quite a common feature to be able to check "Keep me signed in". In Nili Natan wrote in 2017 "We examine the option for providing 'keep me logged in' in primo." This should also work when the patron's authentification runs via an external service.

Patron feedback via twitter.
Being able to stay logged in on your private computer is a standard feature these days. 

Filter Resource Type by Magazines in Primo (VE/BO)

(VE/BO)

We would like the ability to distinguish between journal and magazine article/resource type when searching in Primo. We would like for our users to be able to easily identify or search for just magazine articles.  Being able to search by magazine resource type would be advantageous to all of our students. This option is available in Ebsco searches, so it seems like this could feasibly be implemented in Primo. 

Being able to filter resource type by magazine would allow users to more easily identify and search directly for magazine articles. Currently, magazines are grouped in "articles" which can be confusing particularly if journal and peer reviewed articles appear at top of search results.

Our users are community college students with varying levels of information needs. Users could be completing advanced coursework, basic skills coursework, or students could be English language learners. In some of these cases, journals are not appropriate or relevant for the assignment or user's need. This feature would not just serve community college students, but students in 4-year universities, as well. I've seen this request in Idea Exchange, so I also know that other libraries would like to see this feature become a possibility.

Add A-Z to Database Search (VE)

(VE)

Primo VE does not have an A-Z in Database Search.  This is a parity issue, as this feature is available in Primo managed via Back Office. Ex Libris has stated that this is a design decision because they believe users see an A-Z as outdated.  This opinion is not reflected in evidence in Primo Analytics, with up to 3,300 clicks per month.

Add the "Library" index in the advanced search (VE/BO)

(VE/BO)

"Library" is only available as a facet. It would be useful if "Library" could be also available in the advanced search, like language or resource type.  This type of research is used more than one would think and our patrons regularly ask why it is not possible to limit the results directly at the library level, using this search mode.
In addition, this would limit the side effects of the FRRBisation process (only libraries that have an item of the preferred record appear in the Library facet).

Add filter for "Available Now" (i.e. not checked out etc.) to Availability facet (VE)

(VE)

The Availability facet in Primo currently includes options to limit by "Available online" and "Held by library". It would be helpful if these options could be further refined to enable filtering to materials that are actually currently fully available/accessible -- for example, not checked out to another user or in another out-of-library processing status. This functionality can be found in other library search tools – for example, Overdrive includes an "Available now" filter.
Expected Outcome: Users would be able to further narrow "held by library" results to focus in on those materials that are not in a checked out or other unavailable status.

Researchers working on tight deadlines who need ASAP access to materials are helped by the ability to filter to "Available online" but stymied by "Held by library" results that include physical materials that are checked out or otherwise not available.

Users often want materials that are most immediately available to them. This need is partly met by faceting to content that is "Available online." It would be more fully met by being able to filter by facet to non-online materials that are held within the library that are available for loan (i.e. not checked out or otherwise out of circulation). Users are frustrated when they try to narrow their results to available materials when they find those materials are in fact checked out and not immediately available.

Add barcode search to Primo (VE/BO)

(VE/BO)

It would be useful to be able to search by item barcode within Primo. This would enable our users to locate specific physical items on the shelves more easily. Also, our student-facing staff, not all of whom are Alma users, would find it helpful to be able to search for items by barcode in Primo. This functionality would improve workflow for staff when they need to search a record in Primo without having to navigate out of the items screen in Alma to retrieve the OCLC number, the MMSID or the ISBN, or to pull up the record in Primo when the book is in-hand, without needing to key in the title or ISBN. The barcode is stored at the item level in Alma, where it should be, and is therefore not available for search by any current mechanism for search on bibliographic or holdings data. We would like an enhancement to Alma discovery and publishing which would add the item barcode to the data available to Primo for return of results. We understand that colleagues elsewhere are also keen to see a barcode search functionality added to Primo ( ).

Ability to specify which 856 (MARC) fields display in Links service (VE)

(VE)

In Primo Back Office (BO), it is possible to use normalization rules to specify which 856 MARC fields display in the "Links" section of the Primo full record view. It is crucial to user experience to have a similar functionality in Primo VE to customize which 856 links to display, based on regexp (regular expressions) and 856 first and second indicators and subfields.

An overwhelming variety of links are added to 856s for both physical and electronic bibliographic records: the resource itself, other versions of the resource, finding aids for archival collections, TOCs, cover images, summaries, reviews, excerpts, etc. For electronic resources, despite provider neutral record guidelines, many institutions still add local proxied links to OCLC records. With the volume and variety of 856s in both print and electronic records, an all-or-nothing approach to displaying these links leaves only two unsatisfactory options: either displaying none of these links, or displaying a frustrating and overwhelming amount of potential links of varying relevance to users.
Institutions should be able to control the display of links based on regular expressions and 856 first and second indicators and subfields.

Unify Primo My Library Card display of loans/requests from all institutions in the network (VE/BO)

(VE/BO)

Describe the functionality being requested:
Improve the Primo My Library Card to display a merged, multi-institution view of all of a user's loans, and, a merged, multi-institution view of all requests, instead of the current behavior of separate displays of loans/requests from each owning institution in a network.
Technical Requirements:
Ideally, these unified lists would be sortable by title, current due date, loan/request status, and item's home institution. Loans and in-process requests would each be in their own list in a separate horizontal tab as they are now.

User Story:
In a consortial environment, users often do not know which institution in the network an item is from.  They place a request from the network and may not care whose copy they receive.  Especially for power users with many items, searching through each institution tab in their Library Card to find a particular item is frustrating to them and may lead to items not being returned/renewed on time because the information is not readily available. The current display of items borrowed also makes it impossible for users to renew items from different institutions at the same time.

Business reasons that reflect the community or how all customers would benefit:
In a consortial environment, Primo's My Library Card currently separates a user's loans and requests by Fulfillment Network (AFN) institution. It would be much easier for consortial users to manage their loans and requests if all items were displayed in a single merged list for loans and a single merged list for requests.
See related Idea Exchange with 627 votes:
 

Add "Starts With" Functionality to Call Number in the Advanced Search (VE/BO)

(VE/BO)

We'd like to have "starts with" functionality for the call number field in the advanced search in Primo. Currently, "starts with" advanced searches are only supported for titles.

It is helpful to patrons to be able to search for an entire call number subclass (e.g., PA) to find everything available in that range without going to the stacks. The availability of "starts with" for titles leads patrons to expect it for other searches, like call number.
Existing workarounds are not completely satisfactory:

• Using Alma Analytics is a workaround for staff, but it's not available to patrons.

• The "starts with" functionality works for call numbers in Browse, but Browse displays only the first 20 or so results.