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.
519 results found
-
Display only the last entered Date Range facet
When a person refines a date a second time in Primo, Primo simply displays an additional date facet in the Active Filters area. For example, a person initially filters a search to Years: 1919-2025 and then decides to filter again by Years: 2024-2025. Instead of removing the first date facet and replacing it with the second, Primo simply adds the second facet underneath the first facet. This does not make sense and presents a usability problem for the end user. In all other cases, when two facets are used within the same category, they are to be regarded as having…
2 votes -
Link Authorities in BIB Records to Local Authority Search Records
Current Situation: Local authority search allows patrons to search for authorities and obtain a list of BIB records to which they are connected. However, it is not possible to navigate from an authority in a BIB record to the local authority record in Primo.
Proposed Change: Enable navigation from an authority in a BIB record to the corresponding local authority record in Primo.
1 vote -
Enable Custom Configuration of Primo Normalization Rules for Local Authority Search
Current Situation: Local authority search records are currently displayed with hard-coded normalization rules (NRs).
Proposed Change: Allow users to configure Primo normalization rules for local authority search. This flexibility will enable us to normalize authority records and display fields according to our specific needs.
1 vote -
Move "change language" outside menu and leave it in English + icon
Readers who do not read the current language of the Primo interface, especially when it is in non-Roman characters, cannot find where to change language. We need the "change language" out of the menu, directly in the main screen, and permanently in English whatever the current language is. An icon [globe/flag] might also help.
1 vote -
full text
Currently "full text" is limited to first 65K characters of an article or of a complete [!] book (along with chapter abstracts only). Thus tweak results to full text is misleading. For articles, entering from google scholar may circumvent the problem partially. For books, true research now requires search full text (possibly not available or only available in snippet view) in google books for finding the required source and pages, then searching the discovery for the book for electronic access, similar to finding a physical book.
True full text is strongly required.1 vote -
"Peer reviewed" for academic books
Currently, there is a limiter in discovery to "Peer-reviewed articles" but using this limiter does not bring results from books even by the most celebrated academic publishers. While this information arrives from vendors, there should be a way to search peer-reviewed publications that would exclude magazines but include both peer-reviewed journals and books (or book chpaters) by any academic press.
1 vote -
Make advanced search form expandable/collapsable with discovery setting
The advanced search form now collapses after a search is performed. While this was an implemented enhancement request, there are times when expanding the form is more useful to patrons. For example, displaying collection records and allowing users to search within those results.
It would be helpful to either have a configurable discovery setting that allows the form to stay expanded or collapsed by default, or have a URL parameter to force the form to expand or collapse as needed.
3 votes -
Improved Display of Coverage Statements for Taylor and Francis Journals autoholdings collection.
Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
We propose to:
1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
2. Present only non-overlapping coverage statements to users in primo.
This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all…44 votes -
Ahead of print articles
I would love to see some regulations or procedure set in place for articles not yet published from being published in primo. I understand this is a vastly complex issue but curious if anyone else has had these issues as well and ideas on the topic.
Per Ex Libris
Ex Libris's goal is to reflect the provider’s content and metadata and cannot directly make changes in our databases without the provider making these changes. If the provider has sent us a record for an article that is not yet published, or not yet assigned to a specific volume/issue, you will…1 vote -
Articles not yet made available
I would love to see some regulations or procedure set in place for articles not yet published from being published in primo. I understand this is a vastly complex issue but curious if anyone else has had these issues as well.
Per Ex Libris
Ex Libris's goal is to reflect the provider’s content and metadata and cannot directly make changes in our databases without the provider making these changes. If the provider has sent us a record for an article that is not yet published, or not yet assigned to a specific volume/issue, you will see it as a search…1 vote -
Change how permalinks work
The permalinks provided by Primo do not link to a specific Alma record; instead, they save the result of a search in Primo. This means that when we copy a permalink for a title included in a course, what we are doing when using it is initiating a search for that title in the recommended bibliography collection. Therefore, if that title is no longer included in a course, the permalink we had copied stops working. This is not very useful.
We request that the permalinks provided by Primo be truly permanent and always direct to that Alma record, without changes.…15 votes -
Using FRBR local key to force certain similar records to FRBR in a group
When having records with the same title (245 a) and also very similar subtitles (245 b) or section titles (245 p) or section numbers (245 n) you may want to FRBR them (and no others) in certain (sub)groups by using FRBR local key.
Examples:
In one group:245 a Sveriges rikes lag p Processrätt I
245 a Sveriges rikes lag. n 3, p Processrätt I
245 a Sveriges rikes lag. n 4, p Processrätt IAnd these in another group:
245 a Sveriges rikes lag p Processrätt II
245 a Sveriges rikes lag. n 3, p Processrätt II
245 a…1 vote -
User name in the personal details tab
I'm wondering is it possibility to add a user name in the “personal details” tab, in one of the marked places in the screenshot (PVEMyLibraryCardAdditionalConfigOptions.png)? I tried to do it with a JavaScript Dynamic Directive, however I can't find the variable with the user name.
6 votes -
Can Note be added to the list of field search options in Advanced Search in Primo?
Adding Note to the field search options filter would enable patrons to more effectively search for titles. For example, someone searching for materials in languages not currently available for limiting searches could select Note and write Text in Tagalog or similar to refine their search. Keyword searching does this, but the results lack context and are much less helpful.
1 vote -
Stop the Alma link resolver from matching e-books and print bibs that aren't the same ed.
At present, if we have a 2nd ed e-book and a 2nd ed print (that is 2nd ed., EMEA ed.) of the same title, Primo is linking them when they are actually different editions. Ex Libris says this is because of matching via title and author and that the option to cancel this kind of match of a specific record isn't available. it would be good if we could unlink them in the Primo record
2 votes -
Dublin Core field to display external links (like an 856)
We would like to have a way to link users to external resources from a Dublin Core record, similarly to how an 856 is used in MARC. Example: a digital object in Alma could link to a related finding aid in ArchivesSpace.
Perhaps the field(s) most appropriate to display in this manner would be dc:relation, dcterms:isPartOf, dcterms:replaces, dcterms:requires, dcterms:conformsTo and dcterms:isVersionOf.. but only if those fields utilize (dcterms:URI). If any of those fields are not tagged as a URI, that field should display as it does now.We are agnostic to whether such hyperlinks should be displayed in the "links"…
9 votes -
Resource Type Filter Bar buttons: users expect them to unclick if they change the search scope dropdown
Users raised that they would like the Resource Type Filter Bar buttons to reset themselves to "All" when they repeat their search in a different dropdown scope.
This is especially relevant when the new combination of search scope and resource type doesn't give any hits, e.g. searching the print catalogue scope with the button clicked to see only electronic articles.
1 vote -
Only show "request other issue" for serials.
Presently if a title has a holdings statement attached (holdings 866 I think) or it has a description in an item record, and if the fulfillment rules allow for patron physical requesting, then in addition to item-level request links there will be a "Request other issue" link. The resulting form allows the patron to fill in additional values for chapter, page, volume, issue, part and date. Documentation refers to this as a "Request for a Non-Cataloged Serial Item." However, the link presently appears on non-serial items. Ex: https://librarysearch.williams.edu/permalink/01WIL_INST/1faevhg/alma991013241589702786
Given that this link takes you to a form focused on serials-related…3 votes -
Being able to choose "emailing and printing exporting actions" fields
The print and export options are currently limited.
It would be a lot of help if we could choose the fields that are being exported to excel (or at least add the location field there), and which are being printed. Currently, in the print version there a lot of fields (all of the get it fields) and it takes a lot of space in a printed list for a patron. 4-5 pages for 15 results. The minimum is that there will be a long version and a short one to print, but better of if we could choose which fields…8 votes -
Allow suppression of citation action based on resource type.
Some resource formats, such a patents from CDI, lack crucial information so that the generated citation is inaccurate and unhelpful. For instance, patents lack the patent number, which is present int the record but which doesn't display to patrons. We'd like to be able to suppress the citation action in Primo VE based on certain resource types.
3 votes
- Don't see your idea?