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. Resource Recommender / searchable tags / language code table

    If you want to use the Resource Recommender feature in more languages than just English, you have to put all tags into the "Searchable Tags" box of the English interface. If you change to another language, the box is greyed out and can't be edited.

    I would like to suggest an overhaul of this part of the RR to make the "Searchable Tags" just as avaible for other languages as title and description are.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  2. Dedup process - Create Additional data PNX fied based on prefered record

    In dedup process, all fields from Additional Data section are merged and duplicate fields are removed. This design choice cause some issues with Citation service. When you merge records from differents sources, there is a strong possibility that data are not exactly the same and some data are duplicated. This problem may often be solved by choosing fields from prefered records as it is the case for display section

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  3. Ensure a title level general hold request only activates a request on the relevant holdings and campus for correctly affilated patrons.

    This crosses Alma and Primo but it surfaces as an issue for us mostly in Primo.
    Currently general hold requests are not checked against terms of use. So Primo/Alma applies the request to all holdings regardless of whether the patron can borrow the item or not.
    As an institution with two distinct campuses (NHS and University) we have issues with requests where some of the holdings have no items attached.
    For example we have a journal that has holdings at several libraries at both the NHS and Cardiff University campuses. Some of these holdings do not have any items attached. …

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  4. Calculate item level availability

    For most Primo Central Index collections, availability status in Primo is based on your activated portfolio holdings in Alma. These holdings calculate availability at the publication-level based on the coverage entered.

    Currently it is not possible to calculate availability in a way that recognizes item-level exceptions, such as when aggregator sources do not receive certain article types ('secondary' articles, brief articles, reviews, etc.) from the original publisher.

    The proposed idea is to calculate availability at the item-level.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  5. showPnx page as XML

    In the classic UI, if you added the parameter showPnx=true, in the address bar, to the URL of a record's full display, you were able to get an XML file with the PNX version of the record. In the NUI, on the contrary, the same parameter takes you to a web page containing the PNX record in a textarea.
    The XML view of the PNX record was very much easier to manage: colouring of tags, open/close section as well as you need them, etc.
    Why did you change this behaviour for worse?
    Could we get back the XML version of…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Admin →
  6. Update Primo Central more frequently

    As part of our implementation we have been making changes to our holdings in Alma. Following this we often see resources in Primo that are showing up in our full text results but are not available.

    We are told this is because the holdings file, that the results are based on, is only updated once a week. It is produced on Wednesdays and then is applied the following Monday.

    A more frequent update of the holdings file would be very useful as it would ensure that our users i.e. students and staff are more likely to get accurate information when…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  7. add date/time stamps to indexing & hotswapping sections of Job Details Report

    In the job details reports, where indexing and hotswapping are reported, there is no date/time stamp to indicate how long these portions of the job took to run. It's useful for guesstimating the length of a process before we start it and other sections like FRBR and DeDup include this information

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  8. Number of location codes that can be included in a scope.

    Scopes currently allow only 3 location codes. We would like to have that limit increased.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  9. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  10. Add Knowledge Unlatched content to PCI

    We would like to see Knowledge Unlatched fully indexed in the PCI to enhance discovery for all of the materials in this Open Access collection.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  11. fix Primo's proxying functionality so it can handle encoding

    Propose a solution to this problem: When people try to access content from Primo to Artstor, they are being authenticated into our proxy. After initial authentication into proxy, patrons are not linked to the Artstor result; they are shown an error page (Artstor error), or a generic Artstor resource page--not the actual result. Now that they are logged into the proxy, if they try to access the same link from Primo again, they can get to the result in Artstor properly.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  12. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Admin →
  13. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  14. Use non-LC call numbers for journal categories

    This affects Primo/PrimoVE; but the job is in Alma.

    The new feature (as of Nov 2019) to browse a list of journals by category depends on the 050$a. This should be expanded to use the 055$a, 060$a, 070$a, 080$a, 082$a, 083$a, 084$a, 085$a, and 086$a. Additionally, libraries should be able to pick which of the subfields to use.

    This is an example of the lack of support for non-LC libraries.

    This idea cross-posted as Alma idea.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  15. Display order: side by side instead of top-down

    In Primo, allow the option to display to show print and electronic results side-by-side instead of one after the other. Also apply to link resolver results.
    (Currently using Alma and Primo, not Primo VE.)

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  16. bX: Display dates for recommended articles in Primo VE brief results

    Article dates do not display in brief results related to bX article recommendations. The dates display in the bX sidebar, but when a user clicks on a bX recommended title, the date is missing from the brief results. It was noted that this configuration is currently hard coded and not configurable.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  17. Request: Please make it possible to find a match only by a title in Alma linkresolver

    What I want is to make Alma link resolver find matches by a title. Now, Alma linker resolver is returning results only when ISSN/ISBN is given. And, a lot of CJK titles don't have ISSN/ISBN so that there are many occasions when a subscribed CJK portfolio without an identifier is not found in Primo service page. Unlike Alma link resolver, 360 link resolver supports title searching. This is the example of 360 link. The URL below doesn't contain ISSN information either but, it finds the correct match.

    360 Link resolver:
    http://kg6wg8ak8z.scholar.serialssolutions.com/?sid=google&aulast=이영호&atitle=한국학 연구의 동향과'동아시아 한국학'&title=한국학연구&volume=15&date=2006&spage=9

    but, Alma link resolver doesn't…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Admin →
  18. 776 first indicator and display

    The first indicator for the 776 field specifies whether that field should be displayed or not. I added some 776 fields with a first indicator 1 (do not display note) yet this field is displaying in Primo. I would suggest that when 776 is used with a first indicator 1, this field does not display in Primo as per MARC (see link below)

    https://www.loc.gov/marc/bibliographic/bd776.html

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  19. Support Microsoft Edge for Primo

    According to documentation (https://knowledge.exlibrisgroup.com/Primo/ProductDocumentation/Primo/NewPrimoUserInterface/010FrequentlyAskedQuestions#Browser_Certification), Ex Libris does not support Microsoft Edge for Alma.
    The use of Edge is growing and should be considered a major browser, and therefore supported.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base