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

    284 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 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).

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

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

    121 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Primo VE  ·  Admin →
  4. Ability to select/set preferred record criteria for dedupe/FRBR in Primo VE

    We have instances where records for print materials in our holdings are combined with records for e-resources, to display a single record with multiple access points in our catalog. That is good and expected. However, often the source record is an e-resource record rather than the record for our physical holding, and we would prefer that the record for our physical resource be used so that important local notes are sure to be displayed. When the record for an e-resource is used instead, our local notes are not displayed, and that is a big problem.

    72 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo VE  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base