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

77 results found

  1. Reinstate ability to customize header/footer HTML and no results HTML file functionality in New Primo UI

    Would like to reinstate the ability to customize header/footer html files as well as the ability to customize the no results html file in the Primo New UI please. In the Old UI, you could customize and upload these files individually. You cannot customize any of them in the New UI, even if included in the customization package html folder. Would like to have those files included in the customization manager.

    We would like this ability because some code needs to run first (which case it would be included in the header) or last (when you would include it in…

    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)
  2. Make Relevancy Ranking values available

    To assist with the fine-tuning of Field Boosting, provide a way of showing the values of the rankings of search results.

    I.e. When a search is performed, for each hit make its total ranking value viewable either
    - to users,
    - in a comment in the page's source HTML, or
    - by amending that items URL (similar to &showPnx=true).

    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)
  3. copy a normalization rule set from sandbox to production server

    We need the possibility to tranfer NR testet in the sandbox environment to the production server.

    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)
  4. Allow Primo/Primo VE View customization packages to accept .db files and .DS_Store

    The view customization packages for Primo and Primo VE do not allow .db files. When someone opens a folder with images, Windows automatically creates a hidden Thumbs.db file. MacOS creates similar .DS_Store files.

    This file can be difficult to remove even with rights to view and delete the file, since Windows will sometimes indicate the file is in use and cannot be deleted.

    Rather than jumping through hoops to recreate the customization package structure and carefully place images only in the desired folders never to be opened again, I would propose that Primo and Primo VE accept customization packages that…

    7 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. Allow upload of SVG image files via File Uploader

    We have had some design work done for us and were supplied with a number of SVG format image files. The current Primo File Uploader does not support SVG format image files, but it should.

    7 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. [Primo] - ask for confirmation when running delete pipe

    Right now, when clicking on 'Execute', the Pipe starts immediately.
    Especially in the case of 'delete' pipe, a popup asking for confirmation could help preventing unwanted deletions from the system.

    7 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. Make integration with Alma more seamless in regard to the PCI and Link Resolver

    When we activate our Link Resolver databases in Alma, we have to do it all over again in the Primo PCI. This is redundant effort. Yes, it is one time, but new libraries have enough else to do to configure the system and this seems like an unnecessary step.

    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)
  8. Consortia environment; Provide inheritance for open access collections

    At present, open access collections that are activated by the consortia account are not "inherited" by individual members of the consortium. Given the number of open access collections, and the possible number of consortia members, it can be a tedious task to activate a large number of OA collections for each member.
    We would like to see that OA collections can be "inherited" as well, just like regular subscription collections.

    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)
  9. En Alma Digital se requiere que los campos MARC 5XX se desplieguen diferenciados

    En el perfil de metadatos desplegados en Alma Digital, se requiere que los campos de notas se puedan diferenciar. Actualmente se unen los campo 505 y 520 en "Descripción" y todos los otros 5XX en "Notas".

    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)
  10. Add toggle switch which requires IP validation to grant access to PCI paid content

    Primo allows authentication via access from a specific IP address range or patron login. Once authenticated, patrons can search paid content (from subscription databases) in the Primo Central Index. We are not an academic institution, therefore we do not have a fixed population of patrons in the form of students. In MetaLib our patrons could see paid content in search results only if they were onsite.

    We propose that a toggle switch be added to the Back Office, at the institution level, which would allow us to require IP validation for access to PCI paid content. Thus, being signed in…

    5 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. Backoffice REST API and Hooks

    Alma provides a growing number of API's for process orchestration and Hooks will come soon.

    Primo only provides REST API's which are mainly used for Frontend interaction.

    Primo is missing API's and Hooks to control Tools, Pipes, Processes and Schedules to implement fully automated workflows for Alma or other ILS.

    I would be great to see such API's and Hooks soon, please vote!

    5 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. Show last edit date in Manage Customization Package tab for Primo VE View

    Currently, the manage customization tab shows no information about when the package was last updated. I suggest adding information in the display area that shows "Package last updated: YYYY-MM-DD," preferably with the user's id.

    5 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. Set default language in Primo Back Office

    It would be useful if Primo Back Office users were able to set their own default language preferences (e.g. for content of the code tables) rather than have to select the language every time.

    5 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)
  14. Allow configuration of multiple email addresses in back office

    In primo's general configuration, there is a field for a staff email address. This address is used for emails which are generated by primo in response to an issue (e.g. when an IP is automatically blocked because it is suspected of being the source of a DoS attack) and is also displayed to users of primo when an error page is shown. We would ideally like to be able to send these to different email addresses so they can be processed differently. Would it be possible to add a second email address into the primo configuration and use that for…

    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)
  15. Allow deletion of old unused pipes

    We've got a long list of pipes, including some from an old repository we don't have anymore, and one I accidentally created with the wrong type (regular instead of delete-and-reload). These clutter up the list and make it harder to find the ones I actually use. It would be really good if we could delete the ones we don't want anymore.

    (Or at least to be able to hide them, or if nothing else then to be able to rename them to "zzzDON'TUSE" or something.)

    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)
  16. Make persistent search history opt-in instead of opt-out

    Make Persistent search history an opt-in instead of opt-out when enabled by a library.

    If a library enables the persistent search history in Primo VE, the feature is automatically turned on for all patron records. It would be helpful if patrons who would like to use the persistent search history feature could choose to opt-in to it instead of requiring users to opt-out of it.

    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)
  17. Primo VE: Add the ability to configure different availability messages by location

    We would like to be able to configure availability messages by location. For example, if there are no items, the message "Ask at the Reference Desk" displays. We have a few locations (one for digital materials and one for citations) that do not have physical holdings, so we don't want this message to display for those locations.

    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)
  18. Send an automated confirmation email after a booking request has been successfully placed

    Currently Primo has a nice feature that allows patrons to book items after they log in to their library account. It is called booking request in Alma and Request Item in Primo. We use it to let our patrons book equipment. However, it doesn't send out an automated confirmation email after a booking request has been successfully placed. We request to have this feature (i.e. the system sends out an automated confirmation email to the patron after a booking request has been successfully placed).

    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)
  19. validate normalization rules during saving

    It would be good if during saving a rule ore a rule set a validation is running to check if the NR is consistent ( such as the existance of all used tables)

    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)
  20. add otb support for iso 639-3 languages in Primo

    Primo currently supports iso 639-2 values for languages.
    We would like a support for the broader iso 639-3.
    Iso 639-3 is much richer.
    For example in our library we have more and more materials written in Ladin of the Alps, which is not the iso 639-2 Ladino (a language with the same name but spoken in Spain) but is instead the Ladin lld in iso 639-3.
    As a language iso 639-3 lld is a subset of the broader iso 639-2 roh family. But using just roh is quite a lack of granularity for us.

    Other customers around the world may…

    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)
  • Don't see your idea?

Feedback and Knowledge Base