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.
41 results found
-
Add ability to configure the display at the item level and the location level in the GetIt section
In Primo VE, the display of the GetIt section works currently as following:
If there are only items in one location, the first display after opening the full view is at the item level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma99118073204005503).
If there are items in more than one location, the first display is at the location level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990104195490205503).
Because our libraries are part of a huge consortium, our users always have to check first in which library an item is available before checking the item information. Furthermore, we believe that the user experience would be better, if the GetIt section looked…9 votesHi,
This is to update that this was developed for February 2024 release.
Best regards,
Yael.
-
Relevancy sorting in FRBR version list display should use terms searched
FRBR groups and the display of versions within them does not consider the relevancy of the terms searched. Often a user is searching for a specific version within the FRBR group (ex: Homer's Iliad translated by Richmond Lattimore) but there is no way to focus in on this version within the list of FRBR versions. Even when users search specifically for terms: Iliad Lattimore, Lattimore is hidden within search results. Within the list of FRBR versions, sorting by Relevancy should use the terms searched by the user -- this should enable the works of a single translator (like Lattimore) to…
209 votesIn this enhancement, Primo VE will highlight the selected record on top of the list of FRBR versions, only for the preferred record mode.
We understand from the comments here that there is also a request to add this option for Generic mode, however in the generic mode we only show a link to the list of versions and not pointing for a specific record. In Generic mode we don't show any actions or availability status, and there is no option to open a full mode as this is not a specific representation of the record.
This is why we have chosen to implement this only for preferred mode.
Please provide some more clarifications for the generic mode request in a dedicated idea.
Best regards
-
Remove field 655 from the subject facet
In Primo VE the 655 are shown in the Subject facet. As the 655 relate to form and not to content, they should not be shown as subjects. Furthermore, the 655 are correctly shown in the “Genre” facet.
The 655 should be excluded from the Topic facet in the Facets Section Mapping:
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#Facets_Section_Mapping54 votes -
ShareDigitalResources parameter to allow individual settings
When the customer parameter shareDigitalResources is enabled, which is useful to allow freely available digital representations (for digital objects stored in Alma or in a remote digital repository) to be available to all institutions, records loaded from external data sources via discovery import profiles are also impacted by this. According to Ex Libris, this is by design as these records from external sources are considered as digital objects. This leads to the following problem in Primo:
As soon an IZ enables this parameter, its records from external data sources are included in the search results of local search scopes made…
132 votes -
Add more options to configure facets by prefilter and resource type
The configuration options for facets in Primo VE are currently very limited, and not at parity with Primo on Back Office. It is not currently possible in Primo VE for a single record to have multiple facets or prefilter resource type values, to better align with CDI in a blended search, it is not possible to configure the facet and prefilter resource type values separately and independently of the display resource type values, and these facets cannot be configured with sufficient granularity. As examples of this configuration issue to be made possible with this request: Example 1: Our display types…
417 votesThis is to update that this is now supported in August 2022 release
-
Make it possible to add or exclude records from the OTB resource display types based on locally-defined conditions
We would like to have more flexibility with Primo VE resource types and the related facet and prefilter values. There are situations in which we would like to be able to add records to an OTB resource display type that don't meet the OTB conditions. For example, for certain textual integrating resources that users are likely to think of as books, we use conditions based on the presence of form/genre headings to add them to the OTB ""book"" display type in Primo BO (e.g., open textbooks that are periodically updated: https://searchit.libraries.wsu.edu/permalink/f/j5jme3/CP71251613210001451). Conversely, we would sometimes like to be able…
299 votesThe option to customize the mapping for OTB resource types will be available in May 2023 release.
Best regards,
Yael.
-
New Tool-Give Us Feedback
The Give Us Feedback Tool should perform a validity check of the email address. Currently it is possible to enter anything in the field 'Enter your email'. The email address validation is commonly used by default within forms.
10 votesHello,
This is completed and was released in November release.
Best regards,
Yael.
-
Correct citations for local Articles and Book chapters
Articles and Book Chapters from local sources (externals sources as well as Alma) don't have complete citations because data are missing in the mapping. Volume, issue and pages are not mapped.
Our request is to provide a mapping for these data elements so that they can be added to the Addata section of te record, or to allow sites to normalise the data in this section so that we can provide correct citations and export functionality.96 votes -
Enhance the database search to include keyword searching
Currently the Database Search in Primo VE is limited to searching for words from the title. This is unsatisfactory as many databases have vague and uninformative titles. We need broader search capabilities and would like the search to also include categories, subjects and descriptions.
91 votesPrimo expands the Database Search to include all search fields, such as subject and description. Previously, searches performed in Database Search matched only on the title. In addition, if configured the expanded DB search functionality will also allow users to search by category name.
-
Add Mandatory choices for all Request forms in Primo VE
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).
223 votesThank you for posting this suggestion. Starting of VE July 2021 release you will have more options to improve requests forms: adding mandatory choices , adding forms’ description including links and add generic checkbox. more details can be found in Primo VE release notes
-
Put the FRBR Dedup Test Utility where cataloguers can use it
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.
34 votesNew discovery role is now available : Discovery Operator – Limited " so more library staff can get access to the FRBR Dedup Test Utility
Check for more details in Primo VE release notes – under Allow Task-Oriented Discovery Roles for Staff -
Work with additional batches of 50 records after the first set of 50
It's now possible to select and act upon a set of 50 records in Primo VE. However, once the first set of 50 records has been selected and saved to Favorites (or otherwise acted upon), all actions on additional records must be done manually, one at a time. After the first 50, the user gets the message, "Please edit your selection to include no more than 50 records." and then it is no longer possible to work with records in batch.
For example, often a user will perform a search in Primo VE and find a set of 150 or…7 votesThank you for this suggestions. The new pagination method will allow to select additional set of records and not only first top 50 records.
This is coming with Primo May 2021 release and Primo VE June release. -
Utilize data from multiple fields (LDR and fixed fields 006,007,008) in Primo VE resource type configuration
Related to a previous idea now marked as Completed
(see: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35488570-utilize-ldr-and-marc-fixed-fields-006-007-008-in)The functionality introduced in the April 2019 release only allows you to specify ONE field in the source MARC record that contains the resource type that you want to map to the local resource type.
Primo VE should to be able to determine the resource type from combinations of data in MORE THAN ONE of the fields in the MARC record; i.e. fixed-field coding in the 006/007/008 field in conjunction with the LDR field.
This is particularly crucial for complex resources not coded as language material (LDR pos.…
281 votesIn Primo VE August 2020 we have added the option to add up to four conditions when defining custom resource type. With this we attempt to cover the need to define multiple conditions while keeping indexing performance time
See in release notes of August 2020 https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2020/010Primo_VE_2020_Release_Notes
-
Campus level settings for CDI Link in Record
Discovery Customer Settings are only configurable at the institution level.
It makes CDI Link in Records broken for multi-campus environments with separate subscriptions to vendors like Gale, Infobase, and Kanopy.
Please make customizable using Inventory Management Groups or Discovery Views.
10 votesThank you for this idea, In Primo VE December 2020 release we introduce a new mapping table for managing the Central Index linking templates with your institutional linking parameters where you can also manage multiple linking templates per campus code.
-
Boost Institutional Search Results in Primo VE
We'd like the ability to boost our institutional results in a search profile slot that includes consortial records.
46 votesThank you for this idea. We added to Primo VE the Boost My Institution option to allow an institution in a consortium to boost its search results, over results from other member institutions.
-
Bib MARC field 505$t should be indexed in the Primo PNX file as a title entry
The MARC 505$r is indexed in the PNX as Creator and contributor. The MARC 505$t is not similarly indexed in the PNX as an added or alternate title.
167 votesThank you for posting this idea. with the Primo VE June 2021 release Primo VE will index the 505 $t as well. This will be gradual rolled out pending the semi-annual indexing process planned to be completed by August.
-
Customizable RIS mapping table for Primo VE
In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:
The mapping of the RIS fields to PNX fields is as follows:
IS addata/issue
TY addata/ristype
N2 addata/abstract
N1 addata/notes
PB addata/publisher
A2 display/contributor
ET addata/edition
KW display/subject
EP addata/epage
DO addata/doi
PY addata/date ; display/creationdate
JA addata/stitle
VL addata/volume
CY addata/cop
AU display/creator
T3 addata/seriestitle
T2 addata/addtitle
T1 display/title
SP Addata/spage
JF Addata/jtitle
ID Alma MMS ID
SN Addata/issn; addata/isbn; addata/eissn; addata/eisbnAs most reference managers will read A2 as Series Editor,…
58 votesThank you for this idea . With the April 2022 release Primo VE allows you to customize the default mapping used to export records to RIS format.
-
Display item policy in item record
It would be useful if item policy could be configured as a field to display in either the brief or full item display. Currently, the loanable indicator is defined by the fulfillment terms of use, which is dependent on users signing in in order for Primo to calculate the loan policy specifically for that user.
Having the option to display the item policy from Alma as a field in Primo would be beneficial as this does not change dependent on the user type or fulfillment rules. It would also provide more information to users irrespective of whether they are able…
968 votesHi all,
This enhancement is now available with the Primo VE August 2023 release.
To learn more on this, see -
Best regards,
Yael.
-
Barcode search in Primo
It would be extremely helpful it we could search Primo VE by item barcode. We often want to quickly locate a bib record in Primo and scanning a barcode is the simplest and quickest search.
172 votes -
Customizable Collection Discovery according to PrimoVE views
It'll be great if, according to the view, you can see specific collections displayed in the Collection Discovery.
Currently, Collection Discovery is the same regardless of the view, which goes in detriment of the user experience.334 votesThis is now available in the August 2022 release
- Don't see your idea?