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

1167 results found

  1. Enable person entity functionality at the view level

    The new feature (May 2024) for person entities is either on or off for all views.

    For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.

    Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from…

    41 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)
  2. Discovery collections handling

    When creating or updating an Alma collection (adding/removing titles), the change is not automatically reflected in the Discovery Collections and it is necessary to trigger the reindexing for a correct display.
    This workflow is problematic when titles are removed: records are taken out from a collection but are still present in Primo VE because a reindexing is needed. They can no longer be found by searching for the collection in Alma. Depending on the collection, it might also not be possible to find them all via a single search and it might be necessary to manually add the records to…

    82 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)
  3. More DEDUP keys

    The implementation of the FRBR keys is affected by the DEDUP keys, so it would be desirable to add a new key in the DEDUP keys that includes the label 250.

    106 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)
  4. Primo Header is cut off at a certain Window Size

    When one reduces the size of the browser window, the button for the advanced search moves into the “hidden” menu. Right before it disappears, it is cut off and can no longer be read. Furthermore horizontal scrolling is required in order to visually grasp the other menu items such as "Login" and "Menu". As far as we could check, this affects a browser window size from around 600px to 800px.

    This does not depend on local CSS modifications. It is a general UX issue that affects responsive design and furthermore is breaking with the WCAG accessibility guidelines (WCAG 2.1, 1.4.10, …

    61 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)
  5. HTML Language Tag customizable for Screen Readers

    In order to improve the accessibility of Primo, it would be helpful if one would be able to choose country-specific language settings for screen readers by the HTML language tag. We would be interested in the language setting “de-AT” to be available to recognize the Austrian variety of the German language. This could also be interesting for a lot of other languages.

    63 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)
  6. Article level records from Alma should populate resource sharing form correctly

    Article records from CDI will populate the Primo VE resource sharing form correctly, as a document delivery option for when there is no full-text available.
    However, when it comes to article level records from Alma, the Journal title is incorrect (instead, the article title is entered into this field) and other information is missing, like publication year, volume, etc. Overall the article is not recognized in the Context Object as an article, but instead treated as a journal - thus omitting all fields not relevant to a journal record.
    Example:

    1 - Go to: https://kbdk-kgl-psb.primo.exlibrisgroup.com/permalink/45KBDK_KGL/1pioq0f/alma99124396529705764. See that the resource…

    53 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. Improve resource accessibility with a new field «Request accessible document» in “Digitization optional parameters”

    To provide better access to resources for users with disabilities, ETH Library would like to offer its users accessible digital copies. This service requires an additional field in the digitization request form in Primo VE, in which users can indicate if they would like to request an accessible document. This field could be named “Request accessible document” and be added to Discovery > Configuration > GetIt > Digitization optional parameters, so that libraries can enable and disable the field as they like. We think that it would be best if there was a dropdown list available for this field with…

    45 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. Inform patrons about Pick from Shelf

    This is something we are really missing since we switched to Primo VE.

    I find a book I want to borrow, my library has it, but it's open stacks, which means I can't request it online to be picked up in the owning library.

    In our older catalog we had a pop up message to inform the patrons that they can fetch the item from the shelf themselves.

    DTU (https://findit.dtu.dk) solves it like this, which is exactly what we need - see screenshot dtu1.png

    Under B, we'd show the possible pickup locations, as we do now.

    A is…

    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)
  9. 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…

    201 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 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. Display import profile name also for for failed import jobs

    Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.

    7 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)
  11. Journal Search: Consider the NZ activation for e-resources with Inventory Management Groups in the IZ

    Our consortium activates Open Access e-collections in the Network Zone so that they are available in every IZ of the network. Electronic collections for Open Access e-resources are activated without any Inventory Management Group assigned to it. It should display for every IZ and every Inventory Management Group within the IZ.
    Some of the licensed e-collections in the IZs also cover e-resources that are activated in the NZ as Open Access. (Journals can have partial Open Access) The IZs are using Inventory Management Groups, and the local views are assigned to the campuses of the specific Inventory Management Groups. The…

    48 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)
  12. Open Access articles to display in full text results

    Currently, if only displaying CDI results with full text, articles tagged as open access aren't included. These are only displayed if the user toggles to show results with no full text.

    Ideally, articles tagged Open Access would also be included when displaying results with full text. The tag would need to bypass the link resolver process so those results are also included.

    This would reduce the number of users putting in ILL requests when they didn't realised the article was available OA.

    18 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)
  13. Primo VE mobile device enhancement

    When using Primo VE on a mobile device, such as a mobile phone, if you change from portrait to landscape and then back to portrait, half of the page will become blank, which is not conducive to readers' viewing.

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

    396 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)
  15. Item - Searchability of Public note in Primo VE

    We use the Public note of the item for provenance information. For this reason, the field contents should be searchable in Primo VE.

    68 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)
  16. FRBR generic: make display of the generic record customizable

    We use FRBR generic (in Primo VE) because we deem FRBR preferred to be too confusing for our patrons.

    We can't fix the duplicate display of contributors' names.

    Example:
    https://basel.swisscovery.org/discovery/search?query=any,contains,Homer%27s%20Iliad%20translated%20by%20Richmond%20Lattimore&tab=UBS&search_scope=UBS&vid=41SLSP_UBS:live&lang=en&offset=0, see also screenshot.

    Lattimore is displayed three times, Martin twice.

    As this is supposed to be a generic display, no contributors should be displayed here.


    We got the following response from Ex Libris in our case:

    "
    With the 'Generic record' option enabled, when conducting a search in Primo, in the list of results for a FRBR group, you will see a very generic record which is hardcoded and…

    11 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. Create/add in the ability to show and filter ALL content by place of publication and other data point relevant for decolonising collections

    With linked data being such a big part of what has being talked about so far in relation to NDE and AI being used in some new projects such as Primo:Research Assistant, we feel that it's the best time to think about using this data and the data in the CDI records to try and develop tools to identifying, show, filter place of publication or nationality of authors.

    We have developed our own facet using local fields, regular expressions and information in the MARC 008 to display the place of publication for items in our collection and filter by facet…

    6 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. Primo VE: enable search fields for the deepURLs

    InPrimo VE, in the "search" : {} section of the PNX record there are some fields that are still not searchable,
    like the "unimarclocalfields". It would be nice if all these would be accesssible with the deepURL query parameter
    I.E.: query=unimarclocalfields,contains,XYZ.

    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. Reference to public licenses of other institutions within the consortium

    Public licenses can be viewed in Primo VE's electronic holdings information area, but public licenses are not displayed in the electronic holdings display area of ​​other institutions.
    I would like to be able to display public licenses from other institutions within the consortium on my own institution's Primo VE.
    Without this function, I think that being able to view information on other institutions' electronic holdings would have little effect.
    Detailed information is attached.

    45 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)
  20. Remove the total number of results

    It would be useful if the total number of results are hidden by default from the search results page, but patrons have the option in their user account settings to enable the total number of results.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 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)
← Previous 1 3 4 5 58 59
  • Don't see your idea?

Feedback and Knowledge Base