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 toggle switch which requires IP validation to grant access to PCI paid content
Primo allows authentication via access from a specific IP address range or patron login. Once authenticated, patrons can search paid content (from subscription databases) in the Primo Central Index. We are not an academic institution, therefore we do not have a fixed population of patrons in the form of students. In MetaLib our patrons could see paid content in search results only if they were onsite.
We propose that a toggle switch be added to the Back Office, at the institution level, which would allow us to require IP validation for access to PCI paid content. Thus, being signed in…
5 votes -
Reinstate ability to customize header/footer HTML and no results HTML file functionality in New Primo UI
Would like to reinstate the ability to customize header/footer html files as well as the ability to customize the no results html file in the Primo New UI please. In the Old UI, you could customize and upload these files individually. You cannot customize any of them in the New UI, even if included in the customization package html folder. Would like to have those files included in the customization manager.
We would like this ability because some code needs to run first (which case it would be included in the header) or last (when you would include it in…
8 votes -
Add Back Office code/mapping table codes to UI as IDs or comments
When trying to configure the Primo UI, it would be really nice to be able to inspect an element and see if there are corresponding back office code/mapping table values that control it. These could be added as comments or as IDs or in some other way. This would help Primo admins track down the correct settings quickly and accurately.
3 votes -
Automatic sync of library codes with scopes and static facets
The Library Codes on the Institution page are currently automatically copied to the Library Names code table and the ILS Library Codes mapping table, which is great.
We would like to have an option to automatically sync these library codes also with the Scopes and Search Scopes (used for searching, and Location drop-down lists) and Static Library facets mapping table, in order to eliminate the need for manually updating all library codes in the scopes and static facets.0 votes -
Primo VE: Add the ability to configure different availability messages by location
We would like to be able to configure availability messages by location. For example, if there are no items, the message "Ask at the Reference Desk" displays. We have a few locations (one for digital materials and one for citations) that do not have physical holdings, so we don't want this message to display for those locations.
4 votes -
Our Library has decided to activate in Primo Central Index (1) resources that are free to all users in search and delivery as well as (2) re
Our Library has decided to activate in Primo Central Index (1) resources that are free to all users in search and delivery as well as (2) resources that are restricted in delivery but not restricted in search. As there are new collections added to PCI from time to time, in order to save manpower, is it possible to configure our PCI to automatically activate all newly added resources that either have no restrictions at all or is restricted for delivery only but not restricted for search in our production PCI and staging PCI?
1 vote -
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 -
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.
94 votes -
Allow to delete records in Primo BE ( included dedup records )
Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.
It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it.…
44 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 -
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 -
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 -
Allow deletion of old unused pipes
We've got a long list of pipes, including some from an old repository we don't have anymore, and one I accidentally created with the wrong type (regular instead of delete-and-reload). These clutter up the list and make it harder to find the ones I actually use. It would be really good if we could delete the ones we don't want anymore.
(Or at least to be able to hide them, or if nothing else then to be able to rename them to "zzzDON'TUSE" or something.)
4 votes -
Consortia environment; Provide inheritance for open access collections
At present, open access collections that are activated by the consortia account are not "inherited" by individual members of the consortium. Given the number of open access collections, and the possible number of consortia members, it can be a tedious task to activate a large number of OA collections for each member.
We would like to see that OA collections can be "inherited" as well, just like regular subscription collections.6 votes -
Allow configuration of multiple email addresses in back office
In primo's general configuration, there is a field for a staff email address. This address is used for emails which are generated by primo in response to an issue (e.g. when an IP is automatically blocked because it is suspected of being the source of a DoS attack) and is also displayed to users of primo when an error page is shown. We would ideally like to be able to send these to different email addresses so they can be processed differently. Would it be possible to add a second email address into the primo configuration and use that for…
4 votes -
Set default language(s) in PBO
When managing the various mapping and code tables in the PBO, it gets complicated because I'm constantly having to set the language column. It would be great if we could have that narrowed by default to just the ones we need. To support multilingual institutions, it would need to allow for multiple defaults if possible.
3 votes -
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 -
Set default language in Primo Back Office
It would be useful if Primo Back Office users were able to set their own default language preferences (e.g. for content of the code tables) rather than have to select the language every time.
5 votes -
Copy parts of Normalization Rules Sets to other fields in the same set
It would be very useful to be able to copy subsets/blocks of a Normalization Rule Set to other blocks/fields in the same set, instead of manually copying very complicated rules. This was a NERS request from the Free University of Bozen (4440), but it did not receive enough votes.
38 votes -
Show the terms added to the patron's query by the linguistic features (i.e. stemming, synonyms etc.)
As default behavior, Primo not only looks for the patron's query, but enriches the original keywords of the user with additional terms, in order to improve the performance.
The system first tries to guess the language of the query, and then tries to enrich it, using a variety of steps described in the Linguistic Features section of the documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Technical_Guide/120Linguistic_Features
For example, a query for the string: Birne
if recognised as German, is enriched with following synonyms (dictionary file as to March 2017):gluehbirne(normal),gluehlampe(normal),lampe(normal),leuchte(normal),leuchtkoerper(normal),haupt(normal),kopf(normal),ruebe(normal),schaedel(normal)
The point is that the whole thing is a blackbox for both the librarian and the…
57 votes
- Don't see your idea?