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.
558 results found
-
Open Access Indicator for Unimarc records
Open Access Indication in Primo VE is currently supported for Marc21 and Dublin records : https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Open_Access_Indication_in_Primo_VE
Please support Unimarc record, too !133 votes -
NZ/IZ linking in consortia
Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.
In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the…
118 votes -
Allow Online Services Order to sort by current access
We need the ability to move to top of View It a service with current access (this means the coverage statement is open-ended, ie Available from 1998 - current).
Users get overwhelmed with the long list of services often displayed, and ordering the list according to interface or electronic collection name doesn't address the most important aspect, whether there is current access or not. As an example, on Proquest interface Z, journal title X may provide current access, but journal title Y on the same Proquest interface Z may only have archive access. We only want to put journal title…
235 votes -
Primo VE : Alignment of Unimarc normalization rules with Marc21 normalization rules for the creation of the author facet
The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).Key Issues:
…1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.55 votes -
Author/Title Index in Browse Search
Author/Title Index in Browse Search
Please include an Author/Title index which searches headings combining author/creator name and uniform title. The index usually includes:
* 100/240
* 110/240
* 111/240
* 700 where $$t is present
* 710 where $$t is present
* 711 where $$t is present
* 800 where $$t is present
* 810 where $$t is present; and
* 811 where $$t is present60 votes -
List of Stop Words in Catalan
Alma/Primo clients in Catalan cannot use the Full Text Indexing utility in Primo VE with all its functionality because there is no Stop Word List implemented in Catalan.
Because of this and the 10,000 terms limit per indexed file, the included PDFs are not fully indexed.
We are 17 university libraries and a national library (Biblioteca de Catalunya) that form part of the University Union Catalogue of Catalonia (CCUC); 2 university libraries from València (Universitat Jaume I and Universitat d’Alacant); and 62 collaborative institutions with special libraries.
We contribute to the visibility of more than 12 million documents and…
56 votes -
Disabling automatically generated links for related records if the associated NR is disabled.
Primo VE is capable to automatically create links to related records via MARC 7xx fields.
As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
- in the related records, they differentiate between child records and parent records
- for child records, as the specific relation field is included, Display NR takes effect
- for parent records, as the specific relation field is not included,…48 votes -
Improved Display of Coverage Statements for Taylor and Francis Journals autoholdings collection.
Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
We propose to:
1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
2. Present only non-overlapping coverage statements to users in primo.
This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all…52 votes -
Related titles in Primo VE records display: separate window
When records have bib-to-bib relationships via 8XX (or 7XX), the list of related titles is displayed in the Details section of the series/host record. Unfortunately, the list is currently sorted alphabetically by the title, which is very user-unfriendly with a large number of linked titles.
This behavior has already been criticized in this idea. Unfortunately, it is still not possible to sort the related titles logically by sequence or volume.
The Austrian Library Association (OBV) uses Primo BO and has implemented a user-friendly solution for displaying related titles:
In the case of multi-volume works and series, the individual volumes are…142 votes -
Integrated Library Mapping and Analytics for Primo VE
Develop an integrated library mapping module for Primo VE featuring interactive floor plans with clear, step-by-step directions. Seamlessly integrate this module into Primo VE's existing infrastructure, ensuring a user-friendly interface accessible to all patrons.
Benefits:
• Enhanced user experience: Streamline the path from digital search to physical item retrieval, reducing frustration and improving overall user satisfaction.
• Valuable collection analytics: Gain insights into patron behavior, optimize collection placement, and make data-driven decisions about space allocation.
• Streamlined workflow: Replace third-party solutions, reducing complexity and simplifying library operations.
• Improved accessibility: Ensure all users can easily navigate the library by providing…112 votes -
Allow institutions to exclude the 776 from the CDI holdings file
Proposal: allow institutions to exclude the 776 from the CDI holdings file
Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.
The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible,…
84 votes -
Do not show availability for CDI/Alma records with matching GTI ID
Occasionally, CDI records will show availability for physical items (holdings/digitization offers via Rapido), and the physical records will show online availability. To our understanding, this is due to a matching GTI ID. We were informed in a SF case that it is currently not possible to resolve this. As this leads to confusion for our libraries (mainly digitization requests for an electronic resource) we would be glad if a solution could be found to no longer show these incorrect availabilities (or at least for the digitization requests to show the physical record they were actually placed on).
Example: https://ubs.swisscovery.slsp.ch/permalink/41SLSP_UBS/giv3ks/cdi_askewsholts_vlebooks_978354048849157 votes -
Responsive label "item in place/not in place" for open shelf items
Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.
As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this…
27 votes -
"Remember all filters" should be selected by default
We want "Remember all filters" to be selected by default. It confuses our users who expect that their filters will remain while they change their search, only to find that they had to click "Remember all filters" first. We'd rather them have to de-select "Remember all filters" if there's a reason they don't want to retain them in their searching.
Relates to https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/34854556-make-facets-sticky-by-default-for-the-session, where the "default" part was never instituted.
65 votes -
Provide option to remove 490 field from Browse Index
We would like the option to remove the 490 series description field from the Browse index. Because we use 490 for series description and 8XX for the authorised form of series in the same record, the browse series feature in Primo counts one record twice. If we could have the option to remove this from the Browse index, this would solve the problem. It would need to be optional as it is clear that some Primo Libraries rely on the 490 for this purpose.
26 votes -
please add pick up library in purchase request form for patron to choose if checking "reserve"
Hi, sir,
There is purchase request library in primo VE purchase request form.
But usually the request library is not same as user pick up library, if patron check "reserve", that mean once the purchase is accepted and book send to library ,alma will generate a reserve for this request.
but now has no patron's pick up library for reference.
so please add a pick up library filed in purchase request form if checking "reserve".
Thanks ~20 votes -
Show the date/time a question is asked in the AI research assistant, and in the copied result.
The date/time a question was asked is only visible when hovering over the question in the research history sidebar. This is a problem especially when working with history items that have multiple questions.
Scenario: User asks a question on something contemporary. They want to ask the same question in 3 months and then again in 6 months as more sources become available.From the history they open their previous question and use the "Try again" function. In another few weeks they do this again.
The question responses do not indicate when each iteration of the question was asked.
If they…11 votes -
Purchase Request date
Add the user's purchase request date on their Primo library card in their account.
We would like that the user can see the date when he create a purchase request date on his Primo library card in his account.
We think that's will be an improvement for the users.
19 votes -
Improve Primo linking to limit dead/inaccurate links
To prevent user confusion, frustration, and access delays, we would like Ex Libris' Primo to mirror a feature that LibKey calls "Entitlement Confirmation," which would help prevent delivering dead links to end users, especially when Metadata in the CDI is lacking or incorrect.
Delays between publishing and availability, especially with third-party databases (like EBSCOHost), happen often and can vary in length due to the nature of aggregation. The proposed change would confirm if content is available before indicating to end users that it is. This saves user and staff time and effort, streamlining the process and managing expectations while providing…
22 votes -
Modernize purchase request from customisation
The Rialto purchase request form has a much improved user experience for requesters, a modern style and simpler, more flexible configuration. Its downfall is that it has NO authentication. The product team have reviewed this idea (https://ideas.exlibrisgroup.com/forums/940011-rialto/suggestions/46699696-enable-authentication-on-purchase-request-web-form) and advised that adding authentication does not fit with the Rialto roadmap.
There are some disappointed Rialto customers at this news. Libraries have indicated that they cannot use the Rialto form because it has no authentication.
However, providing an improved UX for the purchase request form used in Primo would benefit many more libraries and their thousands of customers - and…52 votes
- Don't see your idea?