361 results found
-
duplicate field detection
Within the bibliographic record, occasionally there are duplicate fields. We need a way to easily detect them, especially with bibs upon bibs that are merged. We end up with a ton of duplicate 035 fields.
16 votes -
Create Multiple Items in LEAP
In the client we are able to create multiple new item records at the same time and we would like this functionality in LEAP as well.
17 votes -
Display more previous borrowers on item circulation view
On an item record, you can currently only see the information about the current borrower and the most recent previous borrower. This should be increased to at least 3, so that in the case of a question about condition or missing parts, we have more than 1 patron we can ask.
17 votes -
Allow greater customization of slips/receipts
Currently, receipt/slip configuration is hard-coded into Polaris system administration. Libraries are limited in what information they can add to a receipt or slip and do not have control over design elements in sys admin. Innovative does not recommend modifying the related SQL job to make changes there. It would be helpful to have greater flexibility and customization options for libraries, especially for hold and in-transit slips. For example, a library could configure in-transit slip information to match what is required by their library system's delivery service.
47 votes -
Provide easy way to convert item level holds to bib level
We teach staff that, except in very rare cases, they should always be placing bib level holds for customers but sometimes folks make mistakes. It would be great there was a check box option in Leap to convert a customer's item level hold to a bib level hold while retaining their position in the queue. Currently, if a staffer places an item level hold in error, to fix it, they have to place a new bib level hold and then use the checkbox and arrows in the queue to move them from last position (for example, 453) to their former…
24 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.
11 votes -
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…
10 votes -
Ability to view Bib circulations (Statistics) by year complete history, rather than just YTD & Previous Year
Being able to see a more complete circulation statistics for the lifetime of a title gives selection staff a more complete picture of the use of a title, in order to make better decisions about purchasing future titles by an author or in a series.
11 votes -
Allow for more than one 250 field
It is a basic principle of RDA and sometimes we can't display all the info in one field with commas when there are special editions of video games.
14 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.
23 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.
25 votes -
Option to return to find results after record deletion
When a record (item, bib, etc.) is opened from Find results and then marked as deleted, it (and the Find results) are automatically closed. It would great if the record did not close (leaving the Results button available) or the record closed and returned the user to the Find results.
21 votes -
Expired patron transition
We would like Polaris to transition expired patrons to Deleted after a specified time frame. (Such patrons would of course need to have no lost items or checkouts.) We envision this working like Lost Item Transition and the Missing Item Transition. Ideally, we could also set a fine threshold to only delete those expired patrons with less than a certain amount of fines on their cards.
Adding this feature would allow a library to automatically remove expired patrons and allow for a more streamline process for deleting the ones they wanted.
10 votes -
Navigate neighboring results without returning to results list
When I browse in the PAC (specifically, by call number) it provides a list of call numbers. I can choose one, and am brought to it. But, if I want to look at the neighboring items, I have to "Go back to Browse Results" and select the next one from the list. It would be much easier to arrow back/forward between results without returning to the results list.
21 votes -
Make cutting and pasting fields from OCLC seamless
Currently cutting and pasting from OCLC Connexion Client into Polaris is cumbersome. Allow for complete fields and their delimiters to paste into Polaris seamlessly.
14 votes -
Adding a "New" field in LEAP
Because new is both a location and a status, it would be helpful to have an item level field in LEAP that is for "new" items. A simple checkbox would be sufficient, like "holdable" or "display in PAC." This would free up shelf location for any items that are both new and in a specific area, such as Travel, World, Graphic, etc.
9 votes -
Support Custom TOMs / TOM Override
While there are many advantages to way that Polaris calculates TOMs, there are currently some significant limitations for differentiating between formats. 4K BluRays, Playaways/Yotos, and video game systems are all very difficult to distinguish from one another when using only the MARC fixed fields. Additionally, many libraries are expanding their collections with Libraries of Things that are usually coded as "Kit" or "Three Dimensional Object" rather than describing what it actually is. These bib TOMS are also now featured prominently in Vega Discover's rollups.
Over on the Sierra side, the options for bibliographic format can be customized. If a library…
80 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.10 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.
19 votes -
Option to have items automatically move to "missing" status after item is not found on picklist a certain number of times.
Option to automatically update circulation status of an item to "missing" if the item is not found on a picklist after a designated # of searches.
21 votes
- Don't see your idea?