676 results found
-
Ability to Edit/Modify Publication Patterns
It would be great to be able to edit or modify publication patterns as needed.
Currently, we are only able to modify publication patterns IF no issues have been received. After that, the only way to change a publication pattern is to close the current one and open a new one.
It would save staff time and effort if they could update a current pattern with necessary changes rather than being required to create a new one each time.
57 votes -
Find tool - additional columns on a Bibbliographic Search for Series name and volume
Our library team have requested to be able to see the series name and volume number in the returned bib records when searching with the find tool. It will mean they no longer need to open each result to see this information
similar proposal as:
https://ideas.iii.com/forums/951742-ils-polaris/suggestions/48194096-add-edition-statement-to-results-list-in-find-tool34 votes -
Leap Offline Improvements
Currently there is more functionality in the client than in Leap for offline services. I would like Leap to also be able to create customer accounts and process check-ins like the client. But it would also be nice for the check in function, once transactions have been uploaded, to have the option for all items to go to a status of "IN" and be assigned to the branch they were checked in at.
15 votes -
Block e-resources but not renewals for non-residents
We would like to have an option where non-resident patron types have a blocking condition for e-resources, but it only limits e-resources. We would like for them to be able to still manage their online accounts and renew physical items, so the patron-initiated blocking condition does not work. Right now, that can only be done in CloudLibrary through SIP, not API.
1 voteI think this idea needs some clarification. Are you using a non-resident patron code? If so, we do return the PatronCodeID in our PatronValidate API. I wonder if this is a situation where Cloudlibrary has infrastructure in place to support checking the patron code via SIP, but not yet via the Polaris API.
-
Additional UI Customization Options
Across our consortium, we have some library staff who exclusively use Leap, some who exclusively use the Remote Client, and some who use both depending on the task.
Currently, there is only one system-level setting responsible for the Visual Alert Configuration (top banner color) in Leap & the Remote Client. Unfortunately, this doesn’t work well given that Leap has a light font color and the Client has a dark font color across the top, so to achieve an ideal level of contrast for both versions simultaneously is impossible.
To improve accessibility for all users, regardless of the version of Polaris…
13 votes -
Bulk delete ILL-requests in Leap
When searching by ILL-Request in Leap for a specific date range, I would like to be able to Shift + Click to highlight and add to a record set to perform a bulk delete.
5 votes -
Add granularity to One-Click Request feature
We recently had a location close for a few weeks for a construction project. During that time, we turned it off as a holds pickup option in the PAC. However, patrons who were logged into their accounts and had that location as their default holds pickup location could still place holds for pickup at that location using One-Click. The only way to completely stop patrons placing holds for pickup at our closed location was to disable One-Click completely. This annoyed patrons at our locations that remained open, who saw a popular feature of the PAC disappear without warning for seemingly…
14 votes -
Granular bib editing permissions
Currently staff can either edit/modify bib records or they can't. Greater granularity in what edits can be allowed would help distribute the work of maintaining bib records.
For example, if acquisitions staff could be allowed to add additional ISBNs or UPCs to existing bibs, it would free up cataloguing staff from this simple task without opening bib editing completely to a large number of people.
In a larger library system, especially a consortium with a shared catalogue, this could be a big time-saver to both acq and cat staff.
29 votes -
The ability to recover deleted Item Templates
The ability to recover deleted Item Templates.
6 votes -
patron barcode change workflow to automatically populate "former barcode" field
It would be great to have a way in Leap to change the patron barcode and have it auto populate the "Former Barcode" field in a single step. Perhaps a button could be added underneath "Reset Password" for "Replace Barcode" that simply prompts the staff member to scan a new barcode number. Leap would then move the existing barcode to the "Former Barcode" field, and then populate the Barcode field will the newly provided number. Help us save a few steps! Thanks for the consideration.
33 votes -
Indication of a note for a specific issue on the Serial Check in card
When looking at the Serial Check in card, it would be helpful to have some sort of indication that a note has been added to a specific issue.
5 votes -
Block patrons from placing holds in VEGA, Mobile App, PAC and Leap if patron is blocked
Having patrons blocked from placing holds if there account is blocked is greatly needed, as patrons can currently place holds through Leap, Vega, Mobile App even if they are blocked for having too many fines.
69 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 -
When refreshing the Leap Offline installation, offer the Offline mode link again
When you refresh the Offline installation in Leap it would be good to present the URL for Offline mode bookmarking again. The suggestion would be to show it in the pop-up toast message once the offline data is refreshed.
There currently is not an easy way for staff to get to the Offline link again without deleting the offline files and setting it up again.
9 votes -
Include All Patron Duplicate Detection Settings in the API
Currently the API only performs basic duplicate detection (name, birthdate, barcode, username, and optionally the name on ID) when a patron record is created using the PatronRegistrationCreate call. It does not apply other optional settings - email, phone 1, or the UDFs - these only get applied directly in Polaris or the PAC. This idea is for including these optional settings in the API logic.
13 votes -
Ability to check in a routed serial with no barcode to be deleted in Leap
When we are done using a routed periodical we have no way of checking in the issue for deletion. We don't assign a barcode to these issues so it will not allow a check in. We need ability to either delete a periodical in a Routed status or a quick way to un-route to then allow us to delete.
Right now staff are forced into the item record and assign a barcode like "1", save record. Check in item. Then they can delete.
6 votes -
Upload images for item records
I would like to upload images for an item record. We are attempting to build our Library of Things and these items don't have photos tied to the item record.
39 votes -
Fulfilling holds in a particular order (Series)
I would like to be able to have a particular hold become active after a different hold has become filled. This is particularly useful for customers who are engaged in a series and do not want them all at once, but do want them in order and want to place all the holds at the same time.
30 votes -
Allow library to alter default status for "Mark Unavailable" in Missing Part Checkin
This currently defaults to "Display," and displays with that status in PAC. Display is a non-circing status that is actually used for items in our special collections, so we can't rename it to something like "In Repair."
If system admin gave an option to set a default status when "Mark Unavailable" is selected from Missing Part Check In, it would streamline workflows as we wouldn't have to go back and change the status in the item record.
6 votes -
Improve Hold Duplicate Detection
Hold duplicate detection has a flaw that allows duplicate hold requests to be placed on the same titles. The detection seems to apply on title and author information stored with the hold request (apparently on the SysHoldRequestSearchTerms table), which stores point-in-time title/author details that may change if the bib record is overlayed or edited.
This idea is for improving the duplicate detection to fix this gap, but also any similar gaps I may be missing where title-related data is stored separately when the hold is created, and referenced by the dupe detection (I'm not seeing separate tables storing elements like…
10 votes
- Don't see your idea?