286 results found
-
Scheduler: include workflow to schedule/export completed SQL scripts
Scheduler is a powerful tool. Libraries would like to use that tool to schedule SQL scripts. I understand that libraries use 3rd party tools to create SQL statements and then schedule/export/send the results to other 3rd party tools. It would help a lot of libraries that don't have the resources to do this extra setup if a query could be added to scheduler and that query be emailed to one or more individuals in a csv file.
Why do libraries have to use SQL? SQL allows us to query/export/link fields that cannot be queried in Create Lists. Querying the database…
6 votes -
Improvements to Updated Bib Headings report using AACP
When AACP is turned on and we've loaded new / changed authorities, there are some bib records impacted by the authorities' headings which do not get automatically updated and require staff edits. Sometimes it is terminal punctuation that needs to be added for certain entries perhaps tied to a new closed death date; or sometimes it's an indicator in a bib MARC field that should get added because it's in the authority record that's new or changed. We think just a little bit of development here would help save staff time.
6 votes -
Provide In Transit status and print transit slips for ILL items
ILL items- In Transit status and print transit slips
We have three branches and our ILL department is located at one of the branches. We would like the ILL module to change the status to "In-Transit" instead of "Ready for Pickup" and print a transit slip when the items are being sent to two other branches.6 votes -
Translate item status and OPAC message codes in Summary View
Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.
6 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 -
Send to: Notices
It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to the Notices function.
I had submitted a similar request that the shortcut be added to Globally Purge Charges & am wondering if this might be combined into one request or if it's easier to introduce them one at a time?
Use case: each week, Cincinnati generates a list of customers sent a statement of charges (bill notice) via Create Lists. This list is then…
6 votes -
/v6/patrons/{id}/holds/requests/form API endpoint should accept item record numbers as parameters in addition to bib record numbers
The form endpoint is used to identify cases in which a patron must place a volume level hold or is restricted to an item's home library as a pickup location. Both of those involve item level specifics and yet the endpoint only works with bib records. This is an issue in particular with multi-location libraries/consortia who use the home pickup feature.
As an example, a sample bib record has two attached items, one which uses the home pickup feature such that it may only be picked up at library A, and one that does not restrict pickup locations so may…
6 votes -
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…
6 votes -
Make the "New PINs do not match" message configurable in PIN reset flow
In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.
This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.
Suggested improvement:
Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQ…6 votes -
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.
-
Add Sierra Hold Request Date into Hold cancellation notices
Support team told us Sierra isn't designed to supply hold request date for cancellation notices. Please consider add it. thanks
6 votesThe product team will review this idea for consideration for a future release.
-
Increase Max Size of Item Code 1 Field
The Item Code 1 field was going to solve all my statistical issues. I thought it had 5 characters and each character could be 0-9 which meant I could assign a meaning to each character. For example, the first character indicates agency (1 for CPL, 2 for ADL, 3 for BKM) and the second character indicates audience (1 for adult, 2 for young adult, 3 for juvenile, 4 for other) and the third character, format, etc. HOWEVER it turns out that the largest number this field can hold is 32767 which is weirdly random and very limiting when you want…
6 votesThe product team will review this idea for consideration for a future release.
-
Allow libraries to customize return addresses for bills
Our library would like the option to have the return address for bills reflect the address of the patron's home library (as defined in the patron record) rather than the owning location of the item. The current setup (using the owning location of the first item on the bill) means that when patrons check out items sent from another branch to fill a hold, they can receive a bill from a library that they may never have been to. While patrons can visit any of our locations to resolve a bill, we would prefer the bill to reflect their local…
6 votesThe product team will review this idea for consideration for a future release.
-
Require authentication to view Sierra API documentation
Enhance cybersecurity by not revealing the api methods through the swagger interface to unauthenticated users. For example, a potential hacker can view the swagger interface which shows all methods and explains how to use them. This is an issue on all api endpoints including the iii sandbox. My idea is to only reveal the swagger methods to authenticated users.
https://sandbox.iii.com/iii/sierra-api/swagger/index.html#!/patrons
6 votesThe product team will review this idea for consideration for a future release.
-
Reading History via API
At this time it is apparently possible to retrieve the patrons Reading History via REST API sorted by date (oldest first or newest first). The most requested API enhancement request for us is to be able to retrieve the patrons Reading History via REST API sorted by Title. Another enhancement request is to be able to retrieve the patrons Reading History via REST API sorted by Author. This would be useful since users may have hundreds of items in the reading history.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Location Code 0 Displays as None in Checkout Location Field
With the recent changes that allow the label to display in the item record, staff now see the descriptive name of the statistical group in the checkout location. However, 0 displays as None and does not honor what is in the Statistical Group Maintenance table. We have ours labeled for Web Renewals and would like this display to honor what is in the table as opposed to saying 0 None.
6 votes -
Add a column for Loan Rule # to Loan Rule Table instead of using seq # in the table
Today the Loan Rule Number is the position in the Loan Rule Table. This means when we need to keep a lot of old and often Inactive rows in the table so that the loan rule numbers below don't change.
If you added a column with a loan rule number separate from the sequence in the table that the Loan Determiner table would point to, we could still mark old rules inactive until we are sure there are no more checkouts, but after we confirmed that we could delete the row completely and keep a much neater cleaner table with…5 votes -
Create an API endpoint that delivers language translations to Vega
We maintain English and Te Reo Māori names for library branches and item locations in the Sierra branches table. Making these available through an API would allow Vega to display the correct names automatically, and provide a consistent bilingual experience. This would also remove the need to manage translations separately in Vega Admin.
5 votes -
Make Third Party API Transactions More Apparent in Sierra
Some time ago, an idea was submitted to enhance the Sierra API to provide statistical group information, so that circulation transactions in third party applications could be credited to a statistical group other than 0 None.
The idea won the "Let's Connect Sierra API Challenge."
With the release of Sierra 6.0, it then became possible to include a new optional data parameter to specify the statistical group that should be used when recording a transaction performed using the APIs.
My library was excited to hear this, as we'd recently begun using the self-checkout feature in the Bibliocommons' app not long…
5 votes -
include PostgreSQL scheduled patches and upgrades in roadmap and upgrade documents
Sierra 6.6 includes an upgrade to PostgreSQL 16. Innovative should be more specific and tell us that we are upgrading to PostgreSQL 16.10. PostGres 16.14 was the last version in this cycle.
Does Innovative upgrade PostgreSQL with each Sierra upgrade? Will they patch between upgrades with any security fixes?
Libraries need to know Innovative's plans PostgreSQL development, and I am unsure if they are always included in the upgrade notes.
5 votes
- Don't see your idea?