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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. "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.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. resource recommender

    Resource Recommender (RR) entries are currently applied to all Views. There is no way to add them to one view and not to another view.

    We keep a test view on our Production server because our Sandbox is not yet configured for LDAP authentication. We expected that we would be able to apply the RR to only the test view, but this is no currently possible. There are undoubtedly other use cases in this lack of control is also an issue.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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.

    https://knowledge.exlibrisgroup.com/Primo/ProductDocumentation/TechnicalGuide/030DuplicateDetectionProcess/030DuplicateDetectionVector

    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/ProductDocumentation/TechnicalGuide/180FilesUsedbytheDedupAlgorithm#wwconnectheader

    It includes common titles such as annual report, bulletin, transactions... Unfortunately it does not include…

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 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.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. [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.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. 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.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 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_talbot

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. [Primo] - ask for confirmation when running delete pipe

    Right now, when clicking on 'Execute', the Pipe starts immediately.
    Especially in the case of 'delete' pipe, a popup asking for confirmation could help preventing unwanted deletions from the system.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 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.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Enhance SUSHI harvesting job

    The SUSHI harvesting job is set to either run every Saturday or not at all. Some vendors do not make their data available except for certain weeks of the month. This results in failed errors in the notification. Could this be expanded so you can set when the jobs will run, like once a month (after the 15th) when most vendors have made their usage data available.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Primo Registration Service collections should be editable by Ex Libris staff

    As a discovery librarian I would like the Primo Registration Service (Collection Activation) to be editable by Ex Libris staff so that resources incorrectly set as collection-level resources could be reset to Subscription (Linkresolver) level. This would mean large numbers of false positive search results in Primo UI could be reduced.

    Background: the Oxford Research Encyclopedias collection has been set up in Primo Registration Service as a collection-level resource and delivers Primo search results for every title in the collection, whether subscribed or not.

    It includes 27 separate encyclopedias on diverse subjects (we have only 2 titles).

    These are new…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 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.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. 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.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 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.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base