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.
409 results found
-
Please add $b to the mapping of tags 100 & 700 to Primo VE facets
The mapping of Alma tags 100 and 700 to Primo VE facets includes only $a. $b contains for both tags the dynastic number of kings, popes and high nobility. Without the addition of $b it is impossible to distinguish for example the English kings $a Charles $b I and $a Charles $b II or popes $a John $b XXII and $a John $b XXIII
Therefor, we ask to add 100 $b and 700$b to facet values
39 votes -
Primo VE be able to get information from AVA and INT holding fields
Currently, Primo VE's normalization rules can only use information from bibliographic records, so it is not possible to obtain and process information from holdings. The classic version of Primo can get this information from the AVA and INT holdings fields but Primo VE can not perform this task.
39 votes -
Allow additional links to be added to my library account
In classic Primo we were able to add our ILL link to the library account area, so users could go over and see the rest of their loans. We would like the ability to do this again and have it show up on the loans tab in the My Library Account.
39 votes -
Collection discovery - sub collection searches
We welcome the enhanced searching on the top level of collection discovery however we have found we also need full searching over our nested sub collections. This is not only useful for users of PrimoVE but also for local data scopes as we require them to accurately include sub collections in search profiles.
39 votes -
Journal search>Browse by categories : allow indexing of Unimarc journals (PrimoVE)
Currently, only journals described in Marc21 are indexed by subject in Journal Search.
The Unimarc community is now large in Alma/PrimoVE, and the Browse by Categories function would be useful if it took into account all formats.
The idea would be to allow indexing of journals described in Unimarc, which have Rameau/LC subject fields in 60X and LCC field in 680.36 votesHi,
We would like to update that this idea is still not planned, but still being examined for a future release.
Best regards,
Yael.
-
Fix Defect: Advanced Search date filter
The date filter only works for year (not day or month) in the advanced search for Primo Central records.
This is a known issue with searches for Primo Central records. Primo Central searches on the creationdate field, which doesn't have a month/day, only year. Therefore, if you use the Advanced Search Start Date/End Date fields, the results will include Primo Central items outside of the month/day range.
Please fix this defect to allow searching on day, month, and year.
36 votes -
Searching an item corresponding to a specific record is not possible if not logged in to the IZ that owns this item
If you are logged in an IZ A and you are searching a specific item belonging to a specific record, you will find it only if this IZ A owns this item. If you are logged in IZ B that does not own any item of this title, the holdings are merged into one or several records (deduped) and you cannot distinguish which item belongs to which record.
Example:
IZ A has 6 records of one title; each record has one item.
In the IZ A, searching this title, you will find 6 records, each one with its item
IZ…35 votes -
Expandable facets beyond the number we set
Recently it has become possible in VE to display up to 50 facets. 50 tries the patience of the average user but may be what it takes to help those with more specific needs. In some cases CDI limits the number anyway. It would be better if more facets are available this could be noted at the bottom by a "more" link which would then display more than the default number. This would be more consistent with other ways Primo displays complexity.
35 votes -
Journal A-Z and Database A-Z functionality based on a campus scope.
On our current Primo we have Journal A-Z and Database A-Z functionality based on a campus scope. This is due to us having two Primo views - one for Cardiff University and one for NHS Wales. We share a catalogue but have created the ability for our users to search in Primo on a dedicated view depending on their affiliation; so that they receive search results only for items to which they have access. This split in search results includes the A-Z listings. And it is all based around a campus scope. We have been told that for our move…
33 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 -
Ability to store test records for Primo VE
When you test normalization rules for external data sources in Primo VE, you need to upload your test record from your computer every time you make a change in the NR. It should be possible to store sample records for easier testing
32 votes -
Allow Roman numerals for page range in digitization request form
Users submit a range of pages when they request digitization of a material. Preliminary pages in books often use Roman numerals. Please whitelist these characters along with 0-9 in the form validation scheme.
32 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 -
Primo VE webhook search blending
In terms of usability, it would be good if Primo VE webhook search results could be blended to the combined search results (local resources and articles). Blended results feature should be able to select on a search-by-search basis e.g. if you apply search for AI-based article search portals or whether to apply search for printed resources from the repository libraries.
32 votes -
Primo VE: enable search fields for the deepURLs
InPrimo VE, in the "search" : {} section of the PNX record there are some fields that are still not searchable,
like the "unimarclocalfields". It would be nice if all these would be accesssible with the deepURL query parameter
I.E.: query=unimarclocalfields,contains,XYZ.32 votes -
Disturbing hover texts in Get It and Active Filters
Hover texts in Primo VE
In the "Get IT/Location" area in the copy view, all data (for example: section, callnumber, availability, ...) is output again as hovertext (white font with black, semi-transparent background) when hovering over it (see appendices 1-3). The same error also occurs with the Active Filters on the search results page (see appendix 4).
This redundancy disturbs the user experience and already confuses users. In some cases, this phenomenon makes it impossible to see the entire text.
I request that these disturbing hover texts be removed.31 votes -
Change the normalization rules for local resource type book
Change the normalization rules for local resource type book and create a new publiction type called Monographic series. The OTB rule in Primo VE is (Leader(06-07) = ac or ad or am) OR (Leader(06-07) = ab|ai|as AND 008(21) = m): https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/120Other_Configurations/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record
This rule should be created for Monographic Series:
(Leader(06-07) = as AND 008(21) = m)
We also think that ExL should reassess their rule and exclude this part: (Leader(06-07) = ab|ai|as AND 008(21) = m) and set up a new rule for monographic series (check:https://www.loc.gov/marc/bibliographic/bd008s.html). The codes for ‘ai’ and ‘ab’ are so rare we think they…31 votes -
HAL : issue about "full text access" link
HAL https://hal.archives-ouvertes.fr/ is one of the major open repository in French.
Some publications give full text access, others not. See screenshot attached.
We did activate for search Hyper Article en Ligne (HAL) in PCI.
Our concern is that all HAL publications in PRIMO display with "full text access" link even when there is no full text.Please have a look to the example : Reconceptualizing the classification of PNAS articles.
This issue generates lots of complains from our final users. HAL is very well used in French speaking countries.so could you fix this and indicate "full text access" when…
30 votes -
Add prm-spinner after patron submits a Request Form
When patrons submit a request form (Physical Item/Article/Resource Sharing) in Primo VE, there can be a time lag of up to 45 seconds before they get a confirmation message. Before Ex Libris disabled the Send button, patrons were resubmitting the requests during this time lag. Now it appears they are reloading the page and resubmitting request.
I suggest you simply add an in progress status with a spinner so patrons get a visual cue that the form submission is in progress and they just need to be a little patient.
28 votes -
Feedback Tool for Primo VE - allow user's email as addressFrom in Report a Problem Letter
The Feedback Tool for Primo VE (May 2022) would be even better if the user's email address could be put in the addressFrom field in the Report a Problem letter in Alma. Just as the category is put in the emailSubject field:
New feedback received from a Primo user - {category _ name}
allow the addressFrom field to contain:
{user _ email}
This would then work better with CRMs and ticketing systems, or just mean that you can hit Reply to the email.28 votes
- Don't see your idea?