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

490 results found

  1. Fiscal/Calendar Year fields for Primo Analytics

    Please provide the fiscal year and calendar year fields for Primo Analytics. To show trends, it is helpful to compare by fiscal/calendar years.

    12 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. Show only Uniform title when FRBR key contains field 130 information

    When records are grouped together in Primo VE because they have the same uniform title in MARC field 130, the display of the title and creators in the Brief results display for this group is not ideal.

    The group shows the title and creators of one of the records in the group, which can be confusing to the user.

    What would be more ideal in these cases is that when the Uniform Title is used to generate the FRBR key, to only display the Uniform title from field 130 in the Brief results display for the grouped records, and no…

    4 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)
  3. Sort Book Chapters in correct order when using PrimoVE in 'Everything' search

    When using the ‘Everything’ search in PrimoVE you can't consistently sort book chapters into the correct order. Even when using the facets to filter and sort results, it still returns chapters in a variety of orders.

    For example, searching for the following book and filtering by ‘Book Chapters’, refining the year to ‘2015’ and sorting by ‘Title’ still returned the chapters in the wrong order (see attached screenshot).

    “Meeting Health Information Needs Outside of Healthcare” Kreps, Gary L.; Neuhauser, Linda (2015)

    It may not be possible, due to the variety of way book chapters can be structured. However, if it…

    1 vote
    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)
  4. My Library Card: Digital LOANS

    It would really be helpful to have a tab or include borrowed digital books under patron loans so that its easy for them to renew or see what digital books they borrowed and need to return. Currently there is no ability for a patron to see what digital books they may have borrowed and need to return.

    3 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)
  5. Primo VE webhook search blending

    In terms of usability, it would be good if Primo VE webhook search results could be blended to the combined search results (local resources and articles). Blended results feature should be able to select on a search-by-search basis e.g. if you apply search for AI-based article search portals or whether to apply search for printed resources from the repository libraries.

    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)
  6. Enable user personalization for their default "Expand my results" and "Search in full text" options

    Currently, institutions set a default for "Expand my results" and "Search in full text." Users can toggle these settings, but unlike other filters, these toggles are not "sticky" and it does not seem possible to "lock" them. When the session is reset or the user selects "New Search", the institutional default is re-applied. The user who prefers other settings must therefore constantly re-toggle their desired options.

    We find vastly different needs between our faculty, graduate students, professional practitioners, and undergraduates in their search behaviors and preferences. Currently, we have default settings designed for the least sophisticated searchers (undergraduates), but many…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Option to bulk export normalization rules Primo VE

    We would like to make a bulk export for backup of the normalization rules that we have set up in Primo VE.

    At the moment this functionality does not exist but would be very helpful for us. At the moment if we make changes to the normalization rules it is easy to accidentally delete the entire set of rules for one field. It is also not possible to easily roll back a change that we made.

    Therefore it would be useful to have the export option, to have an extra copy of all the normalization rules as a backup.

    2 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)
  8. Consistent UX or labelling for Collection Discovery search box

    Ideal solution: The Collection Discovery search box should be persistent and always search at the item level within all collections (as it does in the lobby) in order to provide a logical, consistent user experience.

    Secondary solution: the label text should be editable for each search box separately to make it clear what is being searched on the page.

    Problem:

    • The lobby search box is for everything
    • The top-level collection search box is for the title of sub-collections in that area only
    • The sub-collection search box is for items in that sub-collection only.

    Yet, all three options say "search" and…

    4 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. Streamline favourites by adding the ability to create labels from the item.

    It would be great if once you clicked the add to favourites button for an item you were either presented with a "Would you like to add a label" option, or the ability to add labels/tags from the ellipses menu, rather than having to go to the favourites menu.

    23 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)
  10. Separate the Primo My Account Update Login Credentials form into two different forms for PIN code and Password

    As a user, I would like to have two different forms for Pincode update and Password update (Update Login Credentials in My Account > Personal Settings) so I am sure that I can also change only one of the two. With the current design (=one form for PIN and password update), it is suggested to me that I always have to update both.

    10 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)
  11. Support "Exact year" date search in Advanced Search

    If a user knows the exact year they want to limit to, they have to type it in twice, whether they are using the facet option or the Advanced Search dropdown for Date Range. It would be helpful if the Advanced Search had a "Exact year" option with a single field to fill in.

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

    71 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)
  13. Change handling of MARC fields 100 and 700 in citation styles in Primo VE

    Handling of MARC fields in citation styles should be changed as follows:
    1. If there are relator codes in $4, only $4 aut and cmp should be considered as author, relator codes $4 edt, ill, ivr, trl and drt should be treated as contributors. Entries with other $4 codes should be ignored for citation.
    2. If there are no relator codes $4 in the record, field 100 should be considered as author, field 700 as contributor.
    Benefits: Citiation styles get independent from cataloguing language as they are now by using $e. Also citation styles work independent from the fact, if…

    8 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. Banner - start and end date

    We're using the banner to promote different library related events/workshops etc that run throughout the year. Currently we would have to manually enable and disable banners.

    If there was something that allows us to determine how long the banner would display then it would make it easier, and not having to make sure a member of staff is available on certain days of the year just to switch on/off a banner.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. API for customization package deployment

    Please add an API to deploy customization packages in Primo VE so that customers with many views can automate the cumbersome deployment process.

    101 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. Title in "digital collection" section

    In Primo VE, within the "Digital Collections" section, digital records currently display the entire content of field 245 as the title. This results in excessively lengthy titles for certain entries. Ideally, we would prefer that only subfield 245$$a be shown as the title within the "Digital Collections" section.

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

    37 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. Ability to place restrictions on Display Source Record link

    When enabling the ‘display source record’ link in Primo VE it would be useful to be able to specify which types of records the link displays or doesn’t display for. In our case we would prefer to restrict the option to our records for published resources so the private notes more typically associated with unpublished material such as manuscripts would not be publicly viewable.

    5 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)
  19. Advanced Search option in Collection Discovery for Alma-D

    Primo's public Collection Discovery pages currently lack the ability to run advanced searches. As a result, only keyword searches are possible at either the collection or sub-collection level, which prevents users from being able to limit or refine searches by necessary fields like Date, Creator, etc. This means that users have to browse collections, sub-collections, and items more broadly than is often helpful when an advanced search would be more likely to bring them immediately relevant results. Primo's Advanced Search for regular discovery is a valuable tool that should also appear in Alma-D's Collection Discovery.

    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)
  20. Expandable facets beyond the number we set

    Recently it has become possible in VE to display up to 50 facets. 50 tries the patience of the average user but may be what it takes to help those with more specific needs. In some cases CDI limits the number anyway. It would be better if more facets are available this could be noted at the bottom by a "more" link which would then display more than the default number. This would be more consistent with other ways Primo displays complexity.

    38 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)
1 2 5 7 9 24 25
  • Don't see your idea?

Feedback and Knowledge Base