67 results found
-
Allow favicon to be set for leap as a staff visual cue
You can set the title bar color and the login message for Leap. However, it would also be nice to have the option to set the favicon so when you have a test, development, and production server open, you could use a favicon to more quickly distinguish between them in your open tabs.
3 votes -
Have PolarisAdmin follow colors and client alert boxes to distinguish system
When changing settings, it is critical to make sure you're changing them in the right place.
The /PolarisAdmin should also pick up the color coding and client alerts. Currently, the /PolarisAdmin does NOT pickup the client color changes or wording, which means you need to do extra work to make sure you are changing the settings in the proper system.
2 votes -
When logging into Leap make the focus on the Continue button
When you are logging into Leap on a machine where you've already logged in, a cookie is set that pre-fills the Branch and workstation. However, you canNOT simply hit enter to continue through this screen because the focus is on the workstation drop down.
This is a request to make it focus on the Continue button when you've already logged in on this browser to make the login process more seamless.
4 votes -
Give staff ID of duplicate user when staff account username or external ID matches one in the system
When you are adding an account or changing information on an account and the system detects a duplicate, it won't let you proceed. However, it won't give you any information on the conflict account.
It would be super helpful to have the conflicting ID shown in the popup message to make tracking down the other account easier.
Especially if the dup happens to be because of something weird like a space or non-printable character.
This seems to happen more as locations move to SSO and fill in their external ID field.
4 votes -
Clear ExternalID on Deletion + Add Clearer Conflict Error Message
We've begun leveraging the "ExternalID" field in Polaris to integrate staff authentication with Google using our Google Workspace email addresses. During this process, we've encountered matching errors when updating existing Polaris accounts that share email addresses with previously deleted user accounts.
It would be extremely helpful if, when a Polaris staff account is deleted, the associated ExternalID is automatically cleared to prevent these conflicts. Additionally, when an error does occur due to a duplicate ExternalID, a clearer error dialog that identifies the conflicting PolarisUserID would greatly assist in resolving the issue quickly.
1 vote -
Integration with Student Integration Systems, like Skyward and TeacherEase
It would be helpful if Polaris could integrate with Skyward and TeacherEase Student Integration Systems. We currently provide service for a number of K-12 schools and it would be helpful if fines/fees could be transferred to the primary system a school uses.
1 vote -
Include Call Number Field in SIP Item Information Response (18) Message
No that we have migrated from Sierra to Polaris, the call number field is not included in the SIP response when using an inventory wand. At this point we only see the barcode and title of an item, which makes it more difficult to find identified items.
6 votes -
Patron Import Process (LEAP) leveraging patron templates
The new patron import process will be a major improvement for handling student data, but it still requires significant data formatting before uploading through LEAP. It would be incredibly helpful if libraries could create their own templates to define how data is mapped to specific CSV columns, including logic for assigning patron codes or populating fields like UDFs. This kind of flexibility would greatly reduce the staff time needed to prepare files for import.
2 votes -
Patron Import Process (LEAP) adding Polaris Username field
Adding the ability to add / update the Polaris username field as an alternative barcode for students/patrons would be hugely beneficial in the import process. This would allow us to have a student ID as a barcode and a former library barcode for patrons to use at the expresscheck.
11 votes -
Back to Search from Send to Record Set
When you create a search to then send to record set we would like option to go Back to Search. Sometimes we only grab part of the initial results into a record set and we would like to go back to the larger list to grab additional items to add into a completely different record set.
Some lists are too long or we want them split up for multiple staff to manage and having these results in different record sets helps with that.
21 votes -
Integrate cloudLibrary with both Polaris and BiblioCommons
We recently began integrating Polaris with cloudLibrary in an effort to keep our collection more up-to-date and have patrons' Polaris accounts reflect their cloudLibrary borrowing. Unfortunately, our results have been inconsistent because while the Polaris/cloudLibrary connection works, there is not a fluid integration between Polaris, cloudLibrary, and BiblioCommons, where patrons are also able to check out cloudLibrary titles. We would like to see full integration between all three vendors so that transactions on any platform are properly communicated to the others.
2 votes -
More granular permissions for patron registration workform
We would like to be able to limit who can change the Expiration Date and Address Check Date in the patron registration workform. Off the two, Address Check Date is most important as this is what we use to make sure patrons are updating their information regularly.
These are configured in SA and are set system wide yet staff continue to change them.
If I remove the 'Patron registration: Modify permission' for member library staff, they won't be able to change other fields.
4 votes -
PII Management Options
Although there are current options for purging patron IDs from circ transactions, and deleting account transactions, there are some gaps with removing PII (personally identifiable information) we'd like to see addressed.
We'd like the option to purge patron IDs from non-circ transactions (incl. patron account history and record history). We'd also like the option to manage patron details on any other tables where history may be maintained after a patron record is deleted (e.g. Notification History, DeletedPatrons, DeletedPatronAccounts, kwmssg, and offline and InnReach process tables). It would also be ideal to have a plan for removing any CNV tables (from…
15 votes -
Return ItemRecordID in responses to BibHoldingsGet
A recent change to PAPI allows for the retrieval of, and adding to, different types of records sets, including Patrons, Bibs, and Items. Adding to Patron and Bib records sets is straight forward because there are existing endpoints within PAPI that return BibRecordID and PatronRecordID numbers. This isn't the case with Item record sets because there a currently no endpoints that provide an item's RecordID. This enhancement would add the ItemRecordID to each row in the BibHoldingsGet response.
7 votes -
Expose web-based System Administration APIs
For larger library systems that need to continually create new staff members, being able to access the APIs would be a big time saver. That would allow, among other things, to automate that task.
3 votes -
A way to customize pop up notices
Various popups appear in Polaris via the client or Leap. Some are pretty clear in what the reminder or error message is about and some popups are not.
I am requesting a way to customize the text and title (Leap only has this visible) to make it more clear for our staff to understand either the popup reminder or the popup error with a little more explanation.
Example for Popup Reminder: Via the client we have a popup reminder about "reminder notices option is email. Do you want to continue?". This occurs when we leave the email field blank per…
17 votes -
Update Bulk Waive schedule in LEAP - add reoccurring
Provide an option to schedule bulk fee waive in records on a reoccurring basis, such as daily, monthly, or other specified intervals. At the moment you can only select one date and run it once.
10 votes -
Add Postal Code table to PAPI
It would be nice for third party vendors and developers to have access to the Postal Code table via PAPI. Something similar to the OrganizationsGet method.
6 votes -
Include Active Directory in web-based System Administration
The current method for changing a Polaris Staff Member's password is clunky and not ideal if part of a large library system. Additionally, all SA management is moving towards the web-based interface. It makes sense to incorporate staff password management into the SA web-based interface.
7 votes -
Ability for PAPI to write to patron Custom Data Fields
It would be helpful if the PatronRegistrationCreate endpoint was able to write to the Patron Custom Data Fields.
6 votes
- Don't see your idea?