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.
647 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.
61 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 -
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 -
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 -
Reconcile top-level facet selection (one by one vs. multiple)
Currently, if you select top-level facets one by one (e.g. "Peer-reviewed Journals" then "Full Text Online"), you get different results than if you select both facets at once (using the checkboxes and clicking "Apply Filters".) The first applies a boolean AND and the second applies a boolean OR.
Ex Libris support has confirmed that this intended and expected behavior.
This functionality seems confusing to both our patrons and staff. I think I can see the argument if this occurs within certain other facets (e.g. Resource Type), but because this happens with top-level facets that do not otherwise seem like the…
60 votes -
Make is possible to display Available From Date and Available To Date to users in Primo
The "Control the Availability of Portfolios Automatically at a Pre-defined Date" feature, introduced in the February 2023 release (https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2023/Alma_2023_Release_Notes?mon=202302BASE), allows libraries to enter an Available From Date and Available To Date in portfolios, and the portfolio will be automatically deactivated after the Available To Date. This feature is designed to be useful in cases where libraries lease a piece of content (typically, a streaming film) for a limited period of time.
In this Idea, we suggest that we should be able to display the Available From Date and Available To Date to end users in Primo. This is…
60 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…60 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.
60 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…
60 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…
60 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 -
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 present59 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 -
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 -
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 -
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.
57 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…
57 votes -
Generate a report of the MMSID's harvested by Primo Back Office
We would like to be able to generate a report of the MMSID's harvested by Primo Back Office.
56 votes
- Don't see your idea?