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.
712 results found
-
Cross-Institution favorites
In a consortial environment, we would like to see favorites shared across institutions.
Currently, favorites from institution A are only visible when logged into institution A but not when logged into institution B and vice versa.
Our desired behaviour would be that all favorites from all institutions are shown, regardless of which institution a user is logged in to.
4 votes -
Research Assistant: please allow to link external website for help pages
The current RA help page is built from the contents of code tables, but this doesn't give much flexibility in lay-out, to include images etc. Our question is that institutions also have the possibility to link to their own web pages for documentation and help.
5 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 -
Improve call number Browse search
To improve the user experience in Primo VE, we propose modifying the call number browsing feature to show a few call numbers both before and after the searched call number, providing better context and making it easier to locate desired items.
5 votes -
Feedbacktool to provide extra info from the Primo record in the Subject of the message
Additional context information of the record such as the source (Alma, CDI, external source) allows problem reports to be dispatched more efficiently to the relevant person / service that can solve the problem.
Our use case is the following: external sources (like institutional repository, archives,..) that are imported into the library catalogue are not managed in Alma. Questions about these records need to be forwarded to the managers of these sources, often to other departments outside of the library. The user is usually not able to make this distinction between records of different sources, so the use of categories is…
24 votes -
Discovery collections handling
When creating or updating an Alma collection (adding/removing titles), the change is not automatically reflected in the Discovery Collections and it is necessary to trigger the reindexing for a correct display.
This workflow is problematic when titles are removed: records are taken out from a collection but are still present in Primo VE because a reindexing is needed. They can no longer be found by searching for the collection in Alma. Depending on the collection, it might also not be possible to find them all via a single search and it might be necessary to manually add the records to…100 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…13 votes -
Add support for custom repositories for citation styles
It's possible to manage and include additional citation style languages, which are stored in GitHub’s CSL Style Repository but they have a huge backlog to add new styles. It would be better if Ex Libris add support for custom repositories for citation styles.
2 votes -
Allow GES to access coverage information to calculate available services for articles
Our library uses GES service availability rules to disable our ILL services request link for articles “when resource is owned by the institution and available.” However, GES interprets a journal as available if we have coverage for any length of time, even if coverage is not available for the article in question. This leads to a number of CDI articles showing “No services available,” as we do not have an available link for access (not having coverage for that particular date/issue), and the ILL link is disabled because the system thinks we have coverage. It would be helpful to have…
3 votes -
Link to Reading List in Leganto at "More from the same Course" in PrimoVE - allow for the link to possess course code instead of course name
Currently in PrimoVE, when a title is present on a Reading List in Leganto, at the "More from the same Course" area of the title search result, the link to the list in Leganto possesses the name of the course and not the course code, which is more meaningful to our users. It would be great to have the ability to change this information which is not currently available.
3 votes -
Create scopes/search profiles of Open Access CDI content
We are starting to promote Open Access content and would like to create a view that holds only this content. Alma currently allows you to create custom/local scopes that are associated with being OA. OA information does exist within the CDI, but there isn't a way to filter it into a scope or profile.
3 votes -
Feedback tool : option to integrate with ticketing system via webhook
We'd like to integrate the feedback button with our ticketing system via webhook instead of via sending mails.
We expect this will give better opportunities for integration eg. mapping the e-mail address of the customer to the customer e-mail address field in the ticketing system.
See also
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/45350419-feedback-tool-for-primo-ve-allow-user-s-email-as22 votes -
Inform patrons about Pick from Shelf
This is something we are really missing since we switched to Primo VE.
I find a book I want to borrow, my library has it, but it's open stacks, which means I can't request it online to be picked up in the owning library.
In our older catalog we had a pop up message to inform the patrons that they can fetch the item from the shelf themselves.
DTU (https://findit.dtu.dk) solves it like this, which is exactly what we need - see screenshot dtu1.png
Under B, we'd show the possible pickup locations, as we do now.
A is…
43 votes -
Display requester note for purchase requests in "Requests" tab of "My Library Card"
Users who submit purchase requests in Primo VE put information in the requester note explaining why they are interested in an item. It would be useful for them to be able to review that note later (especially if it takes a while for a purchase request to be processed and they need to be reminded why they submitted the request), but users without access to the purchase request module in Alma have no easy way to review that information in Primo VE after they submit their requests. It would therefore be helpful for the "Requests" tab of "My Library Card"…
2 votes -
Influence the algorithm in the display format for hits on large broad subject searches where local repository records appear.
In our library we have decided that Primo should also display records from a local repository. This is a database of references to research publications produced by our researchers at our university. It is not always the case that we have electronic access to the titles in this local database. And it's not always the case that we own the physical works.
So we would like to have the titles in our catalogue, but we are well aware that at best they are reference titles that have to be obtained/borrowed.
We are planning to display more local repositories through our…9 votes -
Share on social media: add Mastodon and Bluesky
Share on social media from full title display:
Please add Mastodon and Bluesky as options.
Can't speak for Threads as that's blocked in Europe, but would probably make sense to add it at the same time.
174 votes -
Add more granular CDI suppress settings per electronic collection
When Ex Libris changed the "Exclude CDI ebooks" setting to allow ebooks from Database type collections through, we ended up with a lot of duplicate ebook records. The only way to fix that is to select "Do not show as Full Text available in CDI even if active in Alma" for each of our ebook collections. However, that suppresses everything from the filtered search, including book chapter records. I'd like the ability to only suppress the CDI ebook records per collection.
I understand the need to allow ebooks from Database type collections through, but we've got to come up with…
3 votes -
Allow conditionality/logic toggles for fields in Primo Forms
Description: Currently the Resource Sharing Request form is fixed/non-customisable in the options available, e.g. format everything is available Digital or Print. However, for some circumstances we need to hide the options that don't apply to the request being made (see use case below) Given that conditionality/logic toggle is in the form for the chapter fields, this would is an additional application of the existing functionality in Primo forms, but that we could control.
Use Cases: Where we can only provide a resource type in one way (print or electornic) we want the selection of resource limits the format type appearing…
1 vote -
Develop web browser bookmarking tool/extension for pre-populating Purchase Request
With the recent development of the Order It tool, we have realised that for our purposes, we would like to have a similar toll available related to Purchase Requests.
Quicker, easier more accurate.
The form would help keep things accurate without giving access to order it to ordering librarians and help us utilise the requester information in the purchase request form (ours is behind a login and restricted to set user group)
The tool would grab and place the metadata from websites such as amazon, waterstones, and our suppliers, place the information into the purchase request form (which for us…
1 vote -
Collection discovery - have an alert when using unsupported elements such as emoji
Hello,
In Alma Under Add New Collection Fields for Name and Description fields: "Non-text characters such as emojis are not supported."
In fact, they cause a major side effect : the codes are then no longer translated into labels throughout Primo.
I suggest:
- either correcting this dysfunction
- or, if emoji are prohibited (I'm personally not a fan of them for corporate communications), setting up an alert for the user when they attempt to include them in the relevant fields.
Sincerely,1 vote
- Don't see your idea?