Primo is designed to sort the results list by one parameter only (relevancy, title etc.).
Currently, it is not possible to define a secondary sort. Thus records with the same ranking will appear in no particular order.
It would be beneficial to be able to configure a secondary and third sort options. For example, first sorting by Relevancy, secondary by Publishing Year and third by Title.

Primo (new UI) does not alert the user to sign in in order to save favorites. I suggest that when a user who has not logged in clicks the pushpin icon to save an item to Favorites, a modal appear to let them know they must sign in to save favorites, and give them an opportunity to do so.

It should be possible to hide DUE TIME in Primo, both in My Library Card and the item list. Many libraries do not offer loans by the hour and opening hours in Alma are not the same as the opening hours of the physical library. Therefore displaying the due time in Primo is often just noise.

See attached screenshots.

For the Digitization Request, Hold and Booking Request, and Purchase Request forms, the Alma mapping tables (under GetIt Configuration) define the fields that are displayed to users (Yes = viewable to users, No = not viewable to users).

We would like to have the possibility to configure mandatory fields if we want the user to specify a field in the form (as it is already the case with a check box in the Resource Sharing Request form).

Currently the Review content type in Primo / Primo Central seems to contain both Book Reviews such as
http://shu-primo.hosted.exlibrisgroup.com/44SHUVU1:defaultscope:TNsciversesciencedirectelsevierS0261-5177(06)00203-2

and Review Articles such as
http://shu-primo.hosted.exlibrisgroup.com/44SHUVU1:defaultscope:TN_proquest1373464971

It would be better if these were in separate content types.

Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.

It would be very useful if upon clicking on the unpin icon in the favorites screen, Primo will display a warning message stating that the user is about to delete the marked record/s.
Currently, clicking willingly or inadvertently on the unpin icon will immediately and irreversibly delete the record/s.

Resource types used in Primo Central are limited to 23 (book, article, journal, image...) [See pdf "Primo Central Index Resource Types" in the Documentation Center].

For digitized journal issues, the type in use is 'journal'. Archive collections like HathiTrust may contain tens of thousands of digitized journal issues; institutional repositories may also contain complete issues… This is finally confusing for end-users for who see issues labelled as journals and for whom filtering by resource type has become useless.

Adding a 24th type 'Issue' for this material would be welcome! ‘Journal’ would thus only remain for real journal records.

At this moment, the sort option “Date oldest” displays the records without a date on top of the results list. This is confusing and not relevant for users; when there are several records without a Creation Date they probably conclude that sorting on date oldest doesn’t work. Our request is to display the records without a date always at the bottom of the results list when a sort option on date is used (thus as well for date oldest as for date newest)

A version control system for back office configuration tables, pipes, normalization rules etc.
For files like Custom HTML, CSS, JS, PDS etc. we can manage change history and revert to older versions by using version control systems like Git, Subversion etc. For configuration managed via the web back office and database this is not possible, but it is a vital feature of professional system management. This will become more important in a full SaaS environment.

The FRBR Dedup Test utility is currently hidden in Discovery configuration (Primo VE). The team members who need to use this functionality are cataloguers so they can see what edits might be needed to troubleshoot issues preventing or causing unexpected FRBR/deduplication.

Adding it to the Resources menu in Alma is an option, another might be for cataloguers to be able to trigger it when comparing records in the metadata editor.

With a lot of online retail sites, users are able to choose how many search hits they see per page.

Would this be a helpful addition to Primo?

After all, since the new UI was introduced, the subject of infinite-scrolling vs paging has been contentious amongst Ex Libris customers. It has already led to the addition of the 'Next Page' widget.

Allowing users to choose how many hits they would like to see might take a lot of the debate from us, and put the decision directly into the hands of the end user.

It would be most helpful if a 'Session Timeout' warning could be displayed a certain amout of time before the session actually ends. Included in the warning could be the options to 'keep me logged in' or 'log out now'.

I'd like to see a way to organize my Save Query searches in Primo when I'm signed into my account.

Prior to our go live date, I'm doing a lot of test searches in Primo to analyze results so we can tweak it for the best results. Having the ability to save different searches and variations of them in folders would be a great option, both for us and for our students when we complete our rollover before the Fall semester.

We 'd like the possibility to use translations in OTB Display fields, not only in local fields.
Use case: we want to use a code for contributors & creators ($4), rather than tag Relator term ($e) and use the translation functionality to display this role in the language of the interface.