603 results found
-
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
15 votes -
Automatically associate accounts when creating a new patron account with the Copy feature
I think it would be helpful to automatically create an association between accounts when creating a new account by copying an existing one, e.g., using a parent's account to create a child's account. The Block and Allow options should still be checked manually, though.
The association could be removed after account creation, if necessary.15 votes -
Report for staff user or workstation transactions
We could use a report based on staff user and/or workstation listing all transactions made for a given date range. Most importantly for us, cataloging information which could provide date and time of bib records being created and/or modified as well as circulation information for staff who work the circ desk.
15 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 -
Show Due Date for ILLs in Request Manager
Our ILL clerk would like to be able to see the due date for ILLs from the request manager, so she can make sure that the dates have been added correctly to these items. She currently has to go into each item individually to make sure they were correct.
15 votes -
Ability to Export Individual Owned Record Sets
I had a coworker ask why she couldn't export her record set into excel to allow for more sortability. I was surprised she couldn't and began looking at documentation and noticed that there is that ability, but you have to change the owner of the record set to the branch or system level, which feels like an unnecessary step. I should be able to export a record set I am working on to Excel with my regular ownership without having the (slim) possibility of a coworker accidentally accessing and messing up anything.
15 votes -
"Today" on Date Picker
When using the date picker, we'd love an option to select "Today" and have it set the date automatically for us. When updating really old cards, it can be a pain to have to select a date with the picker when we have to change every field. Typing is limited in its ability to be a workaround, because it requires specific formatting in order to work.
15 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 -
Auto suggest volumes while adding items to a bib record
When creating a new item record on a bib, it would be wonderful if while typing in the volume field, Leap automatically suggested volumes from other items attached to that particular bib. This would help ensure standardization of how the volume is entered on each item record (eg. V.1 vs V. 1 vs. V.01) while also allowing the libraries to add a new volume number for volumes 2, 3, etc. since it would suggest while typing rather than changing the volume field to be a drop down menu of pre-defined options.
15 votes -
Ability to remove spaces from call numbers in Leap
When the callnumber column is pulled from itemrecorddetails via SQL (as opposed to SimplyReports) it includes trailing and leading spaces. It's easy to fix these unwanted spaces in the client, but they don't show up at all in Leap, so can't be fixed. If Leap is to replace the client eventually, it would be great to able to fully edit these fields in Leap (we are hosted, so can't easily modify the data via SQL).
15 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.
15 votes -
Reverting to what the bibliographic record (or any authority record for that matter) was when it was last saved
When you want to get rid of a bunch of edits, but only the ones made since the last save, it saves time to have just one button to click on. For example, when you want to validate juvenile headings, you need to take out |v Fiction for each heading. If they are all good, you want it back in each heading.
15 votes -
Ability to add QR codes to printed or emailed receipts
Ability to add QR codes to printed or emailed receipts
15 votes -
Vernacular script display for non-Roman language materials
MARC records for non-Roman language materials come to us from OCLC with the vernacular script in the 880 fields. Since that doesn't display in Polaris/Leap like we want it to, we have been using MARC edit to swap the 880 fields with the transliterations contained in the regular MARC fields. We are hoping there can be a better way, and Polaris can simply let us choose to use the 880 fields for display when they are present OR display the 880 information alongside the transliteration.
There are several places where the transliteration appears when we'd like the vernacular script to…
15 votes -
bulk add "stat code"
Be able to bulk add stat codes. Currently we can only add at the branch level manually because the library and system level tables are too large. This requires a manual change or contracting Polaris every time we want to add stat codes for all locations.
15 votes -
Ad hoc Patron Bulk Changes From Find Tool
Similar to the change in 7.6 for Item Changes, it would be beneficial to be able to make the ad hoc changes to patron records. Our libraries could easily change their Juvenile patrons to Adult patrons using the Find tool.
15 votes -
Polaris transactions will "run out" of space due to being an "int" data type
The Polaris Transactions database TransactionID is an int data type. This 2,147,483,647 means the biggest number supported by the database. In our busy system, we're about halfway through the available TransactionIDs as we're about to reach 1 billion. This field should be moved up to a bigint data type. Otherwise inserting new data will fail.
15 votes -
Search LEAP by username
LFPL would like the ability to search for patrons by their username in LEAP without having to use the SQL search
15 votes -
LEAP: Allow sending items to an item record set from a patron record "Out / Renew" screen
LEAP: Allow sending items to an item record set from a patron record "Out / Renew" screen
15 votes -
Change default for Damaged Item Check-in
Currently the default option is to charge the patron when doing a damaged item check-in (see screenshot). We would like the default to either be changed to NOT charge the patron, or we would like to be given the option to choose the default ourselves so we can change it to what we want just for our consortium.
15 votes
- Don't see your idea?