545 results found

1. Adjust number of results Collection Discovery

   Collection Discovery pages are great but loading 10 at a time is not enough. Would like to see adjustable results dial similar to what was recently released in Alma. Perhaps even up to 100 results on a page would be sufficient.

   139 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…)
   7 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

2. Drag/drop results facets

   We would like to be able to let our users personalize their search experience by dragging and dropping results facets into different positions in the list. For example, our first facet is Show Only. If a user wanted to see Material Type or Publication Date first, they could simply drag one of those facets to the top of the list. Making those choices persistent through a session and/or through their own personal account would be even better.

   39 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 Functionality  ·  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. Dedup and FRBR cluster monitoring

   Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that add up to a score for each cluster. The Dedup Tools in Primo and Primo VE are helpful when a "bad cluster" is brought to our attention by a customer, but we should not have to wait for this to happen if the cluster size, or random sampling, can bring problems to light. Regular Primo customers need better tools that will provide a more usable output in modern spreadsheet or document formats, and VE customers need similar tools to sample and monitor clusters. If this can be part of Analytics that would be fine, otherwise a separate set of tools is needed.

   Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that… more

   34 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  ·  Administrative Tools  ·  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. Smart login messages - Do not show login message in the ViewIt for Open Access material

   If a user is not logged in they get the Login message on the ViewIt and GetIt tab, whether they need to login to access that resource or not.

   For example, Open Access material.

   We have had many instances of users complaining that they have to login to access OA material. In fact they do not need to login to access this material. The Primo login message is confusing and misleading the user to think that they do need to login.
   See for example the following Open Access material in our Primo instance.
   https://primo-direct-apac.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=RMIT_ALMA_DC11160517080001341&context=L&vid=RMITU&lang=en_US

   In this example the resource is available Open Access and anyone can access it without logging in.
   But Primo continues to display the Login message in the View Online section of the full record.

   To resolve this confusion can the login messages be made situation sensitive?
   If a record has an Open Access indicator can the Login message on the ViewIt section of the full record be hidden.

   If a user is not logged in they get the Login message on the ViewIt and GetIt tab, whether they need to login to access that resource or not.

   For example, Open Access material.

   We have had many instances of users complaining that they have to login to access OA material. In fact they do not need to login to access this material. The Primo login message is confusing and misleading the user to think that they do need to login.
   See for example the following Open Access material in our Primo instance.
   https://primo-direct-apac.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=RMIT_ALMA_DC11160517080001341&context=L&vid=RMITU&lang=en_US

   In this example the resource is… more

   34 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

5. Use of initial articles in title starts with searches in Primo Advanced Search

   Primo is currently unable to adequately accommodate initial articles (a, an, the etc.) when doing a title starts with search in Advanced Search.

   The first title field that appears in the sort section of the PNX is used as the title that is matched against when doing a title starts with search but this leads to different outcomes depending on whether the records are indexed from PCI or Alma:

   When the title field in the sort section of the PNX is created from Alma the default behaviour is to strip the initial article
   When the title field in the sort section of the PNX is created from a PCI record the default behaviour appears to be to retain the initial article

   This means that users cannot enter a title into this field that will accurately retrieve both PCI and Alma records as some titles start with an intial article and others do not. If the Alma records are adjusted so that the initial article is included then they will not sort correctly when sorting by title and users who fail to enter the initial article will not find the title they are looking for.

   Primo should allow users to enter titles into the title starts with search box and it should retrieve all results that match the search terms regardless of whether the user has entered the initial article or not. Users should not be expected to enter titles with an initial article and then to do a separate search for titles without the initial article to ensure they have a complete set of results.

   Primo is currently unable to adequately accommodate initial articles (a, an, the etc.) when doing a title starts with search in Advanced Search.

   The first title field that appears in the sort section of the PNX is used as the title that is matched against when doing a title starts with search but this leads to different outcomes depending on whether the records are indexed from PCI or Alma:

   When the title field in the sort section of the PNX is created from Alma the default behaviour is to strip the initial article
   When the title field in the sort… more

   41 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 Functionality  ·  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. Change order of holdings for e-journals in ViewIt

   Allow the institution to determine the ordering of resources in the ViewIt section of Primo. The single select options would include:
   • By Date – Ascending
   • By Date – Descending
   • Alphabetical
   • (Not sure if there are others)

   Currently e-journal titles with multiple holdings are displayed in alphabetical order. When each holding has a different date range, it can be difficult to scan quickly. This would allow each institution to select what works best for their users.

   55 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

