286 results found
-
Auto- Update library card expiration dates
When a new library card is created in a month, Sierra auto-populates the expiration date for the card as next month +3 years, but this has to be manually adjusted every month by the Circ supervisor. It would be nice if Sierra could automatically set the expiration date for library cards created every month.
7 votes -
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.
13 votes -
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…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…
25 votes -
Expand Window for Create List Export Criteria Display
When exporting from create list the pop-up window can be expanded, but the box displaying the criteria (chosen fields) cannot. We often export more fields than can be displayed within the box. It would be helpful to allow this box to show more of the criteria in a single view so that we can both check what is being exported and easily note what is included when attempting to add the same export to a different list. (We have already maxed out the number of saved exports.) Expanding the window provides an empty space underneath the section displaying the criteria.…
10 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.
8 votes -
Improve the labels for LDR, 006, 007 and 008 in Create Lists
Currently in Create Lists it is very difficult to specify criteria for special fields like the leader, 006, 007 and 008. Many of these have the exact same label, like Audience, which appears four different times. Each of them is for audience as it appears in different versions of the 008 for different record types. Then it appears four more times in the 006.
It would be helpful if each of these different audience codes were labeled in Create Lists, such as "Audience for Books," and "Audience for Music," etc. This would make it much easier to use this function.…
5 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.
6 votes -
Add the ability to transfer an item-level hold to the bib level
Please add the ability to transfer an item-level hold to the bib level. In our system, holds automatically attach to an available item. When the item that has captured the hold is unavailable for some reason (ie. the item has gone missing), there is no easy way to deal with the hold if there isn't another available item. You only see the option to transfer the hold to another specific item. If these are all circulating or unavailable and there is a list of holds at the bib level, you cannot currently transfer that item hold back to the bib…
6 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…
22 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.
11 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 -
A "full Payment History file" event should log an error to the Admin App's System Messages log
Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.
Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged,…
15 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…
13 votes -
Add an API endpoint which permits writing to review files
Currently, when a query is beyond the capabilities of Create Lists, it is usually possible to use a SQL query with Python to produce a report. Such a report might list record numbers of bibs/items/orders/patrons/etc which bear further examination and correction by library staff, but staff must copy record numbers or barcodes in the report and paste them into the SDA to pull up the records in question. It would be much easier if an API endpoint permitted those record numbers to be written to a review file so staff can go through them one-by-one in the SDA.
Another use…
11 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…
24 votes -
Add a Stat Group When Creating a Patron API Key for Vendors
This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or…
26 votesThe product team will review this idea for consideration for a future release.
-
Add 'Previous' button to Receiving
Staff are really appreciating the addition of a 'Previous' button to the record creation process which allows them to back up and fix a mistake without having to go all the way through the process before returning to make a correction. Staff would like to see similar functionality within the Receiving process. We receive using the process that combines creating the item with receiving.
Currently, for receiving an item, it will prompt you through the boxes to fill in the required information. As you proceed through, if you make a mistake or skip something you have to cancel and start…
12 votes -
Additional patron block controls
Additional options for patron blocks would be amazing and allow additional control for libraries to select what integrated systems or circulation services are available. e.g. Block self-service options in the library (SIP2 or API), however, allow holds to be placed through discovery layers.
The controls don't have to be limited to this. Adding the functions and options to select how these are applied from Sierra, rather than relying on integrated systems to control this would be great.
6 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…21 votes
- Don't see your idea?