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
-
Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation
When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.
What we wish to achieve is the following:
When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of…
656 votesHi all,
We are currently reviewing this idea together with Alma.
We will update with any new information we have.
Best regards,
Yael.
-
Improve indexing of in press articles in CDI
The Central Discovery Index (CDI) includes many in press articles (i.e., articles that have been accepted for publication in a future issue). However, because these records do lack a pub date, volume, or issue number, the Alma link resolver cannot reliably determine whether an institution has access to these articles. We ask that Ex Libris improve they way in press articles are indexed in CDI so that the link resolver does not return false positives for content the library does not actually own.
484 votesThis improvement is planned for the 2024 Roadmap.
-
Primo VE: Allow Exclusion of Institution Zone only records from Discovery Network/NZ Scope
In consortial environments, the Network Scope includes Institution Zone only records such as laptops, keys, etc.
We would like the capability to exclude IZ only records from a Discovery Network scope so that we can display only records that are NZ bibs, not local IZ with no NZ bibs.
424 votes -
Ability to edit the OTB (Out-of-the-Box) search and facet rules in Primo VE
We would like to be able to edit the OTB search and facet rules. This is necessary for parity with PBO. There are several things that we were able to do in PBO that we cannot reproduce in VE because of the lack of this functionality. In the PBO OTB author search and facet, we were able to include dates and qualifiers from names in the LCNAF, which improved precision. In the OTB language facet, we were able to include intertitle, caption and audio description languages, which are not currently included in the VE OTB index. On the other hand,…
393 votes -
Improve Primo Search Algorithms
When our users look for a book in the Primo Search Portal they expect that the Primo Search behaves like a Google Search, i.e. they expect that Primo finds books with titles or metadata containing words similar to those in their query. Unfortunately, the Primo Search is very sensitive to the exact spelling of the words in the query. If the search query is slightly inaccurate, the book is not found in Primo. I tried such unsuccessful search queries on www.amazon.de, and Amazon usually found the correct book: Amazon showed the correct hit on top of the list (see…
391 votes -
Primo VE: Ability to use norm rules to specify which 856 (Marc) fields display in Links service
In Primo Back Office (BO), it is possible to use normalization rules to specify which 856 Marc fields display in the "Links" section of the Primo full record view. (See attached screenshot.)
We would like the same functionality in Primo VE to choose which 856 links to display based on the 856 first and second indicators and/or the subfields of the 856 field. Thank you.
345 votesHi all,
This is to update that we plan to develop this option in the future. It is not in the current roadmap for this year, and we will update as soon as we have more details about the development planning.
Best regards,
Yael.
-
Visualization of Analytical Bibliographic Data in PrimoVE.: Correct Sorting of Parts
A multi-part resource (eg: a sketchbook containing 200 drawings) is catalogued in MARC 773 (host/item relationship). PrimoVE ought to sort and display the component parts using $$g and $$q. Currently PrimoVE fails to do this in the correct numerical order. Rather, the presentation is alphabetical which is useless for component-items organized by their part or page number. There was a recent ideas exchange issue raised on this very topic, which was “solved” by providing the aforementioned “alphabetical solution”. However, a NUMERICAL visualization has much more value in Discovery for patrons who are interested in locating an item as part of…
305 votes -
Do Not Highlight Stop Words in the Results of a Keyword Search
There is no value to highlighting words in the search results of a keyword search that were considered STOP words when the search was conducted.
Words such as AND, THE, OR, IN, TO, etc., provide no value on their own and should not be highlighted. Not only does highlighting them add visual noise to the search results, it sends the wrong message to users about how to construct a strong search string.
As the screenshot shows, the highlighting is only adding noise.
299 votes -
Primo VE: Ability to search by publisher (advanced search or facet)
The MARC 260b + 264b field is not included in the out-of-the-box indexing in Primo VE advanced search or facet as PUBLISHER. According to the documentation the publisher name is searchable only by general in the simple search and not in the advanced search, specific search for the publisher name. Readers want to limit the results by the name of the publisher.
295 votes -
Allow libraries to configure the Brief Record Display with more flexibility
In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).
We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to…
275 votes -
In Primo VE and in consortial Alma setup, display print and electronic inventory even if dedupe/frbr is enabled
In a consortial Alma setup with a Network Zone and with Primo VE, our consortia has noticed that if an Institution Zone (IZ) has enabled dedupe/frbr in a Primo View and there is print and electronic inventory for a title, the print inventory of other IZ’s is completely hidden and only the electronic displays.
See “enabled dedupe frbr1.png” https://wrlc-gwu.primo.exlibrisgroup.com/discovery/search?query=any,contains,doing%20bayesian%20data%20analysis%20a%20tutorial%20with%20r%20jags%20and%20stan&tab=WRLC_P_MyInst_All&search_scope=WRLC_P_MyInst_All&vid=01WRLC_GWA:test&offset=0
As you can see in “enabled dedupe frbr2.png” only the electronic inventory displays.
https://wrlc-gwu.primo.exlibrisgroup.com/permalink/01WRLC_GWA/1b1hkge/alma9912376416404101Compare with an IZ in the same consortia which has disabled dedupe/frbr to prove that physical inventory exists.
See “disabled dedupe frbr1.png”
https://wrlc-amu.primo.exlibrisgroup.com/discovery/search?query=any,contains,doing%20bayesian%20data%20analysis:%20a%20tutorial%20with%20R,%20JAGS,%20and%20STAN&tab=WRLC_P_AU&search_scope=WRLC_P_AU&vid=01WRLC_AMU:prod&facet=rtype,include,books&lang=en&offset=0See “disabled dedupe frbr2a.png”…
259 votes -
Display 6XX fields with $v form subdivisions intact
Primo VE is configured to map 6XX $v form subdivisions to a separate display field, breaking the subject string. In some cases, the form subdivision is plucked out of the 6XX, leaving the surrounding string incomplete. For example:
600 10 $aO'Keeffe, Georgia, $d1887-1986 $vExhibitions
displays in Primo VE as:Subject O'Keeffe, Georgia, 1887-1986
Genre Exhibitions
651 #0 $aRome (Italy) $vMaps $vEarly works to 1800
displays in Primo VE as:Subject Rome (Italy)
Genre Maps
Early works to 1800And so on, for all 6XX $v form subdivisions. This cannot be reconfigured. Additionally, each occurrence of the form subdivision is displayed…
250 votes -
Automate SSL/TLS certificate management
For hosted Primo sites that have custom domain names, the current process for deploying SSL certificates involves time-consuming manual steps and hand-offs, many of which must be repeated each time a certificate is renewed. [1]
Several institutions will soon require SSL certificates to be renewed every 90 days, at which point the current manual process will become utterly unmanageable for both Ex Libris and its customers. [2]
I propose that Ex Libris adopt an ACME-like service (such as Let's Encrypt) to fully automate SSL certificate management. The customer's responsibility would be to set up a DNS record (as they do…
204 votes -
Primo VE: Re-instate the A-Z browse function for DATABASES
Re-instate an A-Z browse option for Primo VE Database Search, like the one available for Primo Classic.
201 votesThank you for this idea. We are currently examining it also as part of the NERS voting (7820).
-
Improve Browse by Subject (Primo VE)
In Primo VE, only one of “vocabulary” is available - “Library of Congress Subject Headings.” The choice to use this “vocabulary” is automatically made for you when you choose “Browse by Library of Congress Subject.” The index “Library of Congress name authority records for 651” is not available through this search as it is through the Metadata Editor via Alma. Thus, many, many LC subject headings cannot actually be browsed in Primo VE. Example, you can find NO headings beginning with “Colombia – Commerce,” because there is no LC subject authority for “Colombia – Commerce” or for any further subdivision…
201 votes -
Control Purchase Request Display in Primo by Material Type
Using display logic rules there is no easy way to show the Purchase Request link based on material type. We want to enable the purchase request link for ebooks, but not ejournals. I did come up with a hackey workaround by creating a GES that only does the identification of the journal and then a display logic rule to hide the purchase request if this GES is present, but there seems like there should be a better way to do this?
193 votes -
A-Z option in Primo VE Journal Search
Add an A-Z browse option for Primo VE Journal Search, like the one available for Primo Classic as of the May 2017 release: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/030Highlights/028Primo_May_2017_Highlights#Support_of_Alma_Journal_Search_%28New_UI%29
184 votes -
Hide completed purchase requests from the Primo MyAccount
Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.
177 votesHi all,
We would like to update that we are planning to add this functionality to the Primo Next Discovery Experience User Interface.
We are currently evaluating it together with the Alma team.
More details on the plans for the new interface can be found here:
Best regards,
Yael.
-
Results for e-resources when narrowing down to IZ
The users expect that with the facets, you would be able to filter electronic resources by library and/or IZ that licensed them. This is currently not the case. When filtering by location, e-resources (incl. external data sources) are not delivered as results.
Electronic resources should be recognized by Primo as owned by libraries and institutions like physical resources. We would highly appreciate if Ex Libris could make this possible.
163 votes -
Improve Display Logic in Alma Uresolver to show all variant coverage statements in a collapsed menu
Ideally, Alma should be able to display ALL unique variant coverage statements when showing a collapsed menu.
If a library uses the Display Logic rules to for example show Proquest as an option only once in a services menu, this works very well where a journal may be in 12 Proquest databases with the same coverage.
However, when the coverage varies significantly between these databases, Alma uresolver will still just show one of the coverage statements and a user will only see a subset of holdings and believe this is all the library has. (eg Nursing standard in Proquest is…
159 votes
- Don't see your idea?