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.
562 results found
-
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.
430 votes -
Primo VE: add option to mark all Display Fields for Search and Facet
Primo VE has a standard out of the box mapping of Display Fields, Search Fields and Facets (see https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/050Other_Configuration/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record). Customers cannot adapt or create Search fields and Facets. This is only possible now for Local Fields. I don't understand why this is not possible. Please provide options to mark Display Fields for Search and Facet and to create Search Fields and Facets, just like for Local Fields.
180 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.
62 votes -
Display multi-lingual values in facets in a consistent order
Currently, same values in different languages in multi-lingual facets (topic, author) appear randomly.
We suggest to create a consistent language order independent of the sort by_size configuration option, so that the values in these facets will be displayed by the determined order. For example, if the order will be: Latin, Hebrew, Arabic, Cyrillic - the values will always be displayed by this same language order.
See example image provided for the following search:
https://haifa-primo.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,gibran%20kahlil&tab=default_tab&search_scope=books_and_more&vid=HAU&lang=en_USWe are suggesting that for the facets set by size in the View, the same value in all languages will be grouped together and displayed one…
44 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 -
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…
206 votes -
We would like patrons to be able to view their library barcode in Primo.
Under My Library Account > Personal Details, we think patrons should be able to view their library barcode number. We use ours in additional systems, and we think it would be helpful to point someone to their library account details.
120 votes -
error page for samlLogin internal server errors
Currently any SAML error on POST /primo_library/libweb/samlLogin results in internal server error response (HTTP 500) and shows a corrupted paged from the old UI (see attachment)
Please implement a SAML NUI error Page for these types of errors including the SAML Error description which is currently only written into library_server.log files, e.g.:
2019-09-17 08:36:39,773 ERROR [t-ajp-bio-7701-exec-19] [c-Saml20MessageValidators] [O -(540627545,1652141697,null)] - SAML failure: This reponse samlSessionId does not match ours
2019-09-17 08:36:39,773 ERROR [t-ajp-bio-7701-exec-19] [c-SAMLLoginServlet] [O -(540627545,1652141697,null)] - SAML failure: Response was not verifiedEvent though the end user may not understand the technical details, theses SAML messages are at least…
72 votes -
Add filter for "Available Now" (i.e. not checked out etc.) to Availability filter/facet
The Availability filter/facet in Primo VE currently includes options to limit by "Available online" and "Held by library". It would be helpful if these options could be further refined to enable filtering to materials that are actually currently fully available/accessible -- for example, not checked out to another user or in another out-of-library processing status. This is functionality that I see in other library catalogs, especially for electronic resources/ebook collections.
165 votes -
"Search within results"
We would like to propose a "Search within results" option for Primo. "Search within results" would be a keyword search across all fields present in a user's results list. This is an option offered in common databases, such as Web of Science, so it is something users expect. We feel this search function would increase Primo's usability particularly for inexperienced users.
120 votes -
Increase Primo search capability to support major common search expansions on synonyms.
Salesforce case #00583901 refers (unpublished)
Ex Libris advises that, due to performance considerations, Primo search is unable to support the search expansion for the spelling variants that include the use of 's' or 'z' within a word. This is a common trans-Atlantic spelling variation, and omitting it has a significant impact on search results.
Example: a search for the terms “practice globalisation” produces 441,248 results, but by changing the 's' in globalisation to a 'z', Primo produces an additional 12,000 search results.
209 votes -
Alternative Coverage & Newspaper Search in PCI/CDI
We rely on PCI alternative coverage for maintaining the best discovery layer as this enables full text access to results obtained from known-item searches and topic searches. Using both PCI alternative coverage and the Newspaper Search together present challenges. Using both of these options together result in too many false positives; false positives disappoint users and erode their trust in our discovery system.
Please consider including the Newspaper Search with the regular Primo Central updates that are compared against our institutional electronic holdings file so the Availability statements are correct. As we look ahead to the introduction of CDI, please…
58 votes -
Network Zone suppress dedup/frbr should have a library/location tree
The Network Zone should have the ability to suppres dedup/frbr at the library>location which exists when suppressing dedup/frbr for IZ only bib records from displaying in Primo VE.
IZ only bib records suppress dedup/frbr allows a library to suppress on the permanent physical location in a library. New records added to the location automatically suppress dedup/frbr in Primo VE once this has been configured.
For NZ linked records using the Network Zone, suppressing dedup/frbr for an library/location in the network means multiple steps and constant updating are required from an institution and Network Zone. A local extension needs to be…
54 votes -
Penalization date visible in users' loan page
Hello! It would be great once we had read the bar code of the user, and we have the general information to do a loan or a return it will be great if there we can see the date until they can't borrow books. If not it is a problem because they ask you until when they are ban and we have to go until their profile to penalty section to see it.
Thank you!
41 votes -
Display Copy ID field in Get It
Alma has a Copy ID field but it does not display in Primo in the Get It section. This value should display. It does not have to be in its own column, it could be concatenated with a label of "Copy" and show in the Description column. This was possible in the Aleph/Primo configuration.
57 votes -
When an item has representations for use in Leganto that are suppressed in Primo VE, remove the View Online section
Currently we have print books with digital representations attached in Alma, for use in Leganto. We suppress these representations from Primo by using a note and display logic as this is the only option currently available. However this means that the book in Primo shows an "available online" status in the brief results, and when the full record is opened there is a View Online (GetIT tab) section that is just blank. Returning to the brief results then shows "Check available services". This is very confusing to users. We would like to have a different method of suppressing that means…
53 votes -
Primo Back Office: In a consortial environment, Ability to localize Alma collections to a specific instance of Primo
Hello.
Our university system is in a consortial configuration of Alma and Primo Back Office.
Currently, we cannot use Alma collections because one university's (local and institution-specific) collections display in all other Primo instances in our consortia. This is problematic and confusing because a collection at University A displays in University B's Primo as if it were University B's collection. But the collection is local and specific to University A only.
The "collections" I'm talking about are described in the following Exlibris documentation: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/050Managing_Collections
https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/060Back_Office_Guide/060Configuring_Primo%E2%80%99s_Front_End/050Collection_DiscoveryWe opened Salesforce cases 00636941 and 00708998 and were told by the Exlibris analysts that…
55 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.
304 votes -
Differenciating the code for PCI records from the code for Alma records
The PCI records that we don't subscribe and the Alma records without holding show the same labels on Get It section because they share the codes, such as:
c.uresolver.getit2.holdinglist.empty.top
c.uresolver.getit2.holdinglist.empty.signedinuser
c.uresolver.getit2.holdinglist.empty.signedinuser.noservices
c.uresolver.getit2.holdinglist.empty.guestuser
c.uresolver.getit2.holding_list.empty.bottom
(Samples are on SF #00731305)We want those two groups of records to be distinguished from each other so that we can apply different labels giving more customized information to our patrons.
37 votes -
Primo VE: Campus facet
For larger libraries, it would be helpful to have a Campus facet, as a superstructure to the Libraries facet (which can be very long). Unfortunately, this cannot currently be created as a local facet.
41 votes
- Don't see your idea?