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
-
An option to move the send-to section in Primo VE
We would like to be able to control the location of the send-to section in the Primo VE full record display.
101 votes -
Optimize call number Advanced Search
Currently you can conduct an advanced call number search, but there are a few issues with it:
-It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.
-The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of…
72 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 -
Add 245 subfield c to Primo display
Please add the 245 subfield c to the display in Primo. It does display in Alma. In the example below, you are not able to determine the author/creator's responsibility for the work - Author vs. forward vs. photographer.
We would love to have more granularity in general for what fields/subfields display in Primo for our specific institution.
Thank you!
87 votes -
Allow libraries to review PCI metadata in collections
We would like the ability to not only see more information about the collections (which is already another idea on here) but also the ability to see the metadata for each collection. For example, for Kanopy, we have loaded the MARC records into Alma, but would like to review what the metadata for the PCI collection looks like so we can make a decision about whether or not to enable it. We have no way to know what the PCI collection will add or do until we turn it on in production Primo.
50 votes -
EZProxy (Primo institution wizard) more granular application against specific collections
Currently in Primo institution wizard (Primo Home > Ongoing Configuration Wizards > Institution Wizard > Delivery Base URLs) you can enter an EZProxy base URL. If a proxy is added it will be applied to all Link in Record type resources (though there is the option to exclude OA collections). I would like more granularity so that we could choose to apply the proxy to certain Link in Record type collections, but not to apply the proxy to others.
120 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 -
my account - loans sort options
User should be able to sort their loans not only by title and due date, but also by author, location, maximum renewal date and status (renewable or not) -> all columns shown should be sortable.
238 votes -
Ability to share favorites
We'd like to see a more robust favorites area, with more options for configuration. One thing in particular we'd like would be the ability to organize lists of favorites, then to share those with other users. This has been brought up by librarians who'd like to work on lists collaboratively and then share those lists with students or instructors.
51 votes -
Find e-Journal by Title search
Add the following radio buttons to the Find e-Journal by Title search:
*Contains
*Starts with
*Exact194 votes -
Combining searches from search history into a new search
My colleagues misses the functionality from our previous discovery system to combine searches in the search history list into a new search in an easy way, e.g. S1 AND S3
95 votesThis is currently not planned to be developed. We might evaluate it again in the future.
Currently we are removing the "Under review" status.
-
Add an Abstract resource type for the Primo Central Index
Primo Central Index contains many records for abstracts of conference papers that have been published in journal issues/supplements.
These records are given the Article resource type in Primo. This confuses users, who when they find these items expect a full-length article instead of a short abstract.
It also creates problems with link resolvers, which attempt to generate article-level links and fail (publishers usually do not provide these abstracts as individual articles).
To fix this, Primo Central should be given a new resource type for abstracts.
The sources for these records are usually large indexes such as Scopus or Web of…
171 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 -
“My Favorites” pin should indicate number of records in favorites
In the Primo New UI, there is the “my favorites” pin icon at the top right of the screen (screenshot below of the pin). We ran some usability surveys and found that users would like an indication, via the icon, that something is there. Like the number if pinned items and/or a different color indicating that something is there.
45 votes -
Primo Central Index ( PCI ) - more granularity in excluding content from activated resources - e.g. exclude from index by resource type
Right now in Primo Central Index the customer can either activate or not a resource. But sometimes more granularity would be appreciated. Namely adding a filter by resource type allowing inclusion or exclusion in the index would be very useful. Please note: it's not a matter of adding a resource type in PCI. It's a matter of excluding records with a specific resource type from activated resources.
For example, some resources/data sources contains not only articles, but also journals and other resource types we actually catalogue. Since right now dedup does not work between local records and PCI, this ends…
100 votes -
text
Allow users to text themselves call number/location for an item
193 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 -
Put useful data into the RSS feeds created by Primo
Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.
Let's start with the feed header:
Primo delivers <rss version="2.0">
The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
https://tools.ietf.org/html/rfc4287
It is simply the better option for may reasons.
http://www.intertwingly.net/wiki/pie/Rss20AndAtom10ComparedThe description of the feed is <title>Records from Primo</title> .
As a user I would like to see my search terms in the feed title - like in…55 votes -
Allow Primo to comply with the "force password change on next login" setting in Alma for internal users
Alma has the internal user setting "Force password change on next login". Primo does not comply with this setting, so there is no way to force patrons to change their passwords in Primo. This is problematic, because our internal user accounts have a very insecure default password initially set for them. Please consider implementing this feature for Primo
182 votes -
Allow for consistant customizations in the new UI
The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
We want to implement extensions for functionalities like:
• Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off…205 votes
- Don't see your idea?