Primo
Your feedback matters to us. Help us improve Primo by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
1158 results found
-
Make Primo Analytics network folder available for consortia members
Make the Primo Analytics network folder available to consortia members' Primo Analytics catalogs the way it is for Alma Analytics. This would make it possible to share Primo Analytics reports to all members without adding the report to the shared community folder or copying the report to each institutions' local folder.
4 votes -
Personal name (600/610/611) should be included in Browse subject of Primo VE
Currently Primo VE does not search 600/610/611 as part of a Browse subject search. That means that a patron cannot view or browse through all of the subject headings for books about “Luther, Martin” or “Morrison, Toni.” The 600/610/611 fields are searchable in Alma as “names” but not browsable in Primo VE as subjects. Leaving out personal names goes against the common expectation in library systems to find all subjects including those that describe people, companies, etc. A similar entry exists in the Alma part of Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/35782486-browse-by-subject-headings-to-include-600-610-611
59 votes -
Local Resource Type on IZ-Level with local extensions
I would welcome a possibility to create local resource types on Institutional Zone level using local extensions, for example: MARC 980 $a. In other words: change the resource type to a certain value when a string in 980 $a is available.
By now it is only possible to create local resource types when all necessary data is available in the network zone - local extensions are not available there as they represent extra data for local needs only.
3 votes -
Show exact number of results when browsing instead of 20+
When browsing subjects in Primo, if a result has more than 20 results attached to a single subject entry, that subject displays "20+ records" instead of a specific number, which is what Primo shows for any total less than 20. This happens because Primo uses the Alma browse functionality, but this is not as informative to users as it should be. Instead, users have to click the heading before they can see the exact count of associated records.
11 votes -
Alerts in a consortium with NZ: send alerts for records added to the inventory of the institution of the user
The alert functionality is not really functional in a library network with a Network Zone. Users get an alert when a new bibliographic record is created in the Network Zone, but most users don't care about new acquisitions in other institutions. What they want is to be alerted on new acquisitions in their own institution. This means: to get an alert when a new bibrecord is added to the inventory of of their IZ (not only by creating a new record but also by adding a holding or portfolio to an existing record in the NZ).
Our request is to…98 votes -
Add Popular search category - User Statistical Category
Primo Analytics currently offers Zero search (daily, based on user group) and popular serach Hisotry (monthly, based on user group)
I want to be able to extract the User Statistical Category required for analysis, if not the entire data.
3 votes -
Sorting of collection page witch contains only subcollections
When in Alma a collection page contains only subcollections, in Primo, default sort will be "Relevance", with option to change to title.
If the collection page contains only Titles default sort will be "Sort titles by" value set in the Discovery tab of the Collection Resource Editor, with options to change to any sort that is available in the search results page results.It would be very desirable if the sorting setting in Alma would take effect for a collection page containing only subcollections, so that you could sort the subcollections not only by relevance but also alphabetically.
32 votes -
Support the use of wildcards within phrase searches
At present, the use of wildcards within a phrase search is not supported in CDI. This functionality is supported when searching local records only but does not work when searching CDI or using a blended scope. Since the goal of discovery is to provide a single point of access to local and remote collections, it follows that both indexes should support the same search functionality and operators.
1 vote -
Allow us to collapse like locations for a library using mapping table like classic
In classic Primo we would able to collapse like locations for a library using a mapping table. For example we have some very large buildings and for logistics we have locations like Stacks 3rd floor and Stacks 4th floor. In the facets it would be nice to just have Stacks be grouped all together. This also allows us to create custom pre-filter for our libguides.
47 votes -
Add due dates to Email Record Template
Under the Loans section in Library Card, users can export the list of their loans via email. The email contains names of loans, but not their due dates.
Could due dates be added to the Records Email Template, so the users can see their loans due date in the email export?
Petra
3 votes -
Improve the search for non-preferred terms
The search of a non-preferred term works correctly with standard indexes.
Non-preferred terms are currently indexed in the creator, title and subject fields but they are not additionally indexed in a local search field.
For example the advanced search of a non-preferred term doesn't work when a local search field is chosen.The search for non-preferred terms should be also enabled for local fields
SF 00927933
52 votes -
If your default language for Primo is not English you can not customize some Primo labels in Alma
If your default language for Primo is not English you can not customize some Primo labels in Alma.
3 votes -
Add 12-Hour Due Times Display in Library Card
Currently, per a setting in Alma, due times in Alma and Primo VE can be set to display in the 12-Hour format (ex. 02/25/2023 5:45 PM PST). However, when a patron views their account in Library Card via Primo VE, due times display there in only 24-Hour format (ex. 02/25/2023, 17:45). Please have due times displayed within Library Card use the same format that is set in Alma.
1 vote -
Advanced search: auto suggest synonyms when using "OR" in the search string
We would like to have the feature of auto suggesting popular synonyms when adding "OR" in the search string. It is a feature in EDS and we loved it!
1 vote -
Support Indexing of Collection Type(Alma-D)
When adding an Alma digital titles, all Alma digital titles are indexed, so it takes a total of three days to be published.
It takes three days to update the primo collection lobby.Please consider that only certain collection types or some collections can be indexed to reduce publishing time.
- Support Indexing of Collection Type(Alma-Digital)
- Enable indexing of a range between start and end values.(Alma-Digital)
1 vote -
Poder configurar la ordenación de los items/holdings en Primo VE
Primo no permite configurar la ordenación de los holdings o de los items asociados a un holding en la Vista completa del registro (sección Get It).
En nuestro caso, tenemos holdings diferentes asociados a una misma ubicación y biblioteca. Primo VE no permite ordenar estos holdings por signatura (ver en la imagen adjunta el ejemplo número 1).
Por otra parte, hay casos en los que muchos items dependen de un mismo holding. En este caso nos gustaría que se pudieran ordenar por disponibilidad, es decir, que se mostraran en primer lugar los items disponibles. En el ejemplo 2 del documento…22 votes -
Restrict display of digital collections by campus in views
In the same way that you can allow/disallow the display of electronic resources like ebooks in a specific view in Primo VE based on the campus of the view.
You should be able to restrict the display of specific digital items and collections.
For example if I want to make a digitial collection of database entries for my users, but I want to mark some databases as being only available/visible to a specific campus, then they shouldn't show in other views.
3 votes -
Reflect "Unpaywall API respons" in the availability of the title list.
Current system behavior
Unpaywall API response has no impact on the 'Full text online' indication of the title list..What is this problem?
Even titles that can be accessed with unpaywall are not displayed as "[Available online]", it makes problem for users to understand.
3.Improving idea
Reflect "Unpaywall API respons" in the availability of the title list.
This improvement will enhance users' access to information.11 votes -
Radio buttons on the Resource Sharing item request form on Primo VE
On the Resource Sharing item request form on Primo VE the 'Citation type' radio buttons can't be altered.
Our library would like for the 'Article' radio button to be first, before the 'Book' option, and for it to be pre-selected as the default.
Also, with the 'Format' radio buttons at the bottom of the form we would like to hide both the 'Physical' and 'Photocopy' buttons, but keep the 'Digital' one visible and selected. This is so that our users are aware that their request will be supplied to them digitally.
47 votes -
Improve phrase searching "Highlight"
When using phrase search, please do not highlight partial words or letters.
Please highlight only the exact phrase which use for the search terms.
For example, if a patron searches for "traffic accident", please highlight just "traffic accident" and do not highlight "traffic" or "accident".
Please check the phrase search results your Primo VE.
You can find that word-level highlighting makes the search results confusing.25 votes
- Don't see your idea?