265 results found
-
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.
14 votesThe product manager will review this idea for possible inclusion in a future release.
-
Allow Global Update of Fund Codes
Allow for Global Update of fund codes. I work in an academic library and will often get purchase lists from our liaison librarians for a specific department. The records are brought in and the attached order records are edited in GU with the correct vendor, and selector, etc. It would be a time-saver if I could also update the fund code (which are tied to academic departments) at the same time.
14 votes -
Add "Available at Branch" to Sierra Search/Holds facets
Staff want to limit their search in Search/Holds to items that are on the shelf at their branch. These would be items with a status of "available" and a loan rule equal to zero.
Circulation workflows are severely impacted when staff have to use the SDA and the Discovery Catalogue to determine if items are in the branch.
Libraries with floating collections or multi-branch libraries do not always know what is on their shelves.
Customers that visit the circulation desk want to know if an item is in the branch. Staff want to know if items on a particular subject…
14 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.
13 votesThe product team will review this idea for consideration for a future release.
-
Lock Commands in Rapid Update
When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands…
13 votesThe product team will review this idea for consideration for a future release.
-
System Option to Disable Transit Slip Printing by Default
In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.
Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of…
13 votesThe product team will review this idea for consideration for a future release.
-
Fix "Tile Vertically" so the bottom of the records don't get hidden behind the taskbar on Windows 11.
In Sierra, on Windows 11, when you click "Tile Vertically" so you can see multiple records at the same time, it makes the windows too long, so that the bottom of the windows get hidden behind the taskbar if it is locked. It does not do this if you maximize a record window, or if you use snap. It only seems to be the "Tile Vertically" function.
We use this function a lot to compare records for deduplication, and it is really annoying to have to manually resize windows so you can see the whole thing.
13 votesThe product team will review this idea for consideration for a future release.
-
Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our…
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Customise font size and other details in Sierra pop-up messages
We'd like the ability to customise the font size of the text in Sierra popup messages i.e, increase font of where items are going to be picked up, or making the destination in the top part of the message stand out? Or removing call number which we do not use.
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Add a Note Field in the RFID Pad Server Options Table
As ILS administrators of a large consortium, we would like the RFID Server Options Table to have an additional field/column to add notes (library name, dates, staff initials). When one of our member libraries needs to change RFID entries, we sort through nearly 200 lines to determine which one needs updating. Many entries use IPs without identifying library information. We must read through old library correspondence to discern which IPs belong to the library. This task takes up valuable time when we are trying to assist a library with troubleshooting or adding and removing entries.
An additional free-text field to…
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
It's about time to make Holds APIs first-class citizens
Idea Description
It would be far nicer to have the ability to work with hold data directly--in contrast to having to retrieve hold data via the patron APIs. For example: currently, in order to (reasonably) find the "pickupByDate" values for holds with status "(Bib, Volume, Item) hold ready for pickup" you would have to use a combination of the Sierra SQL feature (to first find all the patron record numbers possessing such a hold) and then filter all the holds for the list of patrons (from the previous step) having the "pickupByDate" key in the response object. Once you have the holds,…13 votes -
Dark contrast display option for the SDA
We see the Sierra 6.0 Release Notes features new Accessibility improvements in the SDA. It is unclear if this includes a high contrast display option which staff recommend to support use of the software by many different types of staff.
13 votes -
Sort "Due Date" column in "Item" view as date instead of string
When a user is in the Cataloging workflow, the "Due Date" column in the "Item" view is sorted as a string instead of a date, eg "1-01-2023" comes before "9-01-2021". It would be helpful for this to be sorted as a date and match the sorting of the "Due Date" column in the "Holds" view.
13 votes -
Control of Scheduler FTP File Names
When you export a file with Scheduler FTP, it currently adds a time and date stamp on the end of the file name. We have no control over this addition to the file name. This stamp makes the file completely useless for many applications. Many of the vendors we might send files to require particular file extensions on our files, such as .mrc. Since this stamp is added to the end of the file name, it is not possible to specify the required file extension.
As a result Scheduler is completely incompatible with Ingram's Ipage service for example.
We need…
13 votes -
Override Prompt/Authorization Required - List Permission(s) Needed
Sometimes it's unclear what permission is triggering the authorization required/override prompt during a transaction and thus what staff member will need to step in to override/allow the transaction to go through. It would be helpful if the "authorization required" prompt included the permission(s) that apply to the transaction.
13 votesThe product manager will review this idea for possible inclusion in a future release.
-
Postpone/freeze a hold after it's Ready for Pickup
Postpone/freeze a hold after it's Ready for Pickup
Similar to Overdrive's redeliver option. Allow a patron to postpone/redeliver their hold one time if it comes in unexpectedly or at a time when they cannot come to pick it up.13 votesThe product manager will review this idea for possible inclusion in a future release.
-
Include hold pickup location in circ_trans
Analysis of holds is often requested by managers keen to see what users are requesting and how much material is going where across multiple sites.
However a lot of detailed information on holds in the SQL tables is transitory e.g. hold, hold_removed.
I have long thought that it would be helpful to include hold pickup location in circ_trans, which provides a historic perspective and can be downloaded and/or adjusted to capture longer time frames.
This would enable data and analysis which is not possible currently.
13 votesThe product manager will review this idea for possible inclusion in a future release.
-
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…
12 votesThe product team will review this idea for consideration for a future release.
-
Add "max number of overdue items" column to patron block table
Many libraries have eliminated fines and they would like alternative ways to provide an incentive for patrons to return items. We would like the option to block patron circulation based on a Library determined number of overdue items. This rule could be added to the Patron Block table so that libraries could customize rule as necessary.
Idea Value: This new setting would provide an incentive for Customers to return their items.
Idea Value: We don't want to restrict the number of items a Customer can sign out, but want to restrict borrowing after a specific number of overdues.
Idea Value:…
12 votesThe product team will review this idea for consideration for a future release.
-
Additional (Staff Only) Message Field In Patron Records
We have been considering enabling the display of the free text Message field in patron records in the WebPac (& a corresponding tab in Bibliocommons). It seems like an easy & useful way to quickly & effectively communicate with customers on issues related to their account.
For example, we might want to create a list of patron records at a library location that is closing for renovation to let them know that for the duration of the closing, their holds will be routed to another nearby branch. We'd apply the message to impacted patron records for as long as it's…
12 votes
- Don't see your idea?