266 results found
-
Permit writing a pre-encrypted PIN via the API without additional encryption
For testing purposes, it would be beneficial to be able to make a backup of a patron PIN, assign a new temporary PIN, perform the testing from the patron's perspective, and then restore the original PIN. This way we would not have to inconvenience the patron by asking them to reset their PIN when testing has completed.
We can retrieve the encrypted PIN with this API GET request:
https://library-app-server:443/iii/sierra-api/v6/patrons/patron-record-number?fields=varFields
but the PIN string will be re-encrypted if we attempt to write it back using the patron record PUT request. We would like to have the option of passing a directive…4 votes -
5 votes
-
Time to Holdshelf Delay Period Not Reflected in SDA Holds Status
The Time to Holdshelf feature in Sierra is useful in keeping patrons from showing up too early to pick up their holds. As seen in the attachment "Discovery Layer View" – which in our case happens to be BiblioCore – the availability status correctly reflects that the recently checked-in item "Easter Mice!" is not ready for pickup because the item is en route to the pickup location (which in this case is a set of freestanding pickup lockers in a remote area of the county).
However, the holds status as displayed in the SDA incorrectly reports the item as being…
25 votesThe product team will review this idea for consideration for a future release.
-
Ability to alter the Recommends Approval and Denial emails that go to patrons who submit a purchase request
Problem: The text of emails sent when using the Approval and Denial notifications in Recommends cannot be currently altered. We would like to be able to provide more customer friendly email templates to patrons that allow us to explain why an item was denied or what the process is for items that are approved.
Impact: Being able to communicate with our patrons at the outset of the process will save staff time by not having to have go back and forth with customers over email to explain processes and reasons for purchase requests. Additionally it will improve the customer's experience…
5 votes -
Hold Pickup Reminder/Courtesy Notice
Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.
Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want…
34 votesThe product team will review this idea for consideration for a future release.
-
Money Owed Data Point for Billed Notices
Idea: add the money owed fixed field as an option for a data point in the Bills Notice Data Library for print templates.
Value: Some libraries would like to be able to call out to users how much in total they owe on their account, not just the total of the items on that particular bill. Adding this field to the data library would enable them to do so.
5 votes -
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.
16 votesThe product team will review this idea for consideration for a future release.
-
Add an Option to restrict Bibliographic Records within the Sierra System ( specific permission)
Problem:
In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:- Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.
Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.
Recommendation:
Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra…
11 votesThe product team will review this idea for consideration for a future release.
-
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.
-
Inter-library loan
We use forms in Sierra for inter-library loans. We have, however, found that some users are too quick in submitting requests. I think it would be a good idea for ILL forms in Sierra to have additional functionality to slow user behaviour down and to allow for more accurate ILL requests:
- We have ILL conditions included as text below our ILL forms that would be better served as check boxes in the form e.g., "I understand I am responsible for copyright"; "I understand I am responsible for any replacement or repair fines".
- I also think if we could make certain…
1 vote -
Add API endpoint to update MARC Leader fields
Our consortium would like an automated way to update the encoding level to help with managing load profiles that use the encoding level priority function. It would be very helpful to add an API endpoint for updating all the MARC Leader fields. The 008 MARC field can only be used for updating some of the Leader fields.
5 votes -
Increase Max System Display Limit for Fines
Our library has very generous allowances for both checkouts & holds on patron accounts. This can sometimes come into conflict with Sierra's seemingly arbitrary system limits. For example, when these items go unreturned & result in replacement charges, which then cannot be added because of the imposed limits. Like my waist can no longer accommodate 32" pants, Sierra cannot currently accommodate the lending policies taken advantage of by some of our more active borrowers.
I'm sure there are other examples where these limits can manifest, but attached is an example message recently seen by staff which reads:
CANNOT ADD FINE…
3 votes -
Block particular bib records from running through a Headings Report, by use of a suppression code
Considerable time would be saved if bib records suppressed from public display (by way of a suppression code) were not included in the Headings Report. These bib records are typically from electronic sets or batches that amount to hundreds of records, some with several headings for each record.
1 vote -
Add multiple items to a review file from the Item Summary page
It's great to be able to add a single item to a review file from the item record page. It would be even better if we could add multiple items from the item summary page.
8 votesThe product team will review this idea for consideration for a future release.
-
Expand the 1,000 location code capacity of Locations Served (portloca) groups
I currently have a need for a Locations Served group which can accommodate 1,245 location codes. The limit imposed by Admin Corner is 1,000 location codes, and per case #08077395, Support asserts that Sierra will not support more than 1,000 location codes per Locations Served (so it's not simply a limit of the Admin Corner interface).
Increasing this limit will potentially lead to a modest increase in memory consumption by any and all circulation processes which hold these Locations Served tables in memory, but do we really need to be concerned about Kilobytes of RAM in 2025? Other Sierra configuration…
3 votesThis idea will be developed for Sierra 6.5.
-
Reinstate Manual Charge
We would like to be able to reinstate manual charges, whether they're for the collection agency fee, or something like a damaged container or replacement power cable. The reason why we cannot currently reinstate this particular charge type is not stated in documentation & while I may have known at one point, memory fades as we age. Being able to simply reinstate a manual charge would simplify & expedite workflows, whereas now, we have to make like Hall & Oates.
1 vote -
Add Invoice Number to Invoice Summary
The Invoice Summary that is sent after posting invoices only lists the voucher number. Our Finance department has to go through the Invoice Register and match the invoice number to the voucher number to know what invoices should be paid. This is very time consuming, and susceptible to human error. Please consider adding the invoice number to the Invoice Summary.
18 votesThe product team will review this idea for consideration for a future release.
-
Add date/time stamp to the "Restart a process/terminal" display
We'd like to see a date/time stamp on the "Restart a process/terminal" display in the Admin Corner and be able to sort by it. We sometimes run out of licenses because staff don't sign out of their SDA sessions at the end of their shifts, and we have to contact Innovative and request that connections older than the current day be closed. It would be helpful to be able to do this ourselves. Currently, we can preemptively reset all connections early in the morning before staff arrive, but if a problem arises during the day we don't want to cause…
8 votesThe product team will review this idea for consideration for a future release.
-
Record History for bib records does not capture elevated credentials
Currently the Record History report for Bib Records in Sierra contains a list of record changes, the login that made a change, and when it was changed.
However, if the change to a bib record was attempted with a login without the required permissions, Sierra will ask for a login with elevated permissions and allow the user make a change once logged in. In this case, the Record history will record the first login (without required permissions), instead of the elevated login needed to make the change.
Problem: Record History report for Bib Records Record History report for Bib Records…
6 votesThe product team will review this idea for consideration for a future release.
-
Make it possible to search for records lacking a MARC field in Create Lists
I recently wanted to run a search for all records that matched certain criteria and did not have an 856 field. However, Create Lists does not currently have a "lacks field" option. It would be very helpful to be able to search for records that do not have certain fields.
23 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?