Skip to content

Primo

← Have an idea for Ex Libris?

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.

How can we improve Primo?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

10 results found

  1. Links in View It should be anchor links rather than buttons in NDE

    In the legacy version of Primo VE, links to remote resources in View It are anchors, allowing the user to see the destination in the browser and to copy it using a right-click. This ends up being critical for troubleshooting. In NDE instead there are only buttons as resource links, so that we need to work much harder to get the URL (e.g. using the "Display CTO" method). Given that these page elements are actually navigational--they are links to remote resources--it would be far more appropriate for them to be rendered as regular anchors/links rather than buttons (regardless of styling).…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →

  2. Improve Resource Recommender Description field behaviour in NDE

    The Resource Recommender in Primo NDE has a 200 character limit (with spaces) for the Description field. When the Resource Recommender displays and has more than 200 characters, it cuts off with an ellipsis. However, the ellipsis cannot be clicked to expand the text, like in other areas of Primo. Instead, the only way to see the full text is to hover over and read the tooltip. In order to improve the experience for users we suggest these improvements to NDE's handling of the Resource Recommender:
    -The ellipsis is clickable, and expands the text of the Description
    -The white space…

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →

  3. Optimise vertical banner space (NDE)

    Out of the box, the NDE Vertical banner wastes the bottom 1/2 to 1/3 of the screen space it is allocated. At the same time, the description text is truncated, requiring the user to hover (or hold on a small screen) to know the details.

    The lower part of the banner accommodates an image, which most institutions will likely use decorative images for, as it is not easy to determine which part of the image might be cropped/selected to display.

    It would be helpful for users to just be able to read a longer description, and this could be accommodated…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →

  4. Primo VE facet for collections regardless of inventory type

    I would like to propose an out of the box facet for collections that can include all 3 inventory types.

    We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

    Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

    As a workaround, we have utilised the digital collection facet for this…

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →

  5. Purchase Request date

    Add the user's purchase request date on their Primo library card in their account.

    We would like that the user can see the date when he create a purchase request date on his Primo library card in his account.

    We think that's will be an improvement for the users.

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →

  6. Allow Online Services Order to sort by current access

    We need the ability to move to top of View It a service with current access (this means the coverage statement is open-ended, ie Available from 1998 - current).

    Users get overwhelmed with the long list of services often displayed, and ordering the list according to interface or electronic collection name doesn't address the most important aspect, whether there is current access or not. As an example, on Proquest interface Z, journal title X may provide current access, but journal title Y on the same Proquest interface Z may only have archive access. We only want to put journal title…

    233 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Primo VE  ·  Admin →

  7. My Library Card: Option to hide Personal Details

    It should be possible to hide Personal Details section under My Account in Primo VE.

    We are able to disable the labels in the following, but seems no option to hide the Personal Details section. Even if we disabled the labels for this tab, it is not completely disable from appearing or being clickable.

    1. Configuration > Discovery > Display Configuration > Labels > All code Tables > Library card Labels
    2. Configuration > Discovery > Library Card Configuration > Personal Details Configuration

    Also, Primo Technical Support Analysts already confirmed the personal details section cannot be hidden using CSS. So we post…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →

  8. Ability to edit the OTB (Out-of-the-Box) search and facet rules in Primo VE

    We would like to be able to edit the OTB search and facet rules. This is necessary for parity with PBO. There are several things that we were able to do in PBO that we cannot reproduce in VE because of the lack of this functionality. In the PBO OTB author search and facet, we were able to include dates and qualifiers from names in the LCNAF, which improved precision. In the OTB language facet, we were able to include intertitle, caption and audio description languages, which are not currently included in the VE OTB index. On the other hand,…

    432 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →

  9. Improve indexing of in press articles in CDI

    The Central Discovery Index (CDI) includes many in press articles (i.e., articles that have been accepted for publication in a future issue). However, because these records do lack a pub date, volume, or issue number, the Alma link resolver cannot reliably determine whether an institution has access to these articles. We ask that Ex Libris improve they way in press articles are indexed in CDI so that the link resolver does not return false positives for content the library does not actually own.

    Example: https://www.screencast.com/t/iZ2jjOgWgC6v

    452 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    8 comments  ·  Primo VE  ·  Admin →
    Planned  ·  AdminAmy Pemble (Admin, Ex Libris) responded

    For full transparency, the commitment we made for this idea is to do the analysis for this feature in 2024. Based on that analysis, we will craft a solution that we can deliver in early 2025. We will keep you updated via this idea.

  10. Ability to store test records for Primo VE

    When you test normalization rules for external data sources in Primo VE, you need to upload your test record from your computer every time you make a change in the NR. It should be possible to store sample records for easier testing

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  • Don't see your idea?

Primo

Categories

Feedback and Knowledge Base

(thinking…)