573 results found
-
Allow libraries to reset staff accounts that are locked out
There are a few scenarios where staff don't remember their exact password and get themselves locked out of LEAP: they are adjunct staff who work infrequently, they have just returned from a long vacation, or simply have brain freeze. In these cases, they open a support ticket, and I would like to be able to reset their account so that they can log in immediately, the same way I can now clear an object lock on an item that someone needs to use. Thanks for considering!
5 votes -
Bookmobile address locations for hold pickup
Bookmobiles move around. When customers get the holds notice, the address listed on the notice is usually the bookmobile home address. The customer shows up only to find that the bookmobile isn't home. We have pickup locations for the customer to choose from in the PAC, but they do not have addresses assigned to them. If they did, we would want that address to be used on the holds notice. Can this be a LX starter and/or Polaris enhancement for Bookmobile.
8 votes -
Hide libraries and branches in Polaris System Administration
Sometimes libraries leave a consortium. Sometimes a branch is closed or merged into another branch. And after the Polaris ILS Admin takes care of clearing out all the bib, item, and patron data... the branches and libraries remain in System Administration.
Just sitting there and doing nothing.
I know it's a huge pain to remove a branch or library from Polaris and I know there's likely an extra cost to it because it's such an involved process.
So add the ability to hide them instead.
That way, when a library leaves the system, you're not wading through the settings and…
28 votes -
Hoopla integration with Polaris
The current process of loading and removing Hoopla records in the staff client is tedious and time-consuming at best. We stopped adding Hoopla records to Polaris because we don't have the staff capacity to deal with the monthly 'remove' lists. An API integration similar to CloudLibrary would be a huge time-saver. CloudLibrary automatically imports records and then sets them to 'withdrawn' when the title is no longer available. The Hoopla database is enormous, so the ability to add some parameters of what to pull would also be helpful.
15 votes -
Edit Half-Deleted Item Records
When doing clean up work we run into instances where we are not able to delete something like shelf locations because it is assigned to records that are in a deleted state. While we know we can just delete the records 1 more time, some of these records are tied to other things we track and would prefer to keep them in the system.
Currently we bulk change them at the server level but would like a way to be able to do this within the ILS.
12 votes -
bulk change due dates
Allow libraries to bulk change due dates of items to account for unexpected closures. Would be ideal to be able to do this from a records set. Or create a SQL job and put it in GitHub or some other accessible location for libraries.
14 votes -
Include perioidical issue information in overdue notices
We had a patron complaint that the email notices do not include magazine issue information, only the main title. The notices also do not include item barcodes, so there isn't any data to match against a specific issue. Could information from the Issue field in the item record be displayed in overdue notices?
14 votes -
Standard Address Number (SAN) Inconsistency
There is no hyphen in Branch SAN but Supplier SAN has a hyphen. This causes confusion for both the library and suppliers while setting up EDI for the very first time for new Polaris customers. It would be better if there was a consistency.
5 votes -
Bulk Delete Item Records in Leap
Now that we have the capability to do ad hoc bulk changes to item records from the bibliographic record in Polaris 7.6, we also need the ability to delete item records in bulk. The workflow in the Client includes the ability to select multiple item records ad-hoc, right click on them, and press delete (or undelete). Delete and undelete buttons should be added next to the Bulk Change button on the Local Items and All Items tabs of the bibliographic workform in Leap. An alternate option could be to add a delete option to the bulk change.
71 votes -
More information on ILL
On the information page for an ILL, there should be the ability to see what staff have interacted with the ILL or if a patron has made a change. We had an ILL get cancelled before it arrived to our library, but we can't tell if it was a staff initiation or a patron one. In the record for a regular item, I can see who has done what with a hold. This would be useful for follow up.
4 votes -
Create a Back End Updating Feature
A few days ago, we discovered an issue in Polaris. It wasn't a huge problem, but it was a bit disturbing for our cataloguers in that they encountered an error when trying to open up a record set. I checked with others in the IUG and, sure enough, there were other libraries who'd seen the same problem.
So I put in a ticket through the Supportal and received a prompt response. It was a known issue (though it wasn't on the list of Known Issues) and there was a patch available for it. I was asked if I'd like the…
16 votes -
Add Items to a Record set from Patron's Hold List
Cataloging staff use staff cards to request items in for call number changes or various projects. It would be helpful for them to be able to add those items into a Record Set for bulk changes directly from the patron record Hold list, in lieu of individually from the item records.
12 votes -
Permission the volume field on item records
The volume field might seem straightforward, but when it's not standardized—or when anyone can input anything—it quickly becomes a source of frustration, especially with holds and sorting. Imagine a patron placing a hold on “Volume 2,” but one record says “v.2,” another says “Vol 2,” and another just “2”… chaos ensues.
Making that field permission-based could go a long way in preserving data consistency and reducing hold errors. It puts a bit more control in the hands of cataloging staff or system administrators
5 votes -
Bibliographic consistency check when editing bibs
In cleaning up bibliographic data after years of laissez faire cataloguing practice, we have run into a consistent stumbling block that requires us to backtrack. Certain bytes, especially in the 007 and 008 fields appear to require consistency across them to properly read at an item level (we became aware of this when getting red toasts scanning items for a weeding record set, that appeared initially to be in the inclusion criteria).
By way of example: If you input in 007 an 01 byte of 'd - Videodisc', than the 04 byte would have to be 'g' 'h' 's' or…
7 votes -
Change status of staff holds without check-in
In my staff duties, I am often putting a hold on an item that will be moved to in-repair for re-cataloging. Currently, I have to place a hold with my staff card and, when the item is held, I must check it in before I can change the status to in-repair. There are even more steps when the item is assigned to a different branch and wants to automatically transfer on check-in. Then I have to change the assigned branch as well.
When the item is held on a Staff account, it would be very helpful to be able to…4 votes -
Force Leap Logout at Browser Close
Leap should force logout when browser/browser tab is closed. Forcing a logout at browser/browser tab close would ensure that any open editable records are closed out as well.
51 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 -
Bulk edit serial status
Currently, when we need to edit a serial's status, it has to be done one at a time. We have multiple branches that all are scheduled to receive the same issue of a magazine. When the expected issue isn't published, due to a double or special issue instead, we have to edit each serial's status individually to "Never published". Adding serial specific fields where appropriate to bulk item edit would help this.
5 votes -
Replicate LEAP column setting customizations in the client
Cataloging staff using the client have to resize the columns of the find tool results every time they search bibs and items. They also would like to be able to add and remove columns from their default searches. In LEAP, they can add and remove columns and LEAP remembers when they resize a column. This functionality in the client would save them steps.
5 votes -
Add support for automated clearing of the [PolarisTransactions].[Polaris].[NotificationLog]
The PolarisTransactions].[Polaris].[NotificationLog] has Personally Identifiable Information (PII) in it. That table is never cleared, even if you select to clear the PatronID from the PolarisTransactions.
Ideally, we'd like an option for this data to just be cleared out after a certain period of time. If that is not possible, then NULLing the patron id when that option is enabled for the PolarisTransactions should work here too.
5 votes
- Don't see your idea?