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 consistent the use of CDI record data in Primo UI
Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.The negative impact of this design decision includes:
* a user is confused by…317 votes -
Have the option to configure portfolio views in VE to more than 25
Classic Primo allowed this via Configuration > Resources > Other Settings > enableviewitshowall_results = true but this does not work in VE
6 votes -
Display on the Location list: textual descriptions of the physical arrangement of a holding unit
Since the updates in January 2021, the Location list has become capable of displaying the Field 866, 852, etc.
There are cases in which the issues of a single journal title are located separately according to publication years. Here we present a case example to explain the situation:
Group 1: The issues published in the last several years; they are shelved in the “New Arrival.”
Group 2: The issues published several years before the Group 1; they are shelved in the “Back Numbers.”
Group 3: The issues published more than 20 years ago; they are shelved in the “Remote Storage.”…
52 votes -
Please add to the PRIMO VE mapping table documentation the last update date and mark the new changes in red.
Hello,
We recently discovered that the Primo VE mapping table was updated with new information.
It would be very helpful if you could add last update date and mark in red the new information, the same way that LC mark in red the new information in Marc 21.
If you would apply this suggestion also to other documentation pages it would be great.
Thanks,
Dafna33 votes -
Allow Local Fields as filters for NZ Search Scopes
When setting up a custom scope we found the "Local fields" option was not available in the dropdown list if we choose scope population "Entire Network".
The "Local fields" option is available in the dropdown list if we choose scope population"My Institution".We think the "Local fields" option should be available for scope population "Entire Network" as well because we can set up up to 10 local search fields in the NZ and they would be used in the scope definition.
This would allow consortia to exclude specific resources from the NZ scopes based on values in the NZ local…
8 votes -
Index Item Level Information
We have entered journal contents into item records. Currently, journal contents is only searchable if the title is available electronically. We would like users to be able to retrieve contents from our physical journal holdings when searching in Primo. This information is contained in the public note field of the item record - having the option to make this searchable would be of great benefit to our users.
Public level notes can be seen in the Primo record, but they cannot be searched so users have to know what they're looking for before they look for it.60 votes -
Allow item-level general electronic services to be used in display logic rules.
Make it possible to hide an Item-level general electronic service based on the existence of another service using a display logic rules. Also, make it possible to hide another service based on the existence of an item-level general electronic service.
1 vote -
Add expand search (outside Imperial) into search scope
When users and staff are searching Primo. Many of them want to run an expand search straight away. Rather than searching everything and then clicking on expand search.
Solution: it would be better if expand search (outside imperial) could be a search scope. Although users the chance to search expand search straight away.4 votes -
Add expand search (outside Imperial) into advanced search
User Story - When staff and users are creating an advanced search. Sometimes they want to search with an expanded search (outside Imperial). However, currently staff have to run the advanced search then click on expand search (outside Imperial). Solution: It would be better if expand search is added to Advanced search as an option.
1 vote -
Ability to collapse all sections in the get it section by default
User Story: Many of our librarians use Primo to search for our records. They would prefer to be able to see the barcode information on all items in the get it section. As soon as they open the record. Rather than having to click each one, show the extra information.
Solution: we are requesting the ability to have all items collapsed by default in a specific view. So that library staff can see the item information, once they open the record.0 votes -
Add "Locate" link to Primo Analytics
We would like to find out how often users are clicking on the Locate item within the Primo VE record to view the map where the item is located; this is the label nui.locations.locate in the ViewIt table. Ex Libris support has confirmed that this link currently cannot be tracked in Primo Analytics because there is not a beacon call associated with the link. We would like to request that the Locate link be added to Primo Analytics tracking.
82 votes -
Static URL for Pay Fines link
The Pay Fines link in the User Account/Library Card interface should allow for a static URL link instead of including the JWT information at the end of the URL.
5 votes -
Allow Primo/Primo VE View customization packages to accept .db files and .DS_Store
The view customization packages for Primo and Primo VE do not allow .db files. When someone opens a folder with images, Windows automatically creates a hidden Thumbs.db file. MacOS creates similar .DS_Store files.
This file can be difficult to remove even with rights to view and delete the file, since Windows will sometimes indicate the file is in use and cannot be deleted.
Rather than jumping through hoops to recreate the customization package structure and carefully place images only in the desired folders never to be opened again, I would propose that Primo and Primo VE accept customization packages that…
7 votes -
The BibTex export from Primo does not include the DOI. Would it be possible to add the doi field? I know doi isn't a standard field in Bib
Include the DOI in the BibTex export from Primo
Would it be possible to add the doi field? I know doi isn't a standard field in BibTex, however it would be very useful and is requested by our users.
20 votes -
Pin to the result last viewed in Primo after closing the item record
The current Primo design returns the user to a random earlier page, not necessarily to the same record, after clicking on a search result to open up the item record. So currently, after viewing result no. 24, and closing it, it could return you to result 11 in the Primo search results page.
1 vote -
Enable authority Record Enrichment in Primo VE on local subject fields
In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records. However, this works only in the generic advanced search Subject field.
We need Primo VE to enable authority record enrichment on local fields as well.
Indeed, we have configured local subject fields that are more specific than the default Subject field. These enable searching only on specific subject vocabularies. But configuring such fields does not include the enrichment capability.
79 votes -
When a patron is unable to access their library account, they should be informed of why not
When a patron is unable to access their library account in PrimoVE, they should be informed of the reason why, in detail.
1 vote -
Retain search field keywords when switching to Browse Search
The following is a request from one of our teaching faculty. "When a subject heading search is performed in [the search scope for my institution's holdings] and the patron then wants to browse other variants of the subject heading and clicks on BROWSE in the top bar, the search box is blank. Then the patron has to retype (or if they are experienced and have copied the subject heading) paste it in and perform the search again. It seems like a simple fix to make the search term sticky so it would automatically populate the browse box."
1 vote -
Primo VE: Re-instate the A-Z browse function for DATABASES
Re-instate an A-Z browse option for Primo VE Database Search, like the one available for Primo Classic.
201 votesThank you for this idea. We are currently examining it also as part of the NERS voting (7820).
-
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
- Don't see your idea?