24 results found

1. Search Results Page number options

   Patrons don't have much options when paging through many pages of search results and have requested the ability to navigate through page numbers. As an example, if there are 100 page results, patrons can only go to next page, last page, first page or previous page. They want to be able to manually enter a page number (for example page 72) to go to that page of results. Switching to total results per page default from 10 to 100 doesn't help with a large number of results.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  0 comments  ·  Discovery & OPAC  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have 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. Clarity in the "available now" facet in PowerPAC for consortium libraries

   When conducting a PowerPAC search using the "limit by" feature to select one's home library and combining that with the "available now" facet, the implication is that only the items at one's home library will show up. That is not the case, as available items at all consortium libraries display in the results. Although it is possible to achieve the desired results by selecting the local library under the "assigned branch" facet, this is not very intuitive for library patrons.

   We would like to see the "available now" facet in PowerPAC split into two options for libraries in consortiums. One option would allow selection of available items at one's home library, and the other, for available items at any library in the consortium.

   Idea Value
   Splitting this facet in two would be more intuitive to PowerPAC users. The new facets could be "available now at my library" and "available now at any library". Our experience is that users do not realize that they need to take the extra step of using the "assigned branch" facet for this type of search. By eliminating that extra step, patrons can more easily get to the results they expect.

   When conducting a PowerPAC search using the "limit by" feature to select one's home library and combining that with the "available now" facet, the implication is that only the items at one's home library will show up. That is not the case, as available items at all consortium libraries display in the results. Although it is possible to achieve the desired results by selecting the local library under the "assigned branch" facet, this is not very intuitive for library patrons.

   We would like to see the "available now" facet in PowerPAC split into two options for libraries in consortiums. One… more

   23 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  1 comment  ·  Discovery & OPAC  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have 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. Web Admin - PAPI Key Management Permissions

   With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).

   We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in the future, and moving admin activities from the client to the web.

   There should be more granular, PAPI Key Management-specific permissions, so that only appropriate users can access or change these, not anyone with admin access.

   Idea Value
   For customers who use API keys, and also give some staff access to system administration functions, this is likely to be a security gap, and may prevent them from moving all staff functions off the client.

   With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).

   We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in… more

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  3 comments  ·  Discovery & OPAC  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have 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. OPAC: Change password request should notify patron and update modification date in patron registration.

   Currently, when a patron changes their password via the OPAC (change logon > change password), no notification is made to the customer nor is the modification date in the patron registration record updated.

   I would like to see an email/SMS notification be issued to the customer when a password is changed via this method as well as have the modification date updated.

   Idea Value
   These updates would provide better security for the library customer by communicating a system change that they may or may not have made themselves.

   These updates would also make it easier for library staff to investigate issues where a library customer is unsure how their password was changed (they claim they have not changed the library password since last used).

   Currently, when a patron changes their password via the OPAC (change logon > change password), no notification is made to the customer nor is the modification date in the patron registration record updated.

   I would like to see an email/SMS notification be issued to the customer when a password is changed via this method as well as have the modification date updated.

   Idea Value
   These updates would provide better security for the library customer by communicating a system change that they may or may not have made themselves.

   These updates would also make it easier for library staff to investigate… more

   21 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  0 comments  ·  Discovery & OPAC  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have 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