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

162 results found

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

  2. Primo Analytics - Add Actions for clicks on View It links, for both Link in Record and Link Resolver

    There is a significant gap in Analytics recorded actions for user engagement with electronic resources directly in our Primo environment.

    In Classic UI, this was partially possible by GetIt Link 1 and GetIt Link 2 actions, but invoked by a user clicking on the Get It tab, rather than an actual link.

    This aspect is not even possible in New UI with a known gap for years for these GetIt actions.
    Link Resolver Usage data is partially recorded in Alma Analytics, dependent on configuration.
    This situation of data loss will be even more of an issue on CDI, with the…

    94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Please note that with the August release we have added more actions to help tracking view it links usage. 

    Just to clarify - In August 2022 we've added actions for “Additional Link to source”, “Additional openURL” (not relevant for Alma URLs), "Link to source" and "OpenURL FT" (not relevant for Alma URLs) - all sent when coming from ViewIt. 

  3. 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.

  4. Display both link in record and links from link resolver in CDI

    When there are records in CDI that have link in record, but also would return links from the link resolver both types of links should be displayed to the end user.

    The challenges with the link in record are discussed in this idea: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/40487230-preference-cdi-link-resolver-records-over-link-in

    They have a tendency to break and if the link for some reason do not lead to the full text the end user does not get any other way to the full text (as they do with the multiple links fromt he link resolver).

    We hope that Ex Libris enables the system to display both link…

    610 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you for this idea, For CDI records with more than one link option, users now can see the preferred linking option in the View It with an option to show more links. This is coming in Primo VE April release and Primo May 2022 release. 

  5. 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.

  6. Add spinner or indicator for Getit frame to indicate content is loading

    The Getit frame in Primo often takes between 10-45 seconds to load. During that time many patrons believe it isn't working so they close the window or leave to go elsewhere.

    We would like to have a spinner or some sort of visual indication built into the Getit frame so patrons know that content is being fetched.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Hide DUE TIME in Primo

    It should be possible to hide DUE TIME in Primo, both in My Library Card and the item list. Many libraries do not offer loans by the hour and opening hours in Alma are not the same as the opening hours of the physical library. Therefore displaying the due time in Primo is often just noise.

    See attached screenshots.

    301 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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

  9. Boost Institutional Search Results in Primo VE

    We'd like the ability to boost our institutional results in a search profile slot that includes consortial records.

    46 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 →

    Thank you for this idea. We added to Primo VE the Boost My Institution option to allow an institution in a consortium to boost its search results, over results from other member institutions.

  10. Primo VE: allow translations in OTB Display Fields

    We 'd like the possibility to use translations in OTB Display fields, not only in local fields.
    Use case: we want to use a code for contributors & creators ($4), rather than tag Relator term ($e) and use the translation functionality to display this role in the language of the interface.

    1 vote
    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 →
  11. location displayed for resources sharing

    Do not display the resource sharing link for item that do not circulate. This is super confusing for our students. The request link does not display in the other scopes, but cannot seem to be turned off for resources sharing. Our students are requesting items from our sister college that do not circulate.

    6 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 →

    Thank you for posting this idea. Please refer to Primo VE release note – January 2021 for more details on Central Definition for Hiding Resource Sharing Button – Based on Institutions Location List

  12. Limit autocomplete-suggestions from PCI/CDI to activated sources

    In Primo you can activate autocomplete to get suggestions for search-queries based on what the end-user begins to type in the search-box.

    We have tested the functionality and see that it could be useful for the end user to get these suggestions. However we see that the suggestions from the central index in some cases are a little strange and that you get suggestions from the entire index and not only the sources the institution has activated. This means that the end-user could get suggestions that gives 0 results.

    If you get a suggestion that leads to nothing you will…

    252 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Customizable RIS mapping table for Primo VE

    In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:

    The mapping of the RIS fields to PNX fields is as follows:
    IS addata/issue
    TY addata/ristype
    N2 addata/abstract
    N1 addata/notes
    PB addata/publisher
    A2 display/contributor
    ET addata/edition
    KW display/subject
    EP addata/epage
    DO addata/doi
    PY addata/date ; display/creationdate
    JA addata/stitle
    VL addata/volume
    CY addata/cop
    AU display/creator
    T3 addata/seriestitle
    T2 addata/addtitle
    T1 display/title
    SP Addata/spage
    JF Addata/jtitle
    ID Alma MMS ID
    SN Addata/issn; addata/isbn; addata/eissn; addata/eisbn

    As most reference managers will read A2 as Series Editor,…

    58 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 →
  14. Add Mandatory choices for all Request forms in Primo VE

    For the Digitization Request, Hold and Booking Request, and Purchase Request forms, the Alma mapping tables (under GetIt Configuration) define the fields that are displayed to users (Yes = viewable to users, No = not viewable to users).

    We would like to have the possibility to configure mandatory fields if we want the user to specify a field in the form (as it is already the case with a check box in the Resource Sharing Request form).

    223 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Thank you for posting this suggestion. Starting of VE July 2021 release you will have more options to improve requests forms: adding mandatory choices , adding forms’ description including links and add generic checkbox. more details can be found in Primo VE release notes

  15. Improve new sort in collection discovery

    As of Nov 2019, we can sort a collection in collection discovery by "relevance" which seems to be arbitrarily applied and title.

    1. There should be the same sort options (as the main Primo results):
    2. Date (newest)
    3. Date (oldest)
    4. Author

    5. Institutions should be able to apply a default of choice

    6. Institutions should be able to remove a sort option

    22 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 →

    Thank you for this suggestion. you can find now with Primo August release notes and Primo VE July release notes more details on the new sort options with also an option to set per collection the default sort.

  16. Better display of subcategories in database-search in Primo

    In the Database search in Primo, to show subcategories you have to click the little arrow in front of the top category. This is not intuitive for end users, and this is actually the feedback that we get most often.

    It would be much better if clicking on a top category both did a search for records in this category and at the same time opened the subcategories.

    This would enable the user to see all the databases in one category, and at the same time display the possibillity to narrow down to a subcategory if necessary.

    I hope that…

    374 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Add Australian language codes to Primo Back Office

    We would like Austlang (Australian language) codes added to the out of the box language code and mapping tables in Primo and for this coding to map to language facets and language display without any additional intervention by institutions. These language codes, used by many Australian libraries, are recorded in the 041$a field(s) of the bibliographic record. These codes do not conform to the three alpha character coding found in ISO639-2 or 639-3. Australian libraries would expect to use these codes in addition to the standard language coding currently available.
    The full list of Austlang codes can be downloaded from…

    114 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Allow "best location" on brief results display to be configured by view

    A user viewing a view that is associated with a particular library or campus should be able to view availability of physical items at that library or campus libraries in the brief results layout. This idea is primarily for institutions with multiple libraries and, especially, multiple campuses. Campuses are associated with libraries, and typically a Primo view will be associated with a campus.

    Currently "best location" can only be set via the user's IP address. This approach works when users are at the location, but when a user is off-campus, the first location to show on brief results and full…

    324 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Option to allow patrons to opt-in/ opt-out of sms from Primo VE my account tab.

    Currently there is no option to enable the sms opt-in option from PRIMO VE. This will allow patrons to enable/disable sms notification if they wish to from My Personal Details on PRIMO VE.

    21 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 →
  20. Utilize data from multiple fields (LDR and fixed fields 006,007,008) in Primo VE resource type configuration

    Related to a previous idea now marked as Completed
    (see: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35488570-utilize-ldr-and-marc-fixed-fields-006-007-008-in)

    The functionality introduced in the April 2019 release only allows you to specify ONE field in the source MARC record that contains the resource type that you want to map to the local resource type.

    Primo VE should to be able to determine the resource type from combinations of data in MORE THAN ONE of the fields in the MARC record; i.e. fixed-field coding in the 006/007/008 field in conjunction with the LDR field.

    This is particularly crucial for complex resources not coded as language material (LDR pos.…

    281 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 →
  • Don't see your idea?

Feedback and Knowledge Base