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.
563 results found
-
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 -
Field Pickup in Resource sharing form with default to leave blank
Now in the Pickup field, the first library in alphabetical order always appears by default. Many users click ENTER without having correctly filled in the Pickup field.
The best thing is that this field, even though it is mandatory, by default remains blank in opción, to force the user to choose.61 votes -
Primo Header is cut off at a certain Window Size
When one reduces the size of the browser window, the button for the advanced search moves into the “hidden” menu. Right before it disappears, it is cut off and can no longer be read. Furthermore horizontal scrolling is required in order to visually grasp the other menu items such as "Login" and "Menu". As far as we could check, this affects a browser window size from around 600px to 800px.
This does not depend on local CSS modifications. It is a general UX issue that affects responsive design and furthermore is breaking with the WCAG accessibility guidelines (WCAG 2.1, 1.4.10, …
61 votes -
Enable person entity functionality at the view level
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from…
61 votes -
comment request
Add comments on the request in the user's account
We would like that the comments which are written by the user are apparent in the user's account.
See attached files for more explanations.
60 votes -
Change the normalization rules for local resource type book
Change the normalization rules for local resource type book and create a new publiction type called Monographic series. The OTB rule in Primo VE is (Leader(06-07) = ac or ad or am) OR (Leader(06-07) = ab|ai|as AND 008(21) = m): 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
This rule should be created for Monographic Series:
(Leader(06-07) = as AND 008(21) = m)
We also think that ExL should reassess their rule and exclude this part: (Leader(06-07) = ab|ai|as AND 008(21) = m) and set up a new rule for monographic series (check:https://www.loc.gov/marc/bibliographic/bd008s.html). The codes for ‘ai’ and ‘ab’ are so rare we think they…60 votes -
Embargoed resources displaying in Primo
Currently records from within an embargo period are discover-able to end-users via Primo.
The user then thinks we have access to the records and selects it only to be presented with No full text available.
Embargoed records are outside of our coverage range and should not display in our discovery interface.60 votes -
Add MODS template as Date Source for OAI-PMH harvest
Currently, there is no MODS template for OAI-PMH harvesting of external collections. As an example, we have many collections in an Islandora repository and have very rich metadata in MODS format. We lose most of that metadata when the collection is harvested because we must use the DC template as the Source format.
60 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 -
Show number of results in Search History
It would be useful to display the number of results associated with a search query when viewing Search History in Primo VE.
59 votes -
Primo does not work with some date formats used for old material and rare books.
Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.
Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are…
59 votes -
CDI records: please provide us the ORCIDs in the PNX record in a usable form
Unfortunately, we have received the following case response: "We have reviewed your request with our content operations team and determined that our system is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement."
So we hope to get support for our proposal in the Alma community.We are currently working on making the ORCID more visible in our Primo (incl. linking to the ORCID entry of an author).
We are glad to see that CDI records already contain the ORCIDs in the PNX record.
Unfortunately, they cannot be used…59 votes -
Allow admin to select in what order Resource Types are displayed
Currently the Resource Types can only be arranged alphabetically or by count (how often the type appears in search results). We would like to be able to preference certain types above others (for example, books, ebooks, articles...over things like Text Resources. So that for any search, the Resource Types are always arranged the same way and in a way that is most helpful for users.
58 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 -
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.58 votes -
Option to create additional links for records from external data sources in Primo VE
At time, in Primo VE, it is only possible to create a link to the resource and a link to the thumbnail in the Import Profile for external data sources. In Primo with a BO, however, it is possible to create nearly as many links in the PNX links section as you like. We use these links a lot for the records of our many different data sources, e.g. create links to an abstract or tables of content, links to related titles, and many mores. These links help to enrich metadata and are user friendly. Therefore, we suggest that in…
58 votesHi all,
This is to update that this issue is currently not planned. We will evaluate it again for next year's road map.
Best regards,
Yael.
-
Show the terms added to the patron's query by the linguistic features (i.e. stemming, synonyms etc.)
As default behavior, Primo not only looks for the patron's query, but enriches the original keywords of the user with additional terms, in order to improve the performance.
The system first tries to guess the language of the query, and then tries to enrich it, using a variety of steps described in the Linguistic Features section of the documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/120Linguistic_Features
For example, a query for the string: Birne
if recognised as German, is enriched with following synonyms (dictionary file as to March 2017):gluehbirne(normal),gluehlampe(normal),lampe(normal),leuchte(normal),leuchtkoerper(normal),haupt(normal),kopf(normal),ruebe(normal),schaedel(normal)
The point is that the whole thing is a blackbox for both the librarian and the…
57 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 -
Enhance DC XML normalization routines for external sources (PrimoVE)
In Primo Back Office, there is 86 inbuilt transformational routines for MARC21 and Dublin Core data normalization (e.g. “Take first words”, “Get highest number and normalize last digit”, and “Remove HTML tags”). Most have been translated for MARC21 in PrimoVE by various people but, because of limited regex and Xpath functionality, few have been translated into Dublin Core XML normalization routines for PimoVE.
We would like to see the implementation of full regex and/or XPath / XQuery functionality (or similar) to allow all Back Office normalization routines to be created for PrimoVE.
57 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
- Don't see your idea?