7. Control Purchase Request Display in Primo by Material Type

   Using display logic rules there is no easy way to show the Purchase Request link based on material type. We want to enable the purchase request link for ebooks, but not ejournals. I did come up with a hackey workaround by creating a GES that only does the identification of the journal and then a display logic rule to hide the purchase request if this GES is present, but there seems like there should be a better way to do this?

   197 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…)
   11 comments  ·  Primo VE  ·  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. Can Noodletools be added into Primo as a citation tool?

   We want Noodletools added into Primo for citations

   72 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…)
   10 comments  ·  Integration with other systems  ·  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. Restrict discoverability of e-resources for walk in users to those resources they are licenced to use

   We're looking to restrict the discoverability of electronic resources for walk in users to those resources they are licenced to use.

   Ideally, Primo would identify that the walk in users were from a certain IP range and in combination with an Alma licence
   condition which allowed walk-in use to the resources, it would allow them to discover the resource.

   41 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 Functionality  ·  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. My Library Account: add Recalled Loans Tab

    It would be very beneficial for library patrons to be able to view their recalled loans, at a glance, when checking their library account in Primo; please could you add a Recalled Loans tab to the Overview section of My Library Account

    165 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…)
    6 comments  ·  User Functionality  ·  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. View Primo as someone else / different types of users

    View Primo as "someone else". It would be useful to view our Primo-page as different types of users. Being able to view Primo as an internal user, or a student, or staff member, or an external user, would help us troubleshoot configuration and settings in Alma. Have we activated the right functionality for the different user groups? Have we hidden what we want to hide?

    tl;dr: Facebook's "View as" functionality in Primo.

    56 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  ·  Administrative Tools  ·  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. Make the New Primo UI more CSS friendly

    While the new Primo interface gave us more power to extend functionality via JavaScript it does not do the same for modifications via CSS due to the lack of properly marked up content.

    In some parts of the New UI the content is well described, often with custom HTML elements, but there are also many places, often in the higher levels in the DOM tree, where better described selectors (preferably through classes) are needed.

    For example, there is currently no selector that show the current system that is being displayed. The <prm-explore>-element could have the current system being shown as a class (search, fulldisplay, openurl, jsearch, account, login etc).

    In the search results the <div.list-item-wrapper> element is used on the parent level. Here the markup would be greatly improved by adding the media-type such as article, book, text_resource etc. Allowing us to style based on media-type.

    It's the same with facets. There's currently no way to target a specific Facet Group with CSS. The first real identifying selector is on the span[translate="facets.facet.facet_XXX"] that is several children down. Having this as a class or other attribute on either the repeating parent <div> or the <prm-facet-group> would help.

    In My Account the <md-tab-content> could use the same treatment. Here the section could be added as an attribute, e.g. overview, fines, blocks_messages etc.

    These are just a few examples where better selectors would be helpful. The best would be if the entire UI got the treatment with better selectors and modifications via CSS in mind. While JavaScript is powerful it is not the correct tool for everything.

    While the new Primo interface gave us more power to extend functionality via JavaScript it does not do the same for modifications via CSS due to the lack of properly marked up content.

    In some parts of the New UI the content is well described, often with custom HTML elements, but there are also many places, often in the higher levels in the DOM tree, where better described selectors (preferably through classes) are needed.

    For example, there is currently no selector that show the current system that is being displayed. The <prm-explore>-element could have the current system being shown as… more

    90 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. Browses: add See Also and Usage info from authority headings

    Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used.

    We propose that See Also and Usage info display in the Browse headings.

    Example headings and See Also and Usage info that does NOT currently display in Primo:

    Blacks:

    Search also under: subdivision Blacks under individual wars, e.g. World War, 1939-1945--Blacks; and headings beginning with the word Black
    Here are entered works on blacks as an element in the population. Theoretical works discussing the black race from an anthropological point of view are entered under Black race.

    It's possible this enhancement could be achieved through application of an API that interacts with Library of Congress systems. Display of narrow/broader terms would also be highly valuable.

    Primo supports display of See references (not same as See Also) in browse headings, if those cross-references are in the bibliographic data ingested by Primo. There is no capacity to display See Also and Usage info from authority records, which are important so that users understand how and why certain terms, especially subjects, may be used.

    We propose that See Also and Usage info display in the Browse headings.

    Example headings and See Also and Usage info that does NOT currently display in Primo:

    Blacks:

    Search also under: subdivision Blacks under individual wars, e.g. World War, 1939-1945--Blacks; and headings beginning… more

    205 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…)
    6 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

14. Subject Browse - allow merging of identical subject terms from different vocabularies

    Right now, when I browse in my Primo by subject, I'm seeing a lot of subject headings repeated from different taxonomies. For example: Microbiology (EBPS), Microbiology (FAST), Microbiology (fast MESH), Microbiology (LCSH), Microbiology (LCSHKIDS FAST), Microbiology (MESH). This looks like a mess and is confusing for the user. I'd like to propose that where subject headings are identical between taxonomies, they be merged into one entry so the user doesn't have to check them all.

    39 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

15. Sort purchase requests in Primo, by newest

    It would be really helpful if user were able to sort their purchase requests in Primo by purchase-request creation date newest. Now Primo shows their purchase requests sorted by oldest, normally the user wants to see the follow up of the most recent.

    53 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 Functionality  ·  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. course reserve

    Course Reserves:
    Requested Enhancement: Offer interface with drop-down menus for Course Title, Course Department, and Course Instructor (similar to drop-down menus in Voyager)

    Currently users can search for course reserves, but there is not a good mechanism to browse. Offering drop-down menus would easily allow users to see what was currently on course reserve by course title, department and instructor.

    Thank you for considering

    305 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…)
    9 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. Displaying the pre-filters used, as the used facets are dispalyed

    It would be very useful to display the pre-filters used in Primo New UI (from both simple search screen - as of May release and advanced search screen). Pre-filters used should be displayed in the brief results list just as the facets used are displayed, at the top of the column. Thus the patron can always see and be aware of all the active filters in the session

    62 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…)
    7 comments  ·  User Functionality  ·  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. Improve usability of exclude/include facet options

    Based on recent usability testing of the new UI we have found that our users appeared to be confused about how to include and exclude facet options from their results set. One of the main pain points seemed to be that they did not know that they were able to exclude a specific facet option (for example to exclude English items from the results set most of our users ticked all options under the language facet other then English rather then just excluding the English option).

    At the moment the option to exclude only appears when someone hovers over the facet option, and it appears on the right of the text of the facet option. Although the option to include a facet also only appears when the mouse hovers over the text of the facet option because it appears on the left of the text it is more obvious, as users will be reading left to right, then something that appears after the text.

    We feel the overall usability of the exclude/include facet option functionality could be improved by:

    1. Moving the exclude option so it is next to the include option on the left of the facet options
    2. Both options are made static so users are aware there are filtering options without the need to hover over the text of the facet option.
    3. Currently a tool tip exists for the exclude option, but there isn't a equivalent tool tip for include. We would like a tool tip to be available for both options.

    Based on recent usability testing of the new UI we have found that our users appeared to be confused about how to include and exclude facet options from their results set. One of the main pain points seemed to be that they did not know that they were able to exclude a specific facet option (for example to exclude English items from the results set most of our users ticked all options under the language facet other then English rather then just excluding the English option).

    At the moment the option to exclude only appears when someone hovers over the… more

    119 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…)
    15 comments  ·  User Functionality  ·  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. An option to move the send-to section in Primo VE

    We would like to be able to control the location of the send-to section in the Primo VE full record display.

    101 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…)
    15 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. Optimize call number Advanced Search

    Currently you can conduct an advanced call number search, but there are a few issues with it:

    -It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.

    -The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of our 3,578 items. Most users would not think to search with an asterisk.

    -When limiting an Advanced Search by Call Number, the only limiters available are Contains and Is(exact). Starts With appears to be an option until you click on it, and then Call Number changes to Title which becomes unavailable to change. Starts With would be the best and most logical limiter for users for a call number search, but it's not available.

    -The Contains limiter does not appear to function correctly. For example, I receive results when searching Advanced Search > Call number > Contains > M1003 .H64, but no results when I search M1003 .H.

    (I submitted ticket 00523629 regarding these requests, and was advised to post them to the Idea Exchange.)

    Currently you can conduct an advanced call number search, but there are a few issues with it:

    -It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.

    -The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of… more

    73 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…)
    6 comments  ·  User Functionality  ·  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