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.
66 results found
-
More contact options for "person" in Resource Recommender
Right now in the Resource Recommender, the only 'contact' option for a 'person' is e-mail. We would like more options, possibly including:
URL - This is important because maybe they have a profile page that has more information, for example, in LibGuides. Would also open up the possibility to include a URL that takes the user to a form to request an appointment
Phone number
Hours - Because we're not necessarily able to respond at all hours.
16 votes -
Improve Author Name Normalization for PCI Facets
Frequently, we encounter different facet values for the same author in PCI search results. For instance, there are some PNX records in PCI with creatorcontrib facet values of "Shakespeare, William" and some with "William Shakespeare". The problem is exacerbated when results are blended with local records.
Ideally, the name forms should be more consistent and match Primo's out-of-the box normalization rules for MARC records.
We realize this is a difficult problem to solve when ingesting metadata from disparate sources, but we believe it could be better.
14 votes -
Activation request for "Films on Demand"
When searching the Community Zone there is a record for Films on Demand (Humanities and Social Sciences Video Collection), but there are no portfolios (titles) attached to it. It's just a brief bib record.
We'd like to request an activated record (with items attached) for Films on Demand.
14 votes -
Ability to examine raw data of a PCI collection for quality assessment
Its tedious to check the quality of primo central collection. It will be helpful to have an API access to the raw data of Primo Central Collections. Collections need to be checked for quality issues e.g. resource types contained. Its important to understand the density, language, and formatting of metadata before a collection is activated in production. Please enable an API for the PNX / Metadata of the collections records. Metadata experts could then assess the quality of a collection more easily. The method would be also more reliable and convenient than checking (some) examples via the Primo frontend.
11 votes -
Library Stack added
To add Library Stack to your indexing so results will populate in Primo.
10 votes -
Incluir Miniaturas portadas Primo
Para mejorar la experiencia para los usuarios , se hace necesario que Primo rescate la mayor parte de las miniaturas de las portadas. De acuerdo a los señalado por la linea de soporte de Primo, este usa el primer ISBN y si dicho ISBN no trae en la metadata de Json el enlace del thumbnail_url, no lo coloca.
Sería beneficioso para el sistema y para los usuarios que se desarrollara este requerimiento10 votes -
776 first indicator and display
The first indicator for the 776 field specifies whether that field should be displayed or not. I added some 776 fields with a first indicator 1 (do not display note) yet this field is displaying in Primo. I would suggest that when 776 is used with a first indicator 1, this field does not display in Primo as per MARC (see link below)
10 votes -
Increase the granularity of of metadata fields for searching in Primo Central
Additional metadata fields be made searchable within Primo Central. Author affiliation, Abstract, Author Keywords, Thesaurus keywords, Chemical name, Source title, Funding information, full text, etc. The publishers and some database providers provide some or all of this information, for the publishers that do not supply the information, the field will be empty, for the many duplicate records the field information may be found in one or more of the duplicate records. It would be better to make search available for the additional fields, than over simplify search and remove the capability. Improves the level of sophisticated and accurate searching within…
10 votes -
Different identification system depending on the view
In our university we have a pending important problem to solve:
- In order to solve some Primo cases in which the user has to be identified, Exlibris technicians ask us for credentials to be able to analyze and solve the cases but logically, for security reasons, we should not give our personal credentials to anyone.
- Our user authentication is through SAML so all of our users are external in Alma.The Systems Department of our university requires that in order to create a user in the system (external to Alma), the responsibility for that account must rest with…
9 votes -
SRU Barcode
We would like SRU availability fields to include barcode. Barcode is a useful identifier for items. This addition would allow us to do things like get all the barcodes in a location and do an inventory.
9 votes -
[Primo] - allow to set up a default view, i.e. the landing view for the user when view ID is missing or mistyped
Right now the 'default' view in Primo is the 'out of the box' view, named 'default', which is normally used as template by user for creating the View actually in use. And that's fine.
But the customer should be allowed to define which view sahll be used as default View in the Primo instance. Current feature "Session timeout URL" is not enough.
- In case for example of mistyping the URL, the system leads to the 'default/otb' view.
- If a View is deleted but a user has a bookmark, again the system leads to the 'default/otb' view.It should…
8 votes -
PCI Collection List in a .csv or similiar format
It would be great to have the PCI Collection List in .csv or similar format. It's time consuming to convert it to a format that is usable. It would be great to be able to easily deduplicate with the PCI Activations export and compare from version to version so we can easily see what collections have been added to the PCI without having to spend hours eyeballing or converting the document.
7 votes -
Include an option to set Primo Alert for specific latest issue of a Journal TOC (table of content)
Include an option in Primo Alert for specific latest issue of a Journal TOC (table of content) as in the case of Ebscohost Alert Notification attached.
7 votes -
Give us a way to brute force boosting any record in Alma with a local field
We have to break the rules of cataloging to add fields to get certain important titles that should ALWAYS be first in a relevance sort to show up at the top. Give us a local field to use in a bib record to always ensure a boost to the top (similar to what we can do to "top" a particular collection to offer in direct linking).
6 votes -
Ensure a title level general hold request only activates a request on the relevant holdings and campus for correctly affilated patrons.
This crosses Alma and Primo but it surfaces as an issue for us mostly in Primo.
Currently general hold requests are not checked against terms of use. So Primo/Alma applies the request to all holdings regardless of whether the patron can borrow the item or not.
As an institution with two distinct campuses (NHS and University) we have issues with requests where some of the holdings have no items attached.
For example we have a journal that has holdings at several libraries at both the NHS and Cardiff University campuses. Some of these holdings do not have any items attached.…6 votes -
Check for physical copies between data sources
Currently records harvested from local sources (e.g. Dspace) can not crosswalk to records from Alma. This means that a patron who finds a record from dspace for a dissertation can not determine if the dissertation is held as a physical copy using the find it tab in Primo.
For example, see http://searchit.lib.ksu.edu/KSUD:Entire_Library_Collection:01KSU_DSPACE2097/18531
The view it tab works, but the Check for Physical Copy times out because Primo's code is not set up to support checking for physical copies from sources other than Primo Central.
I request that the code be enhanced to support this discoverability.
6 votes -
Newspaper index activations should be on the ejournal/newspaper title level rather than on the collection level
The Newspaper Index should be activated on the ejournal/newspaper title level rather than on the collection level.
For example if you activate in PCI a target like Gale Onefile, that has newspaper articles from a range of different titles, the result is radically different in the main Primo index and the Newspaper Index.
The main index will have this activation on ejournal/newspaper title level, so will only display newspaper articles and other content that Alma or SFX says are subscribed.
In the Newspaper Index however the activation is on the Collection level, so that all Gale OneFile newspaper articles are…4 votes -
Search with 'OR' using DeepLinks
Query params in a deep-search are correlated with "AND" by default. It is not possible to correlate two query params of a deep link with a boolean OR.
This feature could be very useful, for instance if you want to search for an author including variant spelling (think of Primo Central Index). Or to query multiply keywords via a single Deep Link.
4 votes -
showPnx page as XML
In the classic UI, if you added the parameter showPnx=true, in the address bar, to the URL of a record's full display, you were able to get an XML file with the PNX version of the record. In the NUI, on the contrary, the same parameter takes you to a web page containing the PNX record in a textarea.
The XML view of the PNX record was very much easier to manage: colouring of tags, open/close section as well as you need them, etc.
Why did you change this behaviour for worse?
Could we get back the XML version of…4 votes -
Use non-LC call numbers for journal categories
This affects Primo/PrimoVE; but the job is in Alma.
The new feature (as of Nov 2019) to browse a list of journals by category depends on the 050$a. This should be expanded to use the 055$a, 060$a, 070$a, 080$a, 082$a, 083$a, 084$a, 085$a, and 086$a. Additionally, libraries should be able to pick which of the subfields to use.
This is an example of the lack of support for non-LC libraries.
** This idea cross-posted as Alma idea. **
4 votes
- Don't see your idea?