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
  1. Preference CDI Link Resolver records over Link in Record when merging

    CDI now merges multiple results for the same article together, but when it does it preferences CDI records with 'Link in Record' rather than displaying the Link Resolver choices under Full Text Availability. The Link in Record articles often lead to indexing sites, not to the publisher where the full text is available. We need a config option where we can preference Subscription (Linkresolver) over Link in Record when merging records in Primo

    220 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Primo VE  ·  Admin →
  2. 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).

    206 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Primo VE  ·  Admin →
  3. Items loaned to Resource Sharing do not show as included in local scopes

    Primo indexes one location for each item - the current location. In the case of resource sharing, the current location for the item is the temporary location. Therefore, when you search from a local scope, items in the resource sharing location are not found.

    We would like to have the scope reflect the permanent location not the temporary location.

    We have a scope for our Teaching Materials Collection which is specifically geared to our Education major students. They are taught to use this scope in their instruction. Not finding materials in this scope that are on loan via R/S (as…

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  4. Customize the Discipline Hierarchy for "Personalize Your Results"

    We would like to customize the "Personalize Your Results" service in Primo UI in order to change the display and hierarchy of the existing disciplines. Currently, discipline labels can be customized, but not rearranged. However, depending on the country, history and traditions, institutions may have a very different approach towards disciplines and their hierarchy.
    We have patrons who do not understand why ‘Physics’ does not belong to ‘Sciences’, why ‘Public Health’ is not under ‘Medicine’, etc. This request aims to give the customers the possibility to create their own hierarchy, not to create or merge disciplines nor to have any…

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  5. Hide completed purchase requests from the Primo MyAccount

    Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Primo VE  ·  Admin →
  6. Allow libraries to configure the Brief Record Display with more flexibility

    In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).

    We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to…

    135 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Primo VE  ·  Admin →
  7. Add ability to select multiple options on Advanced Search drop down menus in Primo VE

    It is not currently possible to select multiple options on an Advanced Search drop down menu is Primo VE (ex: Material Type, Language); this functionality would be very helpful for users who wish to do more precise searching -- especially since Primo VE lacks the functionality of combining search results. This functionality is the HTML select multiple attribute (https://www.w3schools.com/tags/attselectmultiple.asp)

    56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Admin →
  8. Skip Primo log in when the user has already logged in through Open Athens

    When users log in through Open Athens they still have to click on Primo Log in button

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  9. Primo VE: Ability to search by publisher (advanced search or facet)

    The MARC 260b + 264b field is not included in the out-of-the-box indexing in Primo VE advanced search or facet as PUBLISHER. According to the documentation the publisher name is searchable only by general in the simple search and not in the advanced search, specific search for the publisher name. Readers want to limit the results by the name of the publisher.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →
  10. Journal A-Z and Database A-Z functionality based on a campus scope.

    On our current Primo we have Journal A-Z and Database A-Z functionality based on a campus scope. This is due to us having two Primo views - one for Cardiff University and one for NHS Wales. We share a catalogue but have created the ability for our users to search in Primo on a dedicated view depending on their affiliation; so that they receive search results only for items to which they have access. This split in search results includes the A-Z listings. And it is all based around a campus scope. We have been told that for our move…

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  11. Usage Statistics view on the Library Search/Primo for Alma D

    We know we can run usage statistics via alma analytics. The usage report is for the internal library staff to decide on different collections. I want to propose to add the functionality to Alma D, where everyone will see the usage report on Primo in a different facet. This is an essential feature, especially for the end-users. If the function is added, the end-users will be able to see the statistical report about the document/resource, i.e., When was the document/resource last used?
    Yesterday:
    Past 30 days:
    Total Views:
    Total Downloads:
    Total Uses:

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Primo VE  ·  Admin →
  12. Bib MARC field 505$t should be indexed in the Primo PNX file as a title entry

    The MARC 505$r is indexed in the PNX as Creator and contributor. The MARC 505$t is not similarly indexed in the PNX as an added or alternate title.

    157 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Primo VE  ·  Admin →
  13. Disturbing hover texts in Get It and Active Filters

    Hover texts in Primo VE

    In the "Get IT/Location" area in the copy view, all data (for example: section, callnumber, availability, ...) is output again as hovertext (white font with black, semi-transparent background) when hovering over it (see appendices 1-3). The same error also occurs with the Active Filters on the search results page (see appendix 4).

    This redundancy disturbs the user experience and already confuses users. In some cases, this phenomenon makes it impossible to see the entire text.
    I request that these disturbing hover texts be removed.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Admin →
  14. Visualización doble de registros con copias impresas y electrónicas activadas en Primo Central

    En los casos en que disponemos de un registro bibliográfico con ejemplares en formato impreso, copia electrónica activada en la "Comunity Zone", y además se ha activado también en Primo Central para garantizar la indexación y la capacidad de recuperación a nivel de texto completo, el registro bibliográfico se visualiza en Primo VE como si fueran dos registros bibliográficos exactamente con la misma información (códigos de barras, signaturas y ubicaciones duplicados).

    Según nos dicen desde SalesForce, debido a limitaciones/arquitectura del sistema, no es posible combinar el registro de Primo Central con los registros locales en Alma, lo cual crea confusión…

    63 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  15. Update Collections Automatically with Changes to Logical Set

    It is currently possible to manually add contents of a Set to a Collection that will appear in Primo.

    We would like to make it possible to create dynamic Collections that change/update when new items are added that meet the criteria to be added to the logical set.

    Right now, as the logical set changes, the Collection contents remain unchanged.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  16. Add DOI and PMID to Advanced Search Indexes in Primo VE

    DOI and PMID searching can be augmented for enhancement in keyword searching in Primo VE, so that these identifiers can be searches as keywords. It would be very helpful to our researchers to be able to more efficiently and exactly search within Advanced Search fields for DOI and PMID. These fields can be searched within unique fields in the Citation Linker, so the indexes exist, but they are not available for inclusion in Advanced Search settings. We would like to be able to add DOI and PMID as options in Advanced Search settings in Primo VE.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
  17. PrimoVE - allow search scopes defined by Ex Libris and local search scopes to be combined

    It would be great to allow search scopes to be combined in PrimoVE so that predefined search scopes and local search scopes can be configured to search as one scope. Currently, PrimoVE is not able to do this and makes searching more complicated to educate end users on how to search.

    For Example, Allow 690 and 6XXs to be able to be search all under Subject. Curently Subject does not include 690.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
  18. Customize the "View full text in collection" label in CDI

    Primo VE shall allow the library to customize the "View full text in collection" label in full record display page under view it section. There are different kinds of "link text" displayed in CDI mode which makes our users very confused.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
  19. 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.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo VE  ·  Admin →
  20. Add display field Contributor to Fields boosting in Primo VE

    Fields boosting in Primo VE has not an option for Fields boosting of display field Contributor. The default rule for Contributor is including 700, 710, 711. As an example, that means if you boost the creator field for a book with three authors the second and third author in field 700 will not get boosted, just the first author in 100.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo VE  ·  Admin →
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base