239 results found
-
Redirecting Duplicate Copies at Check-In
For libraries using floating collections, the system should support automated redirection of duplicate copies at the point of check-in to other branches that do not currently hold a copy of the title.
The system should surface eligible destination branches automatically, eliminating the need for manual title-level analysis by staff.
In multi-branch library systems, the workflow should allow configurable prioritization rules to determine the destination branch when redistributing items.
Prioritization logic could be applied in the following order:
1) No copy of the title is currently available/on the shelf at the receiving branch
2) Title (or item if not possible) has…4 votes -
Retain Out Location When Renewal Stat group is not zero
Currently, in order to maintain the out loc field in an item record while it is checked out for libraries with auto-renewal, the actual renewal location statistic group number must be zero. This is frustrating as the zero stat group number does not display in reports and we need all renewals to appear in reports. There needs to be a way to retain the out loc in an item record when the renewal stat group number is not zero.
8 votes -
Make pop-up windows remember size and location
When creating a new bib record and using the insert drop-down box, the windows always open in the same place and the same size. If I change the location or size of the window, I have to do it EVERY TIME. This is very annoying. Let me set those parameters and make them permanent for my login.
15 votes -
Include Individual Item Costs in Overdue Notices
Make it an option to also include the item cost in the overdue notice as well (incentive to return!).
In our date due slips (JasperSoft) we include the cost of each item and a total cost to show what the patron saved by using the library vs. buying.
61 votesWe are planning to add the item cost to overdue notice data so it can be included in overdue notices sent through LX Starter as of Sierra 6.7.
Additional changes will be needed in LX Starter before the new data can be included on emails for overdue items.
-
Expand invoice record fields that can be exported from Create Lists
Create Lists allows staff to create review files of invoices, but a number of useful fields from the invoice cannot be exported from the system. Notably the subtotalamt, shippingamt and totaltaxamt fields, which can all be accessed via both SQL and the RestAPI, are missing from the export options.
We would like to see these added so that fuller invoice data could be exported into something like Excel for further accounts reporting and tracking.
14 votes -
Add timestamp to "Suspended" field in user account
Problem:
Our practice is to suspend user accounts when a staff member leaves, rather than delete it, so that we can copy the necessary permissions when a replacement is hired. We then try to delete the accounts after 6 months, but there is currently no method within the Admin App or SQL that tells you when a login was suspended, so we have to track that manually.
Value: adding a timestamp to this field would enable us to more seamlessly manage user accounts for our large consortia and ensure that unnecessary logins are periodically purged.
9 votes -
Data Exchange > Send PRINT FILE using FTS - Include Login Column
I am often having to clean up/delete files that have been saved/"printed" via FTS File Exchange to Data Exchange (send print files out). I sort by date, clear old ones, but some I am hesitant, may still be needed. It would help immensely if the system identified the login associated with this printed file. Then I'd know who to ask/who owns this file (and who isn't deleting their old files). The login column is used elsewhere in the system (Create Lists, etc.), so would ensure consistency.
3 votes -
More universal accessibility features
Improving universal accessibility features for users/employees with diverse accessibility needs.
For example, for employees with visual impairments :
- High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.
Even just the high contrast would help a lot. Additionally, it would be helpful if users…
26 votes -
Make Vendor Payment Info More Readily Accessible
The vendor payment address should be accessible at invoice payment function. Currently, the invoicing function needs to be closed & address information accessed at order record, vendor, etc.
2 votes -
Spending Limit Pop-Up
I know its shocking when the subject of pop-ups in Sierra comes up that anyone would want "MORE!," but our Acquisitions staff would like to see a warning of fund spending over limit at invoicing in addition to ordering.
Their rationale is that shipping & Mylar costs usually cannot be pre-determined. Once posting happens, the fund goes negative. Since there is no going back, like when you're about to go down the chute at the end of a log flume ride, there should be a warning.
2 votes -
Make Selecting 'All' Genuinely Purposeful
From time to time we'll see support tickets where, because of some glitch in the discovery layer, a patron has managed to place upwards of 60 bib level holds on a title.
The holds need to be cancelled in Sierra, so you select 'All.' However, doing so, you still have to address each item individually with a series of additional pop-ups. Over & over again.
This is just one example where I'd like to see selecting 'All' allow for making a single, batch change on the selected records.
2 votes -
Improve patron address parser to better map data to the patron_record_address table
Sierra has a mechanism for parsing the free text entered into patron address fields in the client into separate fields for elements such as city/state/postal code that exist in the patronrecordaddress table. Those distinct fields may then be searched in create lists or utilized in SQL queries. However, the algorithm used to parse out those data points is extremely rigid in terms of the data it expects to see and is quite prone to mapping data incorrectly if an address entered into a patron record does not conform to those guidelines.
For one common example in our system…
28 votes -
Add "mark damaged items" workflow to checkin
Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.
All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.
Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like…
24 votes -
macros
Add additional macro modifiers in Sierra.
The 6.3 update removed the Control + F1 modifier macro. Can we consider adding more modifiers such as left/right control, left/right alt, and left/right shift keys?
Thank you!
3 votes -
Customize layout & Field Visibility in patron View/Edit Record
In the Patron View/Edit Record window the group of fields at the top cannot be arranged in any way but the default. It would be nice to be able to arrange these fields in a way that meets the needs and use of our staff. For example, I would like to be able to put all the editable fields in the first 1-2 columns, such as exp date, language, notice preference, patron type. Then all the uneditable fields (total checkouts, total renewals, circ active...) to the right of these columns. It would be nice to have a sort of drag…
2 votes -
Rearchitect iiirecord.record_metadata to provide improved audit trail accountability
It is sometimes helpful to see who created, updated or deleted a record. Catmaint provides a lot of detail but doesn't cover many record types. I propose the following solution, which doesn't have particularly burdensome storage requirements:
- Build a many-to-many table with an id primary key column, a timestamp, a code indicating the C-R-U-Uprevious-D record operation and foreign keys linking to record_metadata.id and to iii_user.id.
- Backfill this new table using the available timestamps in record_metadata, catmaint and any other table like catmaint which might provide record edit history.
- Rename record_metadata and drop its four *_gmt timestamp columns. Yes, this creates…
14 votes -
Create RestAPI with a Patron Validate role that updates the “last circ activity date” in patron record
Our library wants to provide the patron validate role to our vendors.
But, we do not want to give the vendors any read or write roles.We do this now with several vendors, but the authentication does not update the "last circ activity" field in the patron record.
Is it possible to add a new permission that would only allow authentication but update the "last circ activity" field in the patron record.
Why add this feature?
Our library purges patron that don't circulate for X number of years. We don't want to delete patrons that are actively using our eVendor…27 votesSelected for the Sierra 6.7 release by MEEP enhancement process
-
ID scanner to auto-populate account information
A Sierra feature to allow scanning a Driver’s License to auto-populate customer information for a new account and/or to update an existing account. Automatically inserting a customer's name, date of birth, address, and DL number would result in less typos/mistakes, save considerable staff time when creating or updating an account, and additional staff time in reviewing and fixing errors.
4 votes -
Improve search relevancy for titles with many adaptations
Our staff have found that when they search the staff catalog for classic titles with lots of adaptations many of the adaptations are ranked higher in the search results than the title they actually searched for. For example, a title search of our catalog for "Moby ****" yields "Ahab's Wife" as the top result, with other derivative works and commentaries all appearing before the first record for the novel itself (in our case, result number 24). We'd like to see the results weight matches on the work's own title (e.g., 245 field) higher than matches in other fields, such as…
13 votes -
The patron selfreg form should record the origin IP in the patron record
To inform the blocking of IP ranges from which bad actors are abusing the /selfreg form, record the origin IP in a varfield or new fixed field on the patron record.
If a varfield, the default of an x-Note would suffice, but make this varfield tag customizable via one of the administrative interfaces. Historically speaking, Admin Corner would have been the go-to place to make this customization.
7 votes
- Don't see your idea?