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

1029 results found

  1. 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,…

    178 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. The new Give Us Feedback Tool should provide information about the end users IP

    Access to electronic resources our library subscribes to is IP-based. If the user's IP address belongs to the university's IP range, they are recognized when they go to the resource and do not experience any access problems. Most of the issues reported to our support team come from students who forgot to turn on the VPN. Adding the IP address information to the feedback message would save us a lot of time in processing such issues.

    194 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Display both active (payable) AND accruing fines/fees at Fine+fees tab of a user’s account

    Fines+fees tab of a user’s account does not show the balance of the accruing fines. Fines+fees tab doesn’t include the information of the loans that have accruing fines on them, and this confuses clients. They should be able to see this information easily and understand the difference between active and accruing fines.

    We propose that Fine+fees tab of a user’s account should display the total amount of active and accruing balance; the active (payable) balance with the Pay button beside it and the accruing balance. We also wish that the fine type of the loans that have accruing fines would…

    82 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Report a problem - allow users to add an attachment

    When patrons are reporting a problem in Primo user interface, usually adding a screenshot is very helpful for support.

    Can "Add attachment" be added to the Report a problem form?

    Petra

    48 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Visualization of Analytical Bibliographic Data in PrimoVE.: Correct Sorting of Parts

    A multi-part resource (eg: a sketchbook containing 200 drawings) is catalogued in MARC 773 (host/item relationship). PrimoVE ought to sort and display the component parts using $$g and $$q. Currently PrimoVE fails to do this in the correct numerical order. Rather, the presentation is alphabetical which is useless for component-items organized by their part or page number. There was a recent ideas exchange issue raised on this very topic, which was “solved” by providing the aforementioned “alphabetical solution”. However, a NUMERICAL visualization has much more value in Discovery for patrons who are interested in locating an item as part of…

    237 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Allow HTML coding for all labels

    Hi

    Please allow HTML coding for all labels.
    Including URLs via a href when the label isn't used as a link already.

    This is working for a few labels, but far from all.


    Related:

    HTML for public notes https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/44282220-support-html-in-ges-public-notes-in-how-to-get-it

    HTML for collection discovery description https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37773493-allow-html-in-collection-discovery-description-fie

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Make it easier to re-order Primo display details in Full Record Services

    When configuring the order of "details" fields in Configuration -> Discovery -> Configure Views: [View Profile] -> Full Record Services: Details, Alma users are only able to re-order fields by moving them up or down one table entry at a time. Anytime you add a new field, it's added to the end of the list by default. In our case, we have almost 50 different display fields, and if we want that new field to appear near the top of the list, we have to scroll down and click the Up arrow for that field 50 times to bring it…

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Make the Resource Recommender Banner fit the length of the resource description

    The banner description text is truncated in the first line, making the display of the description dependent on its length and even shorter when viewed on mobile devices. It would be great if the height of the banner would auto-adjust to show all the text.

    I attach images showing this (banner.png) and how we would like it to be displayed (banner_modified.png).

    Thanks

    44 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Translate coverage and licence labels for NZ full text services in IZ views

    PrimoVEs in our network use 4 languages for the user interface - English, German, French and Italian.
    Consortial and Open Access e-resources are activated in the Network Zone for all the IZs.
    When viewing Full-text services from NZ in the detailed view in IZs, the coverage and license labels are not translated to the language of the user UI.
    The absence of translation creates discrepancy for our users. The IZ FT services' labels are translated but the NZ services are always in English.

    103 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Ability to boost newer editions as 5 publication dates does not do this job well.

    Currently we have older editions showing above newer editions in Primo VE. It would be helpful to be able to boost editions by the number of the edition. Currently the date boost has only 5 possible options in Primo VE. This means you can only add 5 separate years to regulate newer editions showing above old ones. Uses date ranges doesn't work as the edition between the range get same boost. Either you need to increase the number of date boost entries or create an ability to boost by edition.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Make the path shorter to change PIN code for self check

    One of the most frequent problems our borrowers have is that they have forgotten the pin code they use when borrowing books at the self check machine. We prefer that they change it themselves by logging into their account, but doing that is rather cumbersome. The function is hidden under My library account/Settings/Address/language settings/Update login credentails. It could instead be placed in the menu or lifted so that it appears before the adress and language settings.

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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…

    216 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…)
    0 comments  ·  Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Searching an item corresponding to a specific record is not possible if not logged in to the IZ that owns this item

    If you are logged in an IZ A and you are searching a specific item belonging to a specific record, you will find it only if this IZ A owns this item. If you are logged in IZ B that does not own any item of this title, the holdings are merged into one or several records (deduped) and you cannot distinguish which item belongs to which record.
    Example:
    IZ A has 6 records of one title; each record has one item.
    In the IZ A, searching this title, you will find 6 records, each one with its item
    IZ…

    33 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Inform users when wildcard limit has been reached for local records (when still displaying CDI results)

    Based on Salesforce case 06390632.

    When using wildcards in a Primo search, there is a limit to how many you can use before the search triggers an error that excludes all local records.

    https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Long_combinations_of_Boolean_operators_and_truncated_terms_(wildcards)_return_0_results

    This limit is only for local records. The CDI search does not follow the same limitations and will still gather results even if this limit is reached.

    If a users crosses the wildcard threshold when searcing in a scope containing only local records, there will be an error message displayed that explains why no results were found. However, if the same search is done in a…

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Allow patrons to order a specific item in a fulfillment network

    Hi

    We are in a consortium with a fulfillment network.

    Which in many cases means that the patrons can not pick which copy of a book they want to order.

    While this may make sense as the default (1), it is frustrating for many patrons, myself included.

    • When more than one copy is available, I want to be able to decide which one to get
    • When a book is on loan I may prefer to wait for the copy of my favorite library to come back instead of getting the book from somewhere else

    This is especially relevant when I'm…

    155 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Primo Name/Title Browse Searches

    Primo Name/Title Browse Searches

    As frequent Primo users searching for known music items, the Alma Music Users Group would like to propose that Ex Libris create a left-anchored browse search for name/title entries found in bibliographic records. An alphabetical left-anchored browse search is particularly helpful for known-item searches that are often used for music materials and prolific literary authors.

    Currently, Primo provides browse search options for names (name portion only ($a,$q,$d)) and name/title headings used as subjects. For prolific authors, it is not unusual to find thousands of name/title headings lumped under the composers or authors name, with “20+ records”…

    269 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Do not display private fields in “display source record” or full record in Primo VE.

    Marc 21 coding is used to identify some marc record fields/subfields as private. As an example, the indicators in the 541 tag are used to indicate that data in the field is ‘private’ to the organisation. Primo VE should automatically hide these fields from the source record and full details display in Primo VE. If an organisation wishes for the field to be made public they can adjust the record coding as appropriate. Alternatively organisations should be able to select to suppress private fields (as identified in marc 21) from public display.

    32 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Collection Discovery : Add a button "View this collection as search results"

    Beside the buttons to display a collection as a Grid or a Gallery, we would like to have a button to get the collection items in the result list, with the brief display and the facets. This could be a deeplink on the Collection ID with a "query=cdparentid" in the URL.

    Please note that there exist two very close ideas:
    https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/36709789-add-facets-into-the-collection-discovery-ui
    https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37607257-collection-discovery-display-items-in-a-list-view
    But this idea groups both features.

    Thank you.

    45 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Generic Field in Resource Sharing Request Form

    We use the ILL request form in Primo VE and use the Generic Field to get users to confirm they've checked whether the resource is in stock. This is working well but now for every request it includes the text from the field "Please tick to confirm you have checked Library Search - we will not buy items that are already available.:true" in the note and request note field on the borrowing request. This makes it hard to see specific notes.

    We'd like to have the option to stop the generic field text being copied to the fields.

    21 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 51 52
  • Don't see your idea?

Feedback and Knowledge Base