694 results found
-
Retain load-all after making changes in a record set
Provide an option to retain the load-all after making changes in a record set. Currently if you load all, then make a change, it reloads the limited set of records.
24 votes -
Polaris Leap: Popup/Prompt for Patron Blocks
Currently, in the desktop client, when opening a checkout window and entering a patron's barcode, if the selected patron has blocks, a window pops up and prompts the user to continue or cancel the interaction. This is not present in the checkout workflow in Polaris Leap, so it is possible for circulation staff to miss important information if they do not open the "Blocks" button before every interaction. Is it possible for an optional feature to be added to notify circulation staff about patron blocks before a transaction?
24 votes -
Preview for MARC Import
There should be a preview or staging phase when importing new MARC records where you can see what duplicates are detected, and what action will be taken based on the profile selected, and have the option to manually override the actions on each record (e.g. don't replace this specific one - just create a second record instead)
24 votes -
When there is a blocking note on an account, a red square block appears like it does for an expired library card.
When a library card is expired a large red box appears on the screen to say the library card is expired. Can we get that same type of box for an account that has a balance and a Blocking note?
24 votes -
Make SimplyReports reports truly use the library level for reports
When you use SimplyReports (née Simply Reports) and create a report and select a LIBRARY, the report data is actually using the branches at the time the report was created. It is essentially a branch level report with the branches a the time of report creation.
This means that if you save the report, then you add a branch, that branch is NOT included in the report output. This causes confusion and extra work. There should be an option to truly make a "LIBRARY" level report, or part of the process of adding a new branch should go back and…
24 votes -
Printing workslips in Leap for the received PO lines
Receiving from the PO and printing workslips with one command.
Or at least keep the check marks of the selected PO lines to receive and then to print slips to avoid selecting the same PO lines twice.24 votes -
Include an "X"/close button on workform tracker records
Sometimes I have a lot of records open in the workform tracker, and it's a pain to have to go into each to close it. It would be useful to have a button I could quickly click to close them instead.
In cases where a record has been modified it should generate a prompt about saving changes, and show you the record again in this case so it's clear what's being saved.
24 votes -
More granular permissions for deleting items/bibs
In Polaris, a single delete of a bib/item record will result in that record being 'marked for deletion.' It is no longer visible in the PAC, but is still visible in Polaris with a Deleted status. Deleting a record in Deleted status, or what we've termed 'double-delete,' will result in the record being fully purged from the database.
Sometimes, staff will delete a record and go back to it to verify the deletion. They see it's still visible in Polaris (missing the Deleted status) and delete it a second time. This accidental purging results in no longer being able to…
24 votes -
Add Custom Data Fields to Item Records
Patron records have 5 UDFs and 10 Custom Data Fields – item records have none of these. As a result, many libraries end up doing some weird stuff with the Name of Piece and Temporary Shelf Location. This idea would add 10 or so custom item record fields that libraries can choose how they would like to use.
Ideally, fields would be capable of multiple data types including freetext, Boolean, date, or numeric. In a perfect world, it could also support a drop down list like the UDFs! The fields would also be searchable in the find tool, just like…
24 votes -
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…
24 votes -
View titles when comparing bib records
Right now when comparing bib records, the tabs all show the bib control number, which at a glance are simply not useful, especially if you have brought up multiple records. I would love for the display tabs at the top to have an option to display the title.
23 votes -
Add Item Mat Type to Bib scoping in Find Tool (Leap)
In the client a bib search can be filtered by Item Material Type. This would be useful in Leap.
23 votes -
Add items to record set from bib
It would be helpful if Leap had the client functionality allowing staff to add items to a record set from a bib record.
23 votes -
Navigation buttons at the top and bottom of All Items list on LEAP bibliographic records
On the All Items tab of LEAP bib records, it would be helpful to have page turning buttons at both the top and bottom of the list for ease of navigation
23 votes -
Leap - display control numbers in list of current and recent workforms
Right now, the only thing that displays in the list of workforms is the title. When comparing records with the exact same title, this can get confusing and requires too many clicks to make sure you are selecting the correct record. There needs to be more information displayed in addition to the title, and should at minimum have a control number.
23 votes -
Checkin Lost Item as Damaged
If an item has a "lost" status, and is returned damaged we are unable to change the status to "damaged" via the check-in damaged option (must be in/out for damaged check-in to be used). This would be helpful for situations where the patron returns an item that was declared lost (either automatically by being +30 days overdue or manually) and then later found and returned to the library via drop box, to be able to demonstrate the item was returned damaged with no previous poor condition notes on the item.
23 votes -
Apply credit to POLI
Currently it is only possible to apply a credit to an entire invoice, which then distributes that across all funds for all items on the invoice. We rarely actually have a credit that applies to an entire invoice. It will apply to a single title, or even and single item, and should only apply to the fund for that item/title.
It would be much better to be able to apply a credit to a POLI, or even better, a specific POLI segment.23 votes -
Restrict hold pickup areas by material type
Allow each library to specify specific material types(?) to not be allowed to be picked up in certain pickup areas. Example would be a wi-fi hotspot not being allowed to be picked up in a locker.
23 votes -
API to Update Bibliographic Records
I'm specifically looking for a great integration between the cataloging tool BTCat and Polaris.
Libraries use tools like BTCat and Skyriver to search for new bib records and update/edit existing records. After making changes, the records currently have to be exported from the cataloging software, then imported into Polaris. These tools have the ability to "push" records into other ILS systems, skipping the need for a manual export/import of records. Adding this functionality would aid libraries in transitioning away from the Polaris desktop client (as bibliographic editing in Leap is a tedious process, at best).
23 votesWe actually added an endpoint to support this integration in Polaris 7.6 (BibsPost). We've been working with BTCat to consume the endpoint in their application.
I'm going to set this to "Planned" for now because the integration is not live with BTCat yet. But the development piece required for Polaris has been done. Please let BTCat know you are interested!!
-
Allow library to exclude certain material types from Claim Return function
Polaris' claim return function is great for locally-owned items but is problematic with INN-Reach. We are constantly reminding staff NOT to use Claim Return for INN-Reach items because it can break transaction links but they continue to do so. If system admin allowed us to exclude our INN-Reach and WorldCat material types from Claim Return and Claim Missing Part functions, it would reduce errors significantly.
22 votes
- Don't see your idea?