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
-
Display times in Back Office according to local timezone
Currently Primo Back Office displays all times according to the server timezone. This is particularly relevant to scheduled pipes. For smoothest operation these need to be coordinated with Alma jobs, which are scheduled against local timezones. Differences in daylight savings times mean we have to update our conversions between the two timezones at least twice a year.
Being a multi-tenanted environment, the underlying server timezone can't easily be changed. But my suggestion is to make the display of any times in Back Office depend on a configurable timezone. ie
1) Allow institutions to configure a timezone
2) Where times and…
20 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 -
"Personalize your results" - enable to add disciplines, not only delete.
"Personalize your results" is a Primo Central feature. The lists of degrees and disciplines are defined by Primo Central, and can be translated locally via code tables in the Back Office.
It is possible to DELETE degrees and disciplines via the Mapping Table, but currently it is NOT possible to add new ones. We would like tohave the possibility to add disciplines.
thank you.18 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 -
Read-only permission set for back-office users
As both a training tool and for wider understanding of the primo product, we would like to have a read-only permission profile where heads of public service or others could look up configuration/normalization settings, but not commit permission changes. As it stands now, each permission set has the ability to write to at least one area of back office. We would like a 'do-no-harm' account that senior or technically abled library staff could review/suggest changes without having the ability to make the change.
15 votes -
Add a Description Field to the Full Normalization Rules
I think it would be verry useful to have a Description Field for each Noramlization Rule so it can be easier to find which one you need to edit. This can also be useful if you want to use and existing Norm rule as a template for a new one, or if you just want to copy part of one. See image for an example.
15 votes -
Modify BackOffice to Clearly Identify Old UI vs New UI components and methods.
It is very frustrating to have documentation that leads you down one path in Backoffice, only to later find out that the path is only applicable to the old UI and has no effect on the new UI. Modify the configuration wizard to clearly identify things as new UI or old UI. Ideally, BackOffice would react to the checkbox for New UI and only show me choices that are applicable to the new UI.
14 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 -
Could Exlibris regularly update the list of common titles used by the Primo duplication detection vector?
Primo uses the duplicate detection vector to determine whether or not records will be deduped and merged in Primo.
One of the match criteria is full title. If two records have the same title and the title is not in the list of common titles, the records are assigned 600 points. (800 points or higher means the records will be dedupe/merged.)
The list of common titles is provided here: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/180Files_Used_by_the_Dedup_Algorithm#wwconnect_header
It includes common titles such as annual report, bulletin, transactions... Unfortunately it does not include other common titles such as news, poems, plays... (See attached Excel file.)
My request…
13 votes -
[PRIMO] Allow normalization of Primo Central Index PC records
It would be great to have the ability to normalize the Primo Central records using NR set as we do for local records.
This would be very beneficial. For example:- Customers could choose their own facet values and harmonize them with local records.
- Values only in PC records could be removed of modified (e.g. toplevel facet values for Open access and Peer Reviewed )
- FRBR and Dedup could be performed also against local records, thus greatly improving results in blended search. etc.
13 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 -
Tags Management in consortium level environment
The Tags Management page is only available to institution level in a non-sharing environment and this is not available in a consortium level environment.
So staff users can't delete tags, which is a problem.
Please make it available for all environment.
13 votes -
[Primo] - Add an enabled / disabled status field to pipes
It would be useful to have an enabled / disabled status field in the Pipe definition.
For example delete pipes or rarely used pipes could be disabled and enabled only when needed, thus minimizing the risk of launching/scheduling them by mistake.
This would also mitigate the current lack of the possibility to deleted old / unused pipes (see https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19994728-allow-deletion-of-old-unused-pipes ). Disabling them would be an improvement.11 votes -
Pull database recommendations from Alma holdings
The resource recommender in Primo currently requires us to manually upload files which list databases or other resources we want to recommend.
Given that most/many? Primo users are on Alma as well, it would be good for primo/alma institutions to have autopopulated database recommendation choices (that can be turned on or off at will) from Alma local holdings.
This is similar to how Summon's database recommender works with 360core knowledgebase.
This creates better efficiency compared to creating seperate lists for the database recommender because if the URL changes or the resource gets cancelled, one would have to update one place…
11 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 -
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 -
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 -
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 -
Primo Central note field - include in export
In the new Primo Central Activation User Interface (Feb 2019 release) you can now add notes to Primo Central collections. Would it be possible for the notes field to be included in the export to excel?
9 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
- Don't see your idea?