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

405 results found

  1. fergusons

    Please add Fergusons Career Guidance Center to Primo Central Index and Alma Activation

    1 vote
    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)
  2. Allow Search Box Placeholder Text to Be Customizable by VIEW

    The search box placeholder text is customizable in the Code Table (nui.search.placeholder) but the change is global. It would be much more useful if the default could be set in the Code Table and then further customized in each view if desired. Or, if that isn't possible, to remove it from the Code Table and just make it a customizable field in each view. Or, if that isn't possible, at least a check box in the view settings that would allow us to remove/hide the placeholder text that was set in the Code Table.

    It's great that we can make…

    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)
  3. Improve Display Logic in Alma Uresolver to show all variant coverage statements in a collapsed menu

    Ideally, Alma should be able to display ALL unique variant coverage statements when showing a collapsed menu.

    If a library uses the Display Logic rules to for example show Proquest as an option only once in a services menu, this works very well where a journal may be in 12 Proquest databases with the same coverage.

    However, when the coverage varies significantly between these databases, Alma uresolver will still just show one of the coverage statements and a user will only see a subset of holdings and believe this is all the library has. (eg Nursing standard in Proquest is…

    159 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)
  4. Physical items sort routine by date - enable I J K descending, but A B C descending

    Hi
    We're running into a problem with the Physical items sort routine - Sort according to date.

    For journals, we want to sort the latest item on top, this works correctly with
    Sort according to chronology I/U/K (year/month/day) - Descending

    Example
    https://basel.swisscovery.org/discovery/fulldisplay?vid=41SLSP_UBS:live&search_scope=UBS&tab=UBS&docid=alma9910177740105504&lang=en&context=L

    BUT
    The same sort routine is also used for multi volume monographs.
    We found out that if we only fill out conditions for Chronology I J K, but those fields are empty, the barcode gets used for sorting.
    Which leads to wrong sorts.

    So we had to add
    Enumeration A, B, C as a condition.

    This leads to…

    0 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. Add Limiter to Select PCI Collections in Primo VE Advanced Searches

    I'd like to suggest that libraries have the option of adding a limiter to the advanced search area of Primo VE that would allow users to pre-select particular PCI indexes to search. Currently, this can only be done by applying the limiters once search results have been generated.

    It would be beneficial if users had the option of pre-selecting which PCI collections to search prior to actually running the search.

    0 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)
1 2 17 18 19 21 Next →
  • Don't see your idea?

Feedback and Knowledge Base