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
-
copy a normalization rule set from sandbox to production server
We need the possibility to tranfer NR testet in the sandbox environment to the production server.
8 votes -
unix-like tool for working with normalization rule sets
to compare two normalization role sets or for finding spezial references in a rule set we need some tools:
- to compare 2 rule sets we need a tool like the diff command in unix
- to find references to a (mapping) table or occurences of fields in a NR we need a tool like grep in unix
9 votes -
Email alerts when Primo BO jobs fail or complete
Add the ability to allow admins to receive or sign up for email alerts when jobs fail or complete in the Primo back office. This functionality is currently supported in Alma.
10 votes -
Send email when pipe finishes with errors.
When a pipe finishes normally, but some records did not load due to errors, right now the only way to find out whether that happened or not is to go into the back office, Monitor Primo Status, Pipe Monitoring, and click on "Errors" next to the pipe (and a futher step to get to "History" if the pipe is not the last one run).
We run four Alma pipes a day, and around a half dozen other pipes once a day. WE DON'T HAVE TIME TO DO THIS and I bet a lot of other customers don't either.
But we…
25 votes -
Backoffice REST API and Hooks
Alma provides a growing number of API's for process orchestration and Hooks will come soon.
Primo only provides REST API's which are mainly used for Frontend interaction.
Primo is missing API's and Hooks to control Tools, Pipes, Processes and Schedules to implement fully automated workflows for Alma or other ILS.
I would be great to see such API's and Hooks soon, please vote!
5 votes -
Make integration with Alma more seamless in regard to the PCI and Link Resolver
When we activate our Link Resolver databases in Alma, we have to do it all over again in the Primo PCI. This is redundant effort. Yes, it is one time, but new libraries have enough else to do to configure the system and this seems like an unnecessary step.
6 votes -
Make configurable preference of source in deduplication
Preference of records coming from differente sources in deduplication is hardcoded in Primo and it causes undesired situations, for example poor SFX records have preference over rich ILS records and the information from ILS records is discarded. Order of preference of sources should be configurable through Primo Admin interface instead of being hardcoded
78 votes -
Make Relevancy Ranking values available
To assist with the fine-tuning of Field Boosting, provide a way of showing the values of the rankings of search results.
I.e. When a search is performed, for each hit make its total ranking value viewable either
- to users,
- in a comment in the page's source HTML, or
- by amending that items URL (similar to &showPnx=true).8 votes -
Ability to administer synonyms via BO
The systemSynonyms and userSynonyms files are only available via the command line so SaaS customers have to request changes be made via SalesForce.
It would be easier to administer if the ability to view systemSynonyms and download/upload/deploy userSynonyms be in the BO.
29 votes -
Add functionality in relevancy ranking for Primo to adjust according to full text criteria
We would like to be able to adjust the relevancy ranking of the results page to display full-text versions above duplicate results that show no full text available.
Example:
This would be most helpful for sources coming from ProQuest Dissertations & Theses (PQDT), where the PQDT result shows as full-text available but results from other PCI sources (ERIC, ProQuest, etc.), show the source as "no full text available."We think this would be helpful for other situations, too.
30 votes -
Primo: ability for Back Office users to mantain their own passwords (or integrate with SAML)
Increasingly I am opening up the Primo Back Office to staff outside Library Systems, for example for people to build reports or test FRBR and DEDUP.
It would be more secure if the Back Office users had the option to change their own password rather than for me to set it.
Even better would be integration with the institution's Single Sign On service (as Alma does).
Regards,
Ciaran
Ciaran Talbot l Library Systems Manager l Red 2.6 Main Library l The University of Manchester Library l The University of Manchester l Oxford Road l Manchester l M13 9PP
@ciaran_talbot11 votes -
Allow upload of SVG image files via File Uploader
We have had some design work done for us and were supplied with a number of SVG format image files. The current Primo File Uploader does not support SVG format image files, but it should.
7 votes -
System generated email: include the domain name in the body of message
Currently system generated emails from Primo do not indicate which server they originated from. We have two servers, production and staging, and we think this is a common setup. In order to know which server the email came from one has to view the message headers. It would be helpful if the emails automatically included the domain name in the body of the message.
2 votes -
Would like FRBR member boosting to be cone at institution level so multi tenant can select default record type(e over print etc...)
Currently in a multi tenant environment some variables are only at the installation level and can't be changed. My example is the FRBR for print always shows, where we would prefer the electronic:
As total care can we do this making the Ebook or electronic version be the first on the brief display rather than the print?
2 votes -
Multilingual CT and MT: Configure inherited languages
Right now most CTs and MTs in the Backoffice are configured in a multitude of languages. The possibility to configure the languages needed by the instance and/or institution would make the usage more convenient and also save disk space.
OTB-Tables could stay the same as they are now, of course. But for at least the instance – if not even single institutions – a set of needed languages should be configurable.
18 votes -
Send e-mail to Primo administrator staff after a scheduled pipe was executed
For many customers, especially SaaS ones that does not have direct access to the server, it is very important to know if a scheduled pipe is executed or not. The idea here is that the BO server send by email a summary of each pipe execution, indicating start and finish date and time, execution status and how many records were imported / deduplicated etc.
8 votes -
Delete uploaded items from file uploader
Add an option to delete files that were uploaded using the file uploader.
22 votes
Miri.Botzer
responded
Submitted by Ex Libris PM on behalf of our customers
- Don't see your idea?