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. View full record in results view

    The current behaviour to move from search results to exploring a record is to open a pop up to view the full record.
    This takes the user away from the results set they are working with.
    There is feedback that some users dislike pop ups.
    We have also observed that many users open full records in a new tab in order to have records of interest open in tabs to go explore in detail later whilst continuing to work with the search results.
    To match user behaviour in exploring search results I'd like to suggest an option to open the…

    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  ·  User Interface  ·  Admin →
  2. Ability to search non-english (especially Scandinavian) characters in local data and CDI data in a consistent way

    A growing number of Central Discovery Index (CDI) sources contain the original non-english characters for specific languages, e.g. Scandinavian (Danish, Norwegian, Swedish) letters such as æ,ä, ø, ö and å. Searching the original Scandinavian letters works for both local and CDI data. However, searching non-English letters are cumbersome for foreign users. There are different ways to anglicize these characters. The traditional Scandinavian way is to use a "folded variant": "ä" -> "ae", "ö" -> "oe", etc. However, this only works for local data (institution zone). CDI use the method of simply removing the dots: "ä" -> "a", "ö" -> "o",…

    9 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 →
  3. Request in PRIMO VE - Terms of Use (TOU) selection appears unnecessarily

    When there is only one TOU in the Request, the option to choose TOU should not be displayed.

    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 →
  4. Search Limiters for Accessibility Features

    As a cataloger, I would like to propose a new option to filter search results for items with accessibility features (captions, audio descriptions, large print, etc). We are in the process of adding 041 subfields (mostly p and q), and 341 and 532 fields to our records in order to help users more easily identify items intended for those with hearing or visual disabilities. Ideally, this feature would utilize that input based on the presence of indicators in the 341 or 532 fields (i.e., 0 and 1) or controlled vocabulary terms to create search facets or indications (similar to the…

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Transformation routine to convert number range to list

    Have a transformation routine that will convert a range of numbers to a list. For example

    input: 3-8
    output: 3,4,5,6,7,8

    This would be very helpful in the search section, as users often search for a series and volume number, but if the series number is in a range they won't find it. E.g., this search will fail

    Series entry:
    The big series, v.24-35

    user search:
    big series 31

    With the new transformation, the search section of the pnx would have
    The big series, v.24,25,26,27,28,29,30,31,32,33,34,35
    and the search would work.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Poder configurar la ordenación de los items/holdings en Primo VE

    Primo no permite configurar la ordenación de los holdings o de los items asociados a un holding en la Vista completa del registro (sección Get It).
    En nuestro caso, tenemos holdings diferentes asociados a una misma ubicación y biblioteca. Primo VE no permite ordenar estos holdings por signatura (ver en la imagen adjunta el ejemplo número 1).
    Por otra parte, hay casos en los que muchos items dependen de un mismo holding. En este caso nos gustaría que se pudieran ordenar por disponibilidad, es decir, que se mostraran en primer lugar los items disponibles. En el ejemplo 2 del documento…

    16 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 →
  7. Add permalinks to Resource Sharing Form

    When a user submits a RS request for an item in Primo, it would be helpful to have a permalink as part of that form. There is a "Source" field, but that isn't helpful in tracking down the original record the user was on. If the metadata in the request doesn't parse into the form correctly (which it sometimes doesn't for less common material types) and the user failed to add more detail, it would be helpful to have the permalink.

    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  ·  Other  ·  Admin →
  8. Customize response page for error 404 resource not found

    To be able to customize response page for error 404 resource not found: either to be able to set up a customized web page with some informative text, or to be able to redirect to starting page of Primo

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Chinese records should be ordered by pinyin

    For the mainland China customers, it would be great that the Chinese records are ordered by pinyin when choose sort by "Title" or "Author" for result list.

    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  ·  User Interface  ·  Admin →
  10. "resource recommender"

    Provide the option to hide individual entries in the resource recommender from public view

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Add 'Not contains' to Primo VE Advance Search

    Please add the 'Not contains' search logic to Primo VE advanced search.

    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 →
  12. Journal search>Browse by categories : allow indexing of Unimarc journals (PrimoVE)

    Currently, only journals described in Marc21 are indexed by subject in Journal Search.
    The Unimarc community is now large in Alma/PrimoVE, and the Browse by Categories function would be useful if it took into account all formats.
    The idea would be to allow indexing of journals described in Unimarc, which have Rameau/LC subject fields in 60X and LCC field in 680.

    33 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 →
  13. Ability to merge deduped records in Primo VE

    In Primo VE, you can currently choose to display a preferred dedup record (in the full and brief display), either from Alma-P, Alma-E or Alma-D (or none, and the first record to show up in the result list will display).

    We would like to add the option to merge all local records. This is the default behaviour in Primo classic.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Admin →
  14. Item policy translations

    In Alma the Institutions have no possibility to add the translations for the policies. In multilingual consortia environments the only possibilities are to display in Discovery the policy description in English or to add all description translations in the same field. Neither these solutions are user friendly.
    The translations should be distributed from the Network.

    82 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 →
  15. Allow custom error pages if View Code does not exist

    Currently any unkown View Code in the URL (e.G: vid=PRIMA) leads to empty page and rotating diamonds.

    In the background Angular is unable to fetch the configuration URL /primo_library/libweb/webservices/rest/v1/configuration/PRIMA which is answered by an HTTP 406 error from the server.

    To the enduser its completely unclear where the problem is located, did she/he make a mistake or is there a problem on the server.

    I would suggest to provide at least generic error page (View Code not found) and respond by HTTP 404 or 406 to the client. This is also important for search engine crawlers if there are any…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Automatically reopen all the closed tabs after Primo timeout when sign in again

    Some of our patrons like to use Primo with many open tabs, each tab can contain one item they are interested in and want to read/check out. The problem is that if they spend longer time than the timeout limit (one hour for our instance), Primo will automatically log out and close all the tabs. And the patron cannot re-claim/re-open closed tabs after sign in again. It has been a recurring complaint and we think extending the timeout limit is not a good solution. Our expectation for Primo is that when patrons sign in again, the lost/closed tabs from the…

    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  ·  User Interface  ·  Admin →
  17. Make consistent the use of CDI record data in Primo UI

    Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
    This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.

    The negative impact of this design decision includes:
    * a user is confused by…

    67 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Have the option to configure portfolio views in VE to more than 25

    Classic Primo allowed this via Configuration > Resources > Other Settings > enableviewitshowall_results = true but this does not work in VE

    6 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 →
  19. Display on the Location list: textual descriptions of the physical arrangement of a holding unit

    Since the updates in January 2021, the Location list has become capable of displaying the Field 866, 852, etc.
    There are cases in which the issues of a single journal title are located separately according to publication years. Here we present a case example to explain the situation:
    Group 1: The issues published in the last several years; they are shelved in the “New Arrival.”
    Group 2: The issues published several years before the Group 1; they are shelved in the “Back Numbers.”
    Group 3: The issues published more than 20 years ago; they are shelved in the “Remote Storage.”

    20 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 →
  20. Please add to the PRIMO VE mapping table documentation the last update date and mark the new changes in red.

    Hello,

    We recently discovered that the Primo VE mapping table was updated with new information.

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/120Other_Configurations/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record

    It would be very helpful if you could add last update date and mark in red the new information, the same way that LC mark in red the new information in Marc 21.

    If you would apply this suggestion also to other documentation pages it would be great.

    Thanks,
    Dafna

    32 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 →
← Previous 1 3 4 5 44 45
  • Don't see your idea?

Feedback and Knowledge Base