44 results found

1. Automate lost card number request via email option in PAC

   Automate lost barcode number requests. The simple way to achieve this is to offer this option below "Forgot your password" on the PAC login screen. The user clicks this and is asked to enter in the email address connected to the account in addition to first and last name. The patron associated with that name and email address would receive an email with the barcode. If the patron does not have an email on the account, or the wrong email address is entered, the user receives an error message.

   Idea Value
   This would save staff time in person and on the phone. Patrons would have an easy way to regain control over their account, as well as access Libby and Hoopla on holidays and after hours.

   Automate lost barcode number requests. The simple way to achieve this is to offer this option below "Forgot your password" on the PAC login screen. The user clicks this and is asked to enter in the email address connected to the account in addition to first and last name. The patron associated with that name and email address would receive an email with the barcode. If the patron does not have an email on the account, or the wrong email address is entered, the user receives an error message.

   Idea Value
   This would save staff time in person and on… more

   •  

   12 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  ·  Customer Relationship & Account Management  ·  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

   Submit Rating

2. Remove Branch Requirement from Patron Bulk Change

   Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.

   This was previously submitted in the old enhancement process:

   "Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can use all patron codes"

   Idea Value
   It is common at multi-branch libraries to update sets of patron records from more than one branch. The current requirement makes this a lengthy process in which multiple record sets have to be created based on patron branch.

   Most of the time, the same patron codes and blocks are used at all branches of a library. When this is not the case, the update could just fail for that record and show as an error in the report. This is already the process when the staff member does not have permission to change patrons from a particular branch.

   This would save staff time and allow for timely updates to patron records.

   Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.

   This was previously submitted in the old enhancement process:

   "Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can… more

   19 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  ·  Customer Relationship & Account Management  ·  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

   Submit Rating

3. LEAP - Picklist processing display - customize fields (exact fields TBD)

   Currently the picklist processing report is as-is with no options to modify.

   We've found it would be helpful for our library to have the last activity date to display when printing the picklist as items may have been returned within the last few days and on their way to being re-shelved or possibly on shelf for years & actually missing. Thinking others may have additional fields that would be of use to them as well.

   It would be a helpful enhancement for staff to have the ability to choose additional fields to customize & re-arrange the columns on the picklist for their own library's needs.

   Idea Value
   More efficient use of time by not searching for the same titles multiple days & improve customer service by getting the item out quicker to our patrons.

   Currently the picklist processing report is as-is with no options to modify.

   We've found it would be helpful for our library to have the last activity date to display when printing the picklist as items may have been returned within the last few days and on their way to being re-shelved or possibly on shelf for years & actually missing. Thinking others may have additional fields that would be of use to them as well.

   It would be a helpful enhancement for staff to have the ability to choose additional fields to customize & re-arrange the columns on the picklist… more

   47 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  ·  2 comments  ·  Customer Relationship & Account Management  ·  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

   Submit Rating

4. Improve Student/Patron Import

   The Problem

   At best, the method and workflow used to bulk import patrons into Polaris (often referred to as student import) is archaic. The Polaris documentation for this process, Importing Student Records as Patron Records, is 19 pages long and seven of those pages are definitions and descriptions for the format of a pipe delimited file. This file contains 65 separate columns, all of which must be included in the file even if they contain no information. The documentation defines at least three columns that you should not populate… so why are they there? You can obtain a sample Excel file so long as you have access to the Supportal.

   After you've populated this spreadsheet you'll need to convert it to PSV and add another and completely separate line above the patron data that specifies the number 1 (Why?), the time, the date, a branch ID, a user ID, a workstation ID, and the version and build of your Polaris system. (Incidentally, the documentation doesn't specify that last bit, you only find out about it in another Supportal post. The documentation says you should end the top line with the number 20. Again, why?) After you do all of that, rename the file in a very special way and change the extension to TRN before putting it in a very special location on your workstation or server. Finally, initiate the import via… the BookMobile?

   Meanwhile, with Koha, you can obtain a starter CSV from within the ILS itself, and import the patrons through a patron import workform. Their patron import documentation comes out to just over two pages and 554 words.

   I apologize for the rant, but I want to stress the length, the tedium, the potential for error, and the brokenness of the Polaris process. As it stands right now, it's almost impossible for anyone other than an ILS administrator to handle patron imports.

   Ideas to Fix the Problem

   Basic changes that would go a long way:

   • Change the import file to CSV.
   • Simplify the CSV to remove columns that shouldn't be used.
   • Add patron import to Leap.
   • Offer the sample CSV within Leap.
   • Create an import process that asks for the information in the leader of a TRN file, but defaults to the current time, date, branch ID, workstation ID, and user ID.
   • This import workform should be separate from the BookMobile functionality.

   Idea Value
   Every year, right around the time I'm submitting this idea, Polaris libraries across the United States are importing large amounts of students into their systems. The process for doing so is meticulous, yet it's also error prone and convoluted. That's not the kind of system you need when you're adding hundreds or thousands of new patrons into your system. The PSV format of the TRN file practically guarantees that you're going to have to make at least one or two file conversions when you obtain data from a separate entity, such as a school. Switching to CSV helps ensure a closer interoperability between database types and product vendors so the potential for error is greatly reduced.

   The Problem

   At best, the method and workflow used to bulk import patrons into Polaris (often referred to as student import) is archaic. The Polaris documentation for this process, Importing Student Records as Patron Records, is 19 pages long and seven of those pages are definitions and descriptions for the format of a pipe delimited file. This file contains 65 separate columns, all of which must be included in the file even if they contain no information. The documentation defines at least three columns that you should not populate… so why are they there? You can obtain a sample Excel… more

   53 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  ·  Customer Relationship & Account Management  ·  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

   Submit Rating