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.
349 results found
-
Apply Display Logic Rules to CDI direct linking records
Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.
For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text…
93 votes -
Ability to boost Ranking of Search Results in Primo VE based on accessibility
Some of our consortium libraries would like the ability to boost the ranking of books that readers can request from libraries.
Currently, the Ranking Configuration page enables you to configure various aspects of the ranking algorithm based on Field Boosting, Date Boosting, Resource type Boosting, Institution Boosting, but not on accessibility.82 votes -
Allow users to customize PNX addata subfields
Currently, the normalization rules for creating addata subfields are not available to users. As a result, redundant information is included in subfields intended for authors, creators or titles and as result the citations are inaccurate.
79 votes -
Improve advanced searching in non-Roman languages so a "Title" + "Starts with" search parameter queries the MARC 880 field
When combined, the “Title” + “Starts with” advanced search parameters do not query the linked MARC 880 field. This prevents users from successfully using this index for non-Roman language search queries.
When the ExLibiris Development Team reviewed this issue previously, they found that Primo VE's design excludes the 880 field from Title Starts With indexing due to index size limitations.
We’ve been advised that “Title Contains” and “Title is Exact” do index the 880 field, and can serve as a workaround. However, users expect consistent search behavior across all indexes, regardless of language used in the search query.
A few…
57 votes -
Resource type newspaper articles in main discovery search
Make it possible to activate resource type newspaper articles in main discovery search, not just in newspaper search. It should be possible to activate both all newspaper articles or included/excluded at collection level. We have the Swedish database Article search/ Artikelsök and today the newspaper articles is not visible in the central index together with other resource types like book reviews, journal articles etc.
65 votes -
Include DOIs in references in APA 7th ed. format for records coded with Dublin Core.
Exlibris has just updated the APA 7th ed. citation format settings to include the DOI for MARC21-encoded records (idea exchange: Improve APA citation format to include the DOI for an article), but we also want Exlibris performs the same process for Dublin Core-encoded records.
Users are increasingly turning to PRIMO to obtain the citation reference of a record they are interested in and in many cases their metadata is in DublinCore format, as more and more catalogs integrate repositories that encode information following this format.
97 votes -
Search should be more forgiving of spelling errors/incorrect searches
We would like the search in Primo VE to be more forgiving in terms of spelling mistakes and incorrect searches, akin to other search engines, as this is what our users are mostly familiar with. For example, searching “Das Leid des jungen Werter” instead of “Die Leiden des jungen Werther” will find the searched for title on Google, Amazon as well as a local bookshops online platform, while on Primo VE, the book itself, of which we have several versions in our catalogue, is not found at all and only some related literature is shown. Another example would be “The…
100 votes -
Put search/feedback links in logical order on mobile menu - NDE
In NDE on small screens, the Advanced Search, Feedback (Report a problem) and Ask Anything (natural language search) links appear in the menu in that order - see screenshot attached.
At minimum, the two search options should be adjacent, and in the order they appear on full screen. The feedback/report a problem should not be in the middle of them, as it is a completely different type of function.
Some institutions may even wish to relocate the feedback option to the bottom of the top menu links.
The original case response was to log here on the idea exchange, as…
18 votes -
Limit Research Assistant results to resources patrons can access
It would be nice at a configuration level to be able to limit the Research Assistant results to those within an institution's collection and OA as the default setting, rather than the entire CDI as it is currently.
Users could then select to expand their search to the CDI, like they currently do when searching Primo.42 votes -
Available online in Research assistant as default.
It would be beneficial to be able to make what is under the refinement icon in the search box more visible. It would be even better if we could make the "Available online" button be checked by default.
As it is now it is so hidden that users aren't aware that this is a possible feature. The fact that the user needs to select the refinement icon to see this possibility isn't optimal.
58 votes -
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 !134 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…
139 votes -
Ability to Configure Multiple Journal Searches
Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).
We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.
Each Journal Search should:
Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)
Have customizable display labels and help text to clearly indicate which journal collection the search covers
Support direct linking to each Journal Search from library platforms
Use Case: …
31 votes -
Converting Greek letters in queries for local materials
When queries include Greek letters with diacritics, the retrieval omits many local records, as there is no conversion in Primo VE between letters with or without diacritics, or with different diacritics.
Example:
Searching ἄγω or αγω gives different results. CDI records are retrieved regardless, while local records can only be retrieved in the exact manner they were cataloged.Using a blended search (local+CDI) can confuse patrons, as it may lead them to believe the library does not have certain materials. Using a local search scope, patrons sometimes receive zero results, so many records are hidden from them.
Greek is not…
38 votes -
Discovery collections per library and unfiltered view
In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable"…28 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…
70 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.73 votes -
Include subfield k from 245 in title index (important for manuscripts/archives)
Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html
This subfield is important for manuscripts and archives. Examples from OCLC:
245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5
245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David…
34 votes -
Display ebook reading format (HTML, EPUB, PDF etc.) in Primo (VE) full display
When displaying links to Ebook providers in Primo (VE) full display it would be suitable to have a notice of what ebook reading formats accessible for each provider. Instead of having to click further to the each provider to retrieve the information. Even information about online reading and/or download option would be suitable.
44 votes -
Enable Custom Configuration of Primo Normalization Rules for Local Authority Search
Current Situation: Local authority search records are currently displayed with hard-coded normalization rules (NRs).
Proposed Change: Allow users to configure Primo normalization rules for local authority search. This flexibility will enable us to normalize authority records and display fields according to our specific needs.
127 votes
- Don't see your idea?