Skip to content

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

50 results found

  1. Saved search alerts - avoid spamming

    Currently a user can enter any email address for alerts to be sent to. To avoid misuse, institutions should be able to configure so that a user can only choose an email address that is in their user account contact details already.

    Also, if the institution does not use such a configuration, and the user inserts an email address that is NOT in their user account, then there should be an email verification process. Alerts will not be sent until the recipient clicks a message to verify they have control of that email address and willing to receive them. Assumes…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Primo VE  ·  Admin →
  2. Enhance "Quick Access" Section in Primo VE to Display All Files Linked to a Representation

    Currently, in Primo VE, the "Quick Access" section within the detailed results page of digital titles displays only the first file linked to a representation. Users are required to open a full-screen viewer, where they can navigate through the additional files using a file navigation pane on the left. While there are arrows in the "Quick Access" section which allow users to navigate between files, this functionality is not always intuitive, and it is not immediately apparent that additional files exist beyond the first one.
    To improve user experience and accessibility, I propose an enhancement to the "Quick Access" section…

    50 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Primo VE  ·  Admin →
  3. New Book List in Primo VE

    I would love to have in-built Primo VE functionality to showcase the new book list in Primo VE, like Trinity College (https://ctw-tc.primo.exlibrisgroup.com/discovery/search?vid=01CTW_TC:CTWTC&lang=en) did using this alternatively, but not everyone is that techy, so please consider adding this in upcoming releases.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
  4. Automate SSL/TLS certificate management

    For hosted Primo sites that have custom domain names, the current process for deploying SSL certificates involves time-consuming manual steps and hand-offs, many of which must be repeated each time a certificate is renewed. [1]

    Several institutions will soon require SSL certificates to be renewed every 90 days, at which point the current manual process will become utterly unmanageable for both Ex Libris and its customers. [2]

    I propose that Ex Libris adopt an ACME-like service (such as Let's Encrypt) to fully automate SSL certificate management. The customer's responsibility would be to set up a DNS record (as they do…

    289 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Primo VE  ·  Admin →

    Hi,

    We are now utilizing the Automated Certificate Management Environment (ACME) protocol to manage custom domain certificates.

    See more details here -

    https://knowledge.exlibrisgroup.com/Cross-Product/Knowledge_Articles/Simplifying_Custom_Domain_Certificate_Renewals_-_Introducing_Automated_Management_with_ACME



  5. Add ability to configure the display at the item level and the location level in the GetIt section

    In Primo VE, the display of the GetIt section works currently as following:
    If there are only items in one location, the first display after opening the full view is at the item level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma99118073204005503).
    If there are items in more than one location, the first display is at the location level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990104195490205503).
    Because our libraries are part of a huge consortium, our users always have to check first in which library an item is available before checking the item information. Furthermore, we believe that the user experience would be better, if the GetIt section looked…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Admin →
  6. Remove field 655 from the subject facet

    In Primo VE the 655 are shown in the Subject facet. As the 655 relate to form and not to content, they should not be shown as subjects. Furthermore, the 655 are correctly shown in the “Genre” facet.

    The 655 should be excluded from the Topic facet in the Facets Section Mapping:
    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/120Other_Configurations/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record#Facets_Section_Mapping

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  7 comments  ·  Primo VE  ·  Admin →
  7. New Tool-Give Us Feedback

    The Give Us Feedback Tool should perform a validity check of the email address. Currently it is possible to enter anything in the field 'Enter your email'. The email address validation is commonly used by default within forms.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →
  8. Collection discovery - sub collection searches

    We welcome the enhanced searching on the top level of collection discovery however we have found we also need full searching over our nested sub collections. This is not only useful for users of PrimoVE but also for local data scopes as we require them to accurately include sub collections in search profiles.

    164 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  2 comments  ·  Primo VE  ·  Admin →
  9. Relevancy sorting in FRBR version list display should use terms searched

    FRBR groups and the display of versions within them does not consider the relevancy of the terms searched. Often a user is searching for a specific version within the FRBR group (ex: Homer's Iliad translated by Richmond Lattimore) but there is no way to focus in on this version within the list of FRBR versions. Even when users search specifically for terms: Iliad Lattimore, Lattimore is hidden within search results. Within the list of FRBR versions, sorting by Relevancy should use the terms searched by the user -- this should enable the works of a single translator (like Lattimore) to…

    209 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Primo VE  ·  Admin →

    In this enhancement, Primo VE will highlight the selected record on top of the list of  FRBR versions, only for the preferred record mode.

    We understand from the comments here that there is also a request to add this option for Generic mode, however in the generic mode we only show a link to the list of versions and not pointing for a specific record. In Generic mode we don't show any actions or availability status, and there is no option to open a full mode as this is not a specific representation of the record.

    This is why we have chosen to implement this only for preferred mode.

    Please provide some more clarifications for the generic mode request in a dedicated idea.

    Best regards

  10. ShareDigitalResources parameter to allow individual settings

    When the customer parameter shareDigitalResources is enabled, which is useful to allow freely available digital representations (for digital objects stored in Alma or in a remote digital repository) to be available to all institutions, records loaded from external data sources via discovery import profiles are also impacted by this. According to Ex Libris, this is by design as these records from external sources are considered as digital objects. This leads to the following problem in Primo:

    As soon an IZ enables this parameter, its records from external data sources are included in the search results of local search scopes made…

    132 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Primo VE  ·  Admin →
  11. Primo VE: Re-instate the A-Z browse function for DATABASES

    Re-instate an A-Z browse option for Primo VE Database Search, like the one available for Primo Classic.

    212 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Primo VE  ·  Admin →
  12. Make it possible to add or exclude records from the OTB resource display types based on locally-defined conditions

    We would like to have more flexibility with Primo VE resource types and the related facet and prefilter values. There are situations in which we would like to be able to add records to an OTB resource display type that don't meet the OTB conditions. For example, for certain textual integrating resources that users are likely to think of as books, we use conditions based on the presence of form/genre headings to add them to the OTB ""book"" display type in Primo BO (e.g., open textbooks that are periodically updated: https://searchit.libraries.wsu.edu/permalink/f/j5jme3/CP71251613210001451). Conversely, we would sometimes like to be able…

    299 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  13. Add more options to configure facets by prefilter and resource type

    The configuration options for facets in Primo VE are currently very limited, and not at parity with Primo on Back Office. It is not currently possible in Primo VE for a single record to have multiple facets or prefilter resource type values, to better align with CDI in a blended search, it is not possible to configure the facet and prefilter resource type values separately and independently of the display resource type values, and these facets cannot be configured with sufficient granularity. As examples of this configuration issue to be made possible with this request: Example 1: Our display types…

    417 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Primo VE  ·  Admin →
  14. Correct citations for local Articles and Book chapters

    Articles and Book Chapters from local sources (externals sources as well as Alma) don't have complete citations because data are missing in the mapping. Volume, issue and pages are not mapped.
    Our request is to provide a mapping for these data elements so that they can be added to the Addata section of te record, or to allow sites to normalise the data in this section so that we can provide correct citations and export functionality.

    96 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Primo VE  ·  Admin →
  15. Enhance the database search to include keyword searching

    Currently the Database Search in Primo VE is limited to searching for words from the title. This is unsatisfactory as many databases have vague and uninformative titles. We need broader search capabilities and would like the search to also include categories, subjects and descriptions.

    91 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Primo VE  ·  Admin →

    Primo expands the Database Search to include all search fields, such as subject and description. Previously, searches performed in Database Search matched only on the title. In addition, if configured the expanded DB search functionality will also allow users to search by category name.

  16. Campus level settings for CDI Link in Record

    Discovery Customer Settings are only configurable at the institution level.

    It makes CDI Link in Records broken for multi-campus environments with separate subscriptions to vendors like Gale, Infobase, and Kanopy.

    Please make customizable using Inventory Management Groups or Discovery Views.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Primo VE  ·  Admin →

    Thank you for this idea, In Primo VE December 2020 release we introduce a new mapping table for managing the Central Index linking templates with your institutional linking parameters where you can also manage multiple linking templates per campus code.

  17. Work with additional batches of 50 records after the first set of 50

    It's now possible to select and act upon a set of 50 records in Primo VE. However, once the first set of 50 records has been selected and saved to Favorites (or otherwise acted upon), all actions on additional records must be done manually, one at a time. After the first 50, the user gets the message, "Please edit your selection to include no more than 50 records." and then it is no longer possible to work with records in batch.
    For example, often a user will perform a search in Primo VE and find a set of 150 or…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →

    Thank you for this suggestions. The new pagination method will allow to select additional set of records and not only first top 50 records.
    This is coming with Primo May 2021 release and Primo VE June release.

  18. Allow Roman numerals for page range in digitization request form

    Users submit a range of pages when they request digitization of a material. Preliminary pages in books often use Roman numerals. Please whitelist these characters along with 0-9 in the form validation scheme.

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  3 comments  ·  Primo VE  ·  Admin →
  19. Primo VE: Please add 773x to the index on ISSN

    When searching on ISSN in Primo, not only journals are found, but also articles because articles in CDI have a data field ISSN.
    This is not the case for locally catalogued articles because following the MARC standard, the ISSN of the journal is catalogued in tag 773$x.
    Not only are locally catalogued articles not found when searching on ISSN, but also the facet on Journal title doesn't work for these local articles.
    Therefor, our question is to add tag 773$x to the index on ISSN to allow for a consistent search experience for local articles and CDI articles.

    109 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
  20. Put the FRBR Dedup Test Utility where cataloguers can use it

    The FRBR Dedup Test utility is currently hidden in Discovery configuration (Primo VE). The team members who need to use this functionality are cataloguers so they can see what edits might be needed to troubleshoot issues preventing or causing unexpected FRBR/deduplication.

    Adding it to the Resources menu in Alma is an option, another might be for cataloguers to be able to trigger it when comparing records in the metadata editor.

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Primo VE  ·  Admin →

    New discovery role is now available : Discovery Operator – Limited " so more library staff can get access to the FRBR Dedup Test Utility
    Check for more details in Primo VE release notes – under Allow Task-Oriented Discovery Roles for Staff

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base