68 results found
-
Edit Username in Admin App
Once a user is created in the admin app, you are not able to update the username. You may update the password, permissions, etc., but not the username itself.
All of our clerk-level positions are part-time, so there is a lot of turnover. Each time an employee leaves, his/her account must be deleted and a new one created for the replacement. When the new account is created, you then must import all of the permissions, options, locations served, etc., of a comparable employee for the same location.
Ideally, we would simply be able to edit the username and password and…
64 votes -
Add "Back" option vs. just "Next" or "Cancel" in Record Creation screen
When you create (a) new item(s) while cataloging -- or create any records actually! -- the pop-up that guides you to enter the data step-by-step should have a back button. Currently, if you make a mistake and click Next you either have to cancel and start over or keep going and fix the mistake on each item record individually after saved/completed. It can be quite tedious when you are adding multiple items at once.
Idea Value
Save time! What would just take a few clicks/seconds to fix can sometimes mean a lot more time, especially if you Cancel and have…
56 votesThis idea has been selected to include in Sierra 6.4
-
Update print templates to support current release of Jaspersoft Studio.
The ability to create custom print templates is an essential component of many parts of the system. LX Starter is a viable replacement for the templates used for notices but not for the printing of things like due slips, spine labels, and hold slips that must remain within the SDA to support daily workflows.
Print templates are designed in a third party software called Jaspersoft Studio, but Sierra's documentation lists version 6.0 as being the last supported version of that software. However, that version is roughly 10 years old and the installer only seems to exist as an old link…
40 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Alerts for when indexing stops
Currently there are no alerts when indexing stops working. We would like to see some put in place.
We recently had our keyword indexing stop working. It wasn't completely obvious to us for few months that there was a problem with indexing as it didn't seem to be every record.
Idea Value
Having an alert to III would save time troubleshooting if it's a metadata problem and raising tickets for something that could have an alert on it.37 votes -
Make Sierra User Profile Imports Additive, at least Optionally
In the Sierra web-based admin utility, in Authorizations and Authentication Admin, when importing permissions from one Sierra user to another, the "donor" settings overwrite those of the recipient user. I propose adding a checkbox to allow these to be imported in an additive manner.
Idea Value
Recently two of my coworkers in Technical Services and Collection Development received promotions and shifted into different roles. When using the feature to assign the permissions of users similar to the new roles, old but still valid permissions were lost due to the way the feature overwrites the recipient permissions with those of the…36 votes -
Make OpenAPI definition document (previously known as Swagger specification) available for Sierra's APIs
There SHOULD be an OpenAPI definition document available for Sierra's APIs via Swagger, but currently, there is not.
The OpenAPI definition document (https://swagger.io/specification/) is a standardized format for describing the structure and behavior of an API. It is a machine-readable document, usually written in JSON or YAML, that provides a comprehensive blueprint of an API's endpoints, operations, input/output parameters, response formats, authentication methods, and other essential details.
For comparison, here is an example for the Polaris API / Swagger install (on an iii training server):
https://polaris-training.polarislibrary.com/PAPIService/swagger/v1/swagger.jsonBenefits of an OpenAPI Definition Document:
…* Standardization: Provides a consistent format30 votesThe product team will review this idea for consideration for a future release.
-
Staff activity log
We occasionally have issues with staff abusing their ability to waive fines or deleting items inappropriately or accessing patron accounts outside of acceptable library operations. We would like to have a way to view these actions within a log file associated with each Sierra login (or filterable by login) so that these activities could be periodically audited by managerial staff and retroactively be reviewed when inappropriate system activities are believed to have taken place.
23 votes -
2038 issue
We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.
21 votesThe product team will review this idea for consideration for a future release.
-
New Skins for Sierra
Can we get some new skins to choose from for the SDA/Sierra Web?
There are currently two: Half Dome & Glacier Point.
We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.
Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?
21 votesThe product team will review this idea for consideration for a future release.
-
Make Review Files in Admin App Consistent w/SDA & Sierra Web
In Sierra - SDA and Web - you can sort review files in Create Lists by the column header, i.e., file #, current records, max records, type, status, login and created.
In the Admin App (BACK END MANAGEMENT > Review Files), the only columns displaying are file # (which doesn't appear to match the file # in the SDA/Sierra Web), number of records (= max records), current and name. Sorting by column is not an option.
The display, labeling and function for managing review files should be consistent.
Idea Value
When managing review files in the admin app, particularly when…21 votes -
Create a GET API endpoint for circulation transactions
This idea came from a discussion at the IUG2025 Sierra Reporting Forum.
It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to…
20 votesThe product team will review this idea for consideration for a future release.
-
Batch Check-In Should Not Update Circactive Date
Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.
We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.
Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.
This…
20 votesThe product team will review this idea for consideration for a future release.
-
Sierra should send an email notification when Offline Files are Uploaded
As the system administrator overseeing a 54-member library consortium, managing Offline File Processing is a routine responsibility. However, we often encounter delays in processing files because libraries don't consistently notify us when they upload offline files. This results in files remaining unprocessed until the next library contacts us, potentially causing unnecessary checkout delays. If we process the files too many days after uploading, additional errors may occur, making it challenging to track items adequately.
An email notification for Offline File Processing would ensure timely handling of uploaded files. We could proactively monitor file uploads, swiftly process them, and promptly address…
18 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Connect Global Update with Scheduler
We complete many repetitive tasks in cataloging and patron record management each day. This entails using Create Lists to generate the list, and then using Global Update to perform the same set of edits each time. We need Scheduler to be able to connect into Global Update to perform those tasks automatically.
This may require enhancement of Global Update to save the Command Input, or it might mean adding the Command Input choices to Scheduler.
Example:
Scheduler runs an updated Create List using a saved search query to identify items that need their suppression code updated.
It then uses a…18 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…
17 votesThe product team will review this idea for consideration for a future release.
-
Ability to change password on login page of SDA
Many libraries are creating individual logins for each staff member. Staff needs the ability to change their password in case they forget it. At this point, they need to be logged into the SDA to change their password which doesn't help if they can't remember it.
17 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Ability to disable a user with one click in Admin Corner
The ability to log into admin corner, view all users and with one click disable them (not delete, but deny them log in access) would be helpful for those with revolving part time employees.
We have student employees that change out regularly, but sometimes they come back as graduate student help, etc within a short time.
Being able to simply turn off an employees access and review it within a year or less to determine if it should be deleted or held would be helpful for keeping our staff accounts cleaned up.
16 votesThe product team will review this idea for consideration for a future release.
-
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…15 votes -
Ability to view history for item and volume records.
It would be helpful for us to have access to the history of item and volume records, including details of their creation and any subsequent edits. This would improve our ability to track changes and ensure accountability if any issues come up.
15 votesThe product team will review this idea for consideration for a future release.
-
Granular Permissions on Item Record
We would like to see more specific permissions on items records to allow staff who don't have access to edit entire item records to be able to do basic things like add and delete item messages or change the status of the item.
Frontline staff are discovering outdated item messages or finding that items are missing, and it's inefficient for them to have to contact someone else to change the status of the item, or delete an item message attached to it.
15 votesThe product manager will review this idea for possible inclusion in a future release.
- Don't see your idea?