289 results found

1. A-Z eBook functionality (similar to eJournals A-Z + databases A-Z)

   We're in the process of implementing Alma/Primo (at present we're Summon clients). Per Inna Ilinskaya, there is no equivalent ejournals/databases A-Z functionality for ebooks in Primo. This is something that our users have become accustomed to in using Summon. Inna recommended that we post this as an enhancement.

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Sort favorites by call number

   We'd like to be able to configure the sort-by options for favorites. We'd specifically like to be able to sort favorites by call number.

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Harmonise the default resource type icons with Leganto's icons

   Since we have both Primo and Leganto, our customers should have a consistent experience with resource type icons between the two interfaces. We have no choice but to use the OOTB icons in Leganto, a set of default Primo icons that harmonises with them would be appreciated. It may be that the size/canvas transparency may vary between them, but in essentials they should look the same where types are equivalent. With CDI we understand there will be additional resource types - this is a good opportunity to bring the two interfaces into a closer alignment for user experience.

   PS: Alma icons could stand an update too.

   Since we have both Primo and Leganto, our customers should have a consistent experience with resource type icons between the two interfaces. We have no choice but to use the OOTB icons in Leganto, a set of default Primo icons that harmonises with them would be appreciated. It may be that the size/canvas transparency may vary between them, but in essentials they should look the same where types are equivalent. With CDI we understand there will be additional resource types - this is a good opportunity to bring the two interfaces into a closer alignment for user experience.

   PS: Alma… more

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Sort by library in the Location facet when library name is configured to display

   When the option to display the library name in the Location facet is configured, we would like the Location facet to be sorted alphabetically by library.

   Currently, the facet list is sorted by location, which means that results for the same library are scattered among the list. For a user it would make more sense to have all the locations from the same library listed together.

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. New tool 'Give us feedback' - allow files to be uploaded

   It would be helpful if the new 'Give us feedback' widget allowed users to upload files when reporting issues. Our current in-house widget allows this and we have found it a useful feature.

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Allow customization of "Show source records" feature

   Since february 2017 relase, it is possible to display MARC record in UI, using "Show source records" feature. As this feature was very much in demand with our users and librarians, we are very pleased.

   Unfortunately, the feature's look and feel doesn't live up to our expectations. In the attach file, you can compare the display our users are used to and the actual display of "Show source record". It lacks of clarity.

   It would be great to be able to customize this feature's display in order to adapt it to our users needs and to preserve the consistency of our display. Currently this not possible according to the answer given in case #393118.

   Thanks for support !

   Since february 2017 relase, it is possible to display MARC record in UI, using "Show source records" feature. As this feature was very much in demand with our users and librarians, we are very pleased.

   Unfortunately, the feature's look and feel doesn't live up to our expectations. In the attach file, you can compare the display our users are used to and the actual display of "Show source record". It lacks of clarity.

   It would be great to be able to customize this feature's display in order to adapt it to our users needs and to preserve the consistency of… more

   •  

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Add Sort by Date to Favorites

   Currently the sort options in the Favorites list are: Date added, Author, or Title.
   Our users would like to be able to sort by date-newest like they can for search results. Many users are interested in most recent material so date-newest is a valuable sort option for them.

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Could the blank resource sharing request form check the Alma link resolver before a user submits the request

   We have configured the blank resource sharing request form into our Primo menu. Before submitting a request on this form it would be useful if the request was check against our institutional collection using the Alma link resolver (similar to what happens with the Citation linker).

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Add very compact display option, 1 row per title

   Please add a really compact additional display option
   – 1 row per title
   – no icon

   to allow an overview / quick scanning of long result lists.

   When I do a search on my laptop, I see two titles on the result list and the start of a third.

   ---

   Default number of results for the compact display should be 100 or more.

   And it should be a setting in the patron account.

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Table of Contents Display

    It would be nice to have the table of contents field (505) formatted in a more user friendly manner within PrimoVE. In Voyager there was a rule that converted the ' -- ' to <LF><CR> (which is 'Enter').

    I have attached examples of how it displays in our Voyager OPAC vs PrimoVE.

    • 

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Make the result list look ok when printed by adding a print stylesheet

    Yes, sometimes you actually want to make a print copy of the result list :) But if you try that (with the new UI), the result is a complete mess. I just tried printing a result with 5 results, expecting them to fit into one page. Instead I got three pages, and two of the results disappeared altogether.

    To make the result list look ok when printed, we need a print stylesheet. Of course every Primo customer can spend hours trying to make their own, but it would be much better if Primo could ship with a default stylesheet that made for an acceptable result. Navigational stuff like the header and the facets column should be removed, since you cannot make use of it on a print copy.

    Yes, sometimes you actually want to make a print copy of the result list :) But if you try that (with the new UI), the result is a complete mess. I just tried printing a result with 5 results, expecting them to fit into one page. Instead I got three pages, and two of the results disappeared altogether.

    To make the result list look ok when printed, we need a print stylesheet. Of course every Primo customer can spend hours trying to make their own, but it would be much better if Primo could ship with a default stylesheet that… more

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Allow libraries at primary Alma campus to be prioritized in Primo displays

    Currently on an item brief display, when multiple holdings exist, the availability statement shows whichever holding library comes first alphabetically, and on the results pages the Libraries facet lists libraries in alphabetical order. This alpha setup is problematic for multi-college / multi-library institutions that use per-campus Primo views. If the campus holds the item, its holding, not another campus that comes first alphabetically, should display in the availability statement. In addition, the Libraries facet should either prioritize the primary campus, or be sorted in order of number of hits (as most facets are) rather than alphabetically.

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Language field in Brief Record Display ought to use the Language codes Labels (VE)

    For institutions with multi-lingual collections, the out-of-the-box Language field can be a useful addition to the record display. When Language is added to the Full Record display, the "Language codes Labels" code table is used to convert the abbreviated codes used in metadata records into generally understood language names–e.g. the code 'gle' displays as 'Irish'.

    When the Language field is added to the Brief Record display, however, the labels are NOT used and the code is displayed as-is. Ex Libris recognizes this as a defect (case #06659538) but a solution is not part of the current development work plan. We are dismayed, as we hoped to add this field to our brief record display to remedy student difficulties demonstrated during usability interviews. The Language field is included in our Full Record display, but it is less visible there than it would be in the Brief Record.

    Scenarios where having the language label in the Brief display would be helpful for users:

    1. Students can have trouble distinguishing which titles are foreign language material because the metadata is primarily or solely in English. This sort of confusion can lead to item requests for material that a student cannot read and thus cannot use, which wastes the time of the student during their research, wastes the time of library staff who processed the request, and sometimes costs the library money for postage/fees incurred to process the request. For online resources, this confusion leads to inflated usage statistics that can be misleading for calculating cost per use and making renewal decisions. Image: eng metadata jpn contents

    2. Titles can be in a different language than the contents of the text while the record metadata is in a third language. Numerous older titles, for example, are in Latin, which can be misleading about the linguistic nature of their contents. This confusion has similar impacts as described in the first scenario. Image: eng metadata latin title irish text

    3. The Language facet is not sufficient to distinguish the primary language of the material from the presence of supplemental text in that language, like subtitles on a film. Patrons who are seeking resources in specific languages can be frustrated by this. For example, the film Parasite remains in search results after the English language filter is applied, even though the dialogue is in Korean and French while English is only present as subtitles. In those same filtered results, you can see the film Transfer, which is in German and French. Image: eng filter koreanFrench dialogue

    Since the code is displayed in the Brief Record, we cannot add it for our users–it would cause more confusion than it would resolve. The out-of-the-box Language field needs to be fixed so the "Language codes Labels" code table is invoked for the Brief Record, as it is for the Full Record.

    For institutions with multi-lingual collections, the out-of-the-box Language field can be a useful addition to the record display. When Language is added to the Full Record display, the "Language codes Labels" code table is used to convert the abbreviated codes used in metadata records into generally understood language names–e.g. the code 'gle' displays as 'Irish'.

    When the Language field is added to the Brief Record display, however, the labels are NOT used and the code is displayed as-is. Ex Libris recognizes this as a defect (case #06659538) but a solution is not part of the current development work plan. We… more

    •  

    •  

    •  

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Citation generator is inaccurate

    The citation in the existing and new UI for books is not valid MLA or APA.

    The PNX information that populates the citations is stored in a hidden mapping table that cannot be edited. For example, I can see that series information for a book comes from addata/seriestitle. Primo will use the entirety of the field in the citation. For this particular record, this is the content of that section:

    Rowling, J. K. Harry Potter Ser. ; 2.

    Likewise, book titles come from addata/btitle. For this record, this is the entirety of the section:

    Harry Potter and the Chamber of Secrets / by J.K. Rowling ; illustrations by Mary GrandPré.

    Because the content of the citation is based on fields in your records, you might want to examine your normalization rules for the addata section and see which fields from your source record are being used. Since you're seeing extraneous information in the citations, this might require changes to your source data or to the normalization rules (to pull data from a different source field).

    If you want to change which PNX fields Primo uses to build the citation (for instance, changing from addata/btitle to display/title) this would qualify as an enhancement.

    The citation in the existing and new UI for books is not valid MLA or APA.

    The PNX information that populates the citations is stored in a hidden mapping table that cannot be edited. For example, I can see that series information for a book comes from addata/seriestitle. Primo will use the entirety of the field in the citation. For this particular record, this is the content of that section:

    Rowling, J. K. Harry Potter Ser. ; 2.

    Likewise, book titles come from addata/btitle. For this record, this is the entirety of the section:

    Harry Potter and the Chamber of… more

    •  

    •  

    •  

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Extend hypertext linking for Relation, Is Part Of, and Uniform Title to remote records

    Enhanced hypertext linking for ispartof, relation, and unititle was introduced in the November 2017 Primo Release. These new fields joined existing hypertext linked fields for creator, contributor, and subject.
    However, a key difference for the three newer fields is that they only show lateral links in the UI for local records. This limitation is hardcoded, and is confirmed but not explained (Case: 00486499).
    Like many sites, we have configured our Primo environment without search scopes with a source-agnostic design, with the underlying premise that users do not care who owns an item or where the record comes from, only that they can access the content.
    
    The limitation of this feature to local records causes confusion to users as to why one record has helpful linked fields, but another does not. It also actively hinders their use of this valuable relationship tool to bring together related content. As both informal and formal contextual relationships are an oft-mentioned increasingly strong focus for Ex Libris, restricting only some hypertext links to local records is a surprising design decision which does not place the user first.
    See attached a doc showing a local Alma record with the relation field hyperlinked for a series, and a remote PCI record for the same series where the relation field is not linked. In this instance, this is a series which has been published as both a journal and individual monographs, which are notoriously difficult for our users to understand and bring together cohesively.

    Enhanced hypertext linking for ispartof, relation, and unititle was introduced in the November 2017 Primo Release. These new fields joined existing hypertext linked fields for creator, contributor, and subject.
    However, a key difference for the three newer fields is that they only show lateral links in the UI for local records. This limitation is hardcoded, and is confirmed but not explained (Case: 00486499).
    Like many sites, we have configured our Primo environment without search scopes with a source-agnostic design, with the underlying premise that users do not care who owns an item or where the record comes from, only that… more

    • 

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Auto correct typos

    Primo search should have the ability to auto correct common spelling errors and typos.

    A current review of our zero result searches has shown that many zero result searches are typos and misspellings.
    Users are used to systems that can auto-correct or suggest corrections for misspelled words.
    Auto correct of typos would greatly improve the user experience.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Adding a hierarchical tree display option to Collection Lobby

    Please add a hierarchical tree display option to Collection Lobby. When a top-level collection has many sub-collections across all depth level, it's too hard to browse individual collections and titles.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Make Journal titles hyperlinks

    Hi there, users would be helped if search results didn't just bring back links to articles but also had the journal title hyperlinked to take them to the journal's home page or contents page. To help further there could be text box that instructs the user to search for the article they're looking for in the journal's site. Deep links to articles are the most common to fail so this improvement would help students find the articles within journal/publishers sites. Saving time and making them give up less easily.

    Thanks for your consideration.
    Cheers, James

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Resource recommender

    Currently there isn’t any option to order resources other than alphabetically for the resource recommender.

    We have control over the order that the ‘Types’ of resources display by (e.g. Databases, People, Websites …), but as all of our resources are databases, we are limited to the default sort.

    Would like more flexibility on this.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Index local in Advanced search

    We have a local index with a closed list of values and we would like to present only this list of values to users doing an advanced search.

    An example with the local index "Original language" based on the 905 field. This field contains three possible values: Yes, No, Bilingual.

    We would like for an advanced search, when the user chooses the Original Language index, to present the closed list that shows three possible values: Yes No Bilingual

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Interface  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close