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

1133 results found

  1. System generated email: include the domain name in the body of message

    Currently system generated emails from Primo do not indicate which server they originated from. We have two servers, production and staging, and we think this is a common setup. In order to know which server the email came from one has to view the message headers. It would be helpful if the emails automatically included the domain name in the body of the message.

    2 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. e-shelf indication that items have been copied to clipboard ready for pasting

    e-shelf indication that items have been copied to clipboard ready for pasting. There is no indication available and when copying large amounts of items it is unclear as to whether they have been added to the clipboard or not so the user cannot tell when it is time to paste.

    1 vote
    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)
  3. Relais third-node adapter

    There should be a way to search consortium library ILSes using Metalib or a z39.50 third-node adapter. We are currently building a metalib quickset to federate search across the consortium. We hate relais' discovery service so we would like to keep users in primo. Currently, the relais link in the new UI is for known items. We would like to create a consortium based union catalog. Even better would be if this could get accomplished by daily automated harvesting within PCI (leaving d2d's web API to check availability and process the loan). If you think this would require additional resources,…

    1 vote
    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)
  4. Add link "Back to results list" on the e-Shelf

    This is the use-case I want to improve:
    A user is constructing complex queries and collecting some records.
    From time to time she wants to check the e-Shelf and then continue skimming trough the results list.

    ¡There is no simple navigation path from the e-Shelf back to the results list!

    There are 2 less-than-ideal solutions:

    1/ repeating the query from tab "This session's queries" (flaws: it is cumbersome to find the corresponding query and too much clicks are necessary)
    2/ the back button of the browser (flaws: the yellow e-Shelf star icons are not up to date and too much…

    25 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)
  5. Display "Sign in to check request options" message/link on a higher level

    Display the "Sign in to check request options" message/link on a higher level than for each location? That would make it much more visible for customers, instead of having to click on individual locations drop down links.

    3 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)
  6. Send e-mail to Primo administrator staff after a scheduled pipe was executed

    For many customers, especially SaaS ones that does not have direct access to the server, it is very important to know if a scheduled pipe is executed or not. The idea here is that the BO server send by email a summary of each pipe execution, indicating start and finish date and time, execution status and how many records were imported / deduplicated etc.

    8 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)
  7. Primo - "related titles sorted alphabetically by title" also for Primo direct / classic not VE

    In Primo VE one can have related titles sorted alphabetically by title
    This is particularly useful for multipart, journals, and in general complex record structure. Unfortunately, this is possible only in Primo VE, but not in classic Primo.
    It would be useful if the 2 versions of Primo were aligned also regarding this very useful feature.

    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  ·  User Interface  ·  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. Ability to collapse elements in full title display per view and per search scope slot

    Please add the ability to collapse elements in full title display
    - per view
    - per search scope slot

    We are in a consortium, and some information in the full title display is confusing for our patrons and we have no way to hide it.

    We would like a setting to collapse each element of the full title display separately. This setting needs to be configurable per view and within the view per search scope slot.

    Example:

    We have the search scope slots
    - our IZ
    - NZ & CDI

    Section 'Other loan and request options' should be collapsed in…

    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  ·  User Interface  ·  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. 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)
  10. 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)
  11. Option to have patron block notes viewable in Primo

    Currently, you can include a note in a patron's block in Alma, but that note won't display in Primo. You have the option of creating a separate note in the patron's record that is viewable, and the block type will provide the patron with some information, but it would be nice if we had the option to include a user-viewable note when creating the block.

    0 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. Automatic sync of library codes with scopes and static facets

    The Library Codes on the Institution page are currently automatically copied to the Library Names code table and the ILS Library Codes mapping table, which is great.
    We would like to have an option to automatically sync these library codes also with the Scopes and Search Scopes (used for searching, and Location drop-down lists) and Static Library facets mapping table, in order to eliminate the need for manually updating all library codes in the scopes and static facets.

    0 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)
  13. Allow the view code field to be editable

    To enable seamless updates to the Primo interface it would be useful for the Code for the view to be editable.

    This would allow you to continue to use the same public address for your Primo instance, but switch the view to a new one by changing the code in the Back Office. For example, it would allow you to switch from a the current live view to a new one.

    Currently the field cannot be edited (see screenshot).

    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  ·  User Interface  ·  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 53 54 55 57 Next →
  • Don't see your idea?

Feedback and Knowledge Base