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.
77 results found
-
Add a job that can set the CDI option collectively
We would like you to add a job to set "Activate for search in CDI" collectively for the electronic collection set of CZ.
Also, please add a job to batch update the following CDI options for the electronic collection set of IZ.
- CDI Search activation status
- We subscribe to only some titles in this collection
- CDI-only full text activation
- Do not show as Full Text available in CDI even if active in Alma0 votes -
Show last edit date in Manage Customization Package tab for Primo VE View
Currently, the manage customization tab shows no information about when the package was last updated. I suggest adding information in the display area that shows "Package last updated: YYYY-MM-DD," preferably with the user's id.
5 votes -
Add to Primo Backend BE tools for counting and migrating (= export and reimport) user comments
As Primo administrator we have no tool
1) allowing us to know how many user comments are in the system (to have an idea on how this feature is used and therefore useful
2) allowing us to migrate user comments in case there is a change authentication system and metadata. For example, we switched from a case sensitive to a case unsensitive authentication platform and, since user comments in Primo are linked to user via the ID used for authentication, we could not export them, manipulate and fix the users, and reimport them.
Therefore a way to export / reimport…3 votes -
Make persistent search history opt-in instead of opt-out
Make Persistent search history an opt-in instead of opt-out when enabled by a library.
If a library enables the persistent search history in Primo VE, the feature is automatically turned on for all patron records. It would be helpful if patrons who would like to use the persistent search history feature could choose to opt-in to it instead of requiring users to opt-out of it.
4 votes -
"Feedback Tool" for the New Primo UI: Configuring the Feedback Letter - please support multilingualism
There are already pre-defined labels for the e-mail in different languages (e.g. default.report.emailTextNoEmail) but they are currently non-functional :-(
Configuring the Feedback Tool for the New Primo UI
https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/New_Primo_User_Interface/Additional_Features_for_the_New_UI/Configuring_the_Feedback_Tool_for_the_New_Primo_UI
"Note: Only the en_US descriptions are supported for email labels, and no translations are provided if configured in the table."According to Production Management, implementation is not planned for the time being and we should raise an idea.
So, please vote for this idea ;-)13 votes -
Send an automated confirmation email after a booking request has been successfully placed
Currently Primo has a nice feature that allows patrons to book items after they log in to their library account. It is called booking request in Alma and Request Item in Primo. We use it to let our patrons book equipment. However, it doesn't send out an automated confirmation email after a booking request has been successfully placed. We request to have this feature (i.e. the system sends out an automated confirmation email to the patron after a booking request has been successfully placed).
4 votes -
customization package API
Please add an API to deploy customization packages in Primo VE so that customers with many views can automate the cumbersome deployment process.
0 votes -
API for customization package deployment
Please add an API to deploy customization packages in Primo VE so that customers with many views can automate the cumbersome deployment process.
53 votes -
Transformation routine to convert number range to list
Have a transformation routine that will convert a range of numbers to a list. For example
input: 3-8
output: 3,4,5,6,7,8This would be very helpful in the search section, as users often search for a series and volume number, but if the series number is in a range they won't find it. E.g., this search will fail
Series entry:
The big series, v.24-35user search:
big series 31With the new transformation, the search section of the pnx would have
The big series, v.24,25,26,27,28,29,30,31,32,33,34,35
and the search would work.13 votes -
Allow Primo/Primo VE View customization packages to accept .db files and .DS_Store
The view customization packages for Primo and Primo VE do not allow .db files. When someone opens a folder with images, Windows automatically creates a hidden Thumbs.db file. MacOS creates similar .DS_Store files.
This file can be difficult to remove even with rights to view and delete the file, since Windows will sometimes indicate the file is in use and cannot be deleted.
Rather than jumping through hoops to recreate the customization package structure and carefully place images only in the desired folders never to be opened again, I would propose that Primo and Primo VE accept customization packages that…
7 votes -
Make handling of multilingual labels easier
Hi
Our Primo VE has 4 interface languages.
1)
Changing a term means I have to change it in each language separately, save it (which throws me out of the table to the list of tables), click 'edit' again, then change the next language etc. Otherwise the changes are not taken.Surely there's a way to make that easier?
For example display all languages at once, which would also make it much easier to compare the languages.
2)
After I changed a label, when I search for it, I still get results, although it does not exist any longer in…10 votes -
En Alma Digital se requiere que los campos MARC 5XX se desplieguen diferenciados
En el perfil de metadatos desplegados en Alma Digital, se requiere que los campos de notas se puedan diferenciar. Actualmente se unen los campo 505 y 520 en "Descripción" y todos los otros 5XX en "Notas".
6 votes -
Add a Deploy button to all screens that require a deploy
So may times we forget or don't know that a deploy is required for a change to be implemented into production.
- It would really nice that any feature that requires a deploy a deploy now button be included on the screen (some sections already have this feature)
- It would be even better if there was a banner at the top of the admin panel if there were changes that require a deploy to implement pending so that Administrators can easily see that a deploy is required.
1 vote -
Primo - Set up display logic rules - document type level
Set up display logic rules not at the level of a target or a service but at the level of the document type:
in particular, no more link or SFX service to be displayed when document type is dataset or patent, it seems SFX does not know how to process datasets metadata.1 vote -
Searchable Training Videos
Enable the content of all training videos to be retrievable when searching the Ex Libris Knowledge Center. This would improve training by making the video content more accessible. By indexing audio transcripts of training videos, customers can more easily retrieve information relevant to their query and help ourselves.
3 votes -
Normalization Sets Change Control
It will be nice if we have a Normalization Sets Change history including:
- what changed on a normalization set old and new value
- who change it
- when has been changed
- possibility to revert to the previous version
3 votes -
add otb support for iso 639-3 languages in Primo
Primo currently supports iso 639-2 values for languages.
We would like a support for the broader iso 639-3.
Iso 639-3 is much richer.
For example in our library we have more and more materials written in Ladin of the Alps, which is not the iso 639-2 Ladino (a language with the same name but spoken in Spain) but is instead the Ladin lld in iso 639-3.
As a language iso 639-3 lld is a subset of the broader iso 639-2 roh family. But using just roh is quite a lack of granularity for us.Other customers around the world may…
4 votes -
Remove the character limit for the Resource Recommender Description field
Currently, there is either no limit or a large limit on the Description field of the Resource Recommender when files are uploaded from Excel.
However, if you open an existing Recommender to edit something (fix a typo, add additional keywords, update a URL), you are not permitted to save unless the Description field has fewer than 300 characters. This means I opt not to fix my typos, and I have to spend the time to rewrite the description to fit into <= 300 characters in order to update a URL. I find this limitation very frustrating.
Please either remove or…
140 votes -
Resource Recommender: "truncation", "starts with" and "part of" tags
Enable more functionalityfor tags. Currently we have a database for laws. Nobody search for law, laws etc. We want the option to make the database searchable with tags like "law of; "law for" "comonlaw" etc. I cant put in all the laws and synonyms as tags.
So it would good for users to get a match on all those things.19 votes -
Determine source for Autocomplete-suggestions in a blended scope
In Primo you can activate autocomplete to get suggestions for search-queries based on what the end-user begins to type in the search-box.
We have tested the functionality and see that it could be useful for the end user to get these suggestions. However we see that the suggestions from the central index in some cases are a little strange and that you get suggestions from the entire index and not only the sources the institution has activated. This means that the end-user could get suggestions that gives 0 results.
The local index suggestions seems to be a lot more accurate…
135 votes
- Don't see your idea?