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
-
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 -
Option to deactivate the Resource Sharing Request Service for records without physical item of electronic/digital services
Dear colleagues,
this idea is for adding the option to deactivate the Resource Sharing Request service in Primo VE for some groups of records without physical item of electronic/digital services, without having to deactivate the Resource Sharing Request rule in Discovery Interface Display Logic.This deactivation should be applicable only to local records (catalogued in Alma) and the single institutions should be able to decide if enable it or not.
We would like the same behavour that exists for Primo also for Primo VE (for example, indicating to Primo VE that when the availability is "no inventory" ILL must be…
73 votes -
Export to Excel
We would like the "Export to Excel" functionality to be configurable. For exemple, we would like to remove the permalink column from the file.
73 votes -
Hover-over article abstract in PRIMO VE
Currently, patrons need to go into the full article record from the brief results page to read abstracts.We would like to suggest that PRIMO VE provide the user with a hover-over article abstract on the brief results page so patrons can skim abstracts before going into the full record.
69 votes -
Do not display private fields in “display source record” or full record in Primo VE.
Marc 21 coding is used to identify some marc record fields/subfields as private. As an example, the indicators in the 541 tag are used to indicate that data in the field is ‘private’ to the organisation. Primo VE should automatically hide these fields from the source record and full details display in Primo VE. If an organisation wishes for the field to be made public they can adjust the record coding as appropriate. Alternatively organisations should be able to select to suppress private fields (as identified in marc 21) from public display.
68 votes -
Changing the language in Primo should also update the preferred language in Alma
We have a mix of users with different languages at our university, but we cannot get a reliable language setting from the SIS feed. Therefore it is important that the users can edit the language preference themself to get letters from the library in the correct language.
Today, changing the language in Primo only changes the interface language in Primo, but we would like it to also update the preferred language in Alma.
68 votes -
Visualización doble de registros con copias impresas y electrónicas activadas en Primo Central
En los casos en que disponemos de un registro bibliográfico con ejemplares en formato impreso, copia electrónica activada en la "Comunity Zone", y además se ha activado también en Primo Central para garantizar la indexación y la capacidad de recuperación a nivel de texto completo, el registro bibliográfico se visualiza en Primo VE como si fueran dos registros bibliográficos exactamente con la misma información (códigos de barras, signaturas y ubicaciones duplicados).
Según nos dicen desde SalesForce, debido a limitaciones/arquitectura del sistema, no es posible combinar el registro de Primo Central con los registros locales en Alma, lo cual crea confusión…
68 votes -
Item - Searchability of Public note in Primo VE
We use the Public note of the item for provenance information. For this reason, the field contents should be searchable in Primo VE.
68 votes -
Collection Discovery : Add a button "View this collection as search results"
Beside the buttons to display a collection as a Grid or a Gallery, we would like to have a button to get the collection items in the result list, with the brief display and the facets. This could be a deeplink on the Collection ID with a "query=cdparentid" in the URL.
Please note that there exist two very close ideas:
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/36709789-add-facets-into-the-collection-discovery-ui
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37607257-collection-discovery-display-items-in-a-list-view
But this idea groups both features.Thank you.
67 votes -
Display number of loans in item record (Primo VE).
It can be useful if Primo VE display the number of loans per item under the get It section.
66 votes -
Items loaned to Resource Sharing do not show as included in local scopes
Primo indexes one location for each item - the current location. In the case of resource sharing, the current location for the item is the temporary location. Therefore, when you search from a local scope, items in the resource sharing location are not found.
We would like to have the scope reflect the permanent location not the temporary location.
We have a scope for our Teaching Materials Collection which is specifically geared to our Education major students. They are taught to use this scope in their instruction. Not finding materials in this scope that are on loan via R/S (as…
64 votes -
Index MARC 250 (Edition Statement) in Primo VE
The MARC 250 field is not included in the out-of-the-box indexing in Primo VE according to the documentation. Users frequently include the edition in their searches because it is referenced in a citation they've found. It seems like it would be a worthy inclusion in the keyword index.
63 votes -
Add ability to select multiple options on Advanced Search drop down menus in Primo VE
It is not currently possible to select multiple options on an Advanced Search drop down menu is Primo VE (ex: Material Type, Language); this functionality would be very helpful for users who wish to do more precise searching -- especially since Primo VE lacks the functionality of combining search results. This functionality is the HTML select multiple attribute (https://www.w3schools.com/tags/att_select_multiple.asp)
62 votes -
Field Pickup in Resource sharing form with default to leave blank
Now in the Pickup field, the first library in alphabetical order always appears by default. Many users click ENTER without having correctly filled in the Pickup field.
The best thing is that this field, even though it is mandatory, by default remains blank in opción, to force the user to choose.61 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 -
Show number of results in Search History
It would be useful to display the number of results associated with a search query when viewing Search History in Primo VE.
59 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 -
Show e-collections activated in the NZ in the Database Search of IZs
In our network we activate certain Open Access e-resources in the Network Zone. These e-collections are activated for every IZ without restriction. Some of our Institution Zones are using the Database Search to allow Patrons to search for their e-collections. Unfortunately, the Database Search is showing only e-collections that are activated and have inventory in the IZ. It does not show any of the Network Zone e-collections.
We would like to have the option to include the Network zone activated e-collections in the Database Search of the IZs.
56 votesThank you for posting this idea. We are checking the option to enhance Database Search scope to include also e-collections that are available for all not only for the specific IZ.
-
Option to create additional links for records from external data sources in Primo VE
At time, in Primo VE, it is only possible to create a link to the resource and a link to the thumbnail in the Import Profile for external data sources. In Primo with a BO, however, it is possible to create nearly as many links in the PNX links section as you like. We use these links a lot for the records of our many different data sources, e.g. create links to an abstract or tables of content, links to related titles, and many mores. These links help to enrich metadata and are user friendly. Therefore, we suggest that in…
55 votesHi all,
This is to update that this issue is currently not planned. We will evaluate it again for next year's road map.
Best regards,
Yael.
-
Enhance DC XML normalization routines for external sources (PrimoVE)
In Primo Back Office, there is 86 inbuilt transformational routines for MARC21 and Dublin Core data normalization (e.g. “Take first words”, “Get highest number and normalize last digit”, and “Remove HTML tags”). Most have been translated for MARC21 in PrimoVE by various people but, because of limited regex and Xpath functionality, few have been translated into Dublin Core XML normalization routines for PimoVE.
We would like to see the implementation of full regex and/or XPath / XQuery functionality (or similar) to allow all Back Office normalization routines to be created for PrimoVE.
55 votes
- Don't see your idea?