257 results found
-
Access to SAML logs
When using the LDAP authentication option, it was useful to be able to see the authentication logs to diagnose login issues. After switching to SAML authentication, access to the SAML logs is only available to Innovative support.
I propose granting customers access to the CAS Apereo application logs so that we can see SAML authentication issues. These logs may not be as detailed as the LDAP ones since the authentication is happening at the IdP but they might provide clues to further investigate authentication issues.
1 vote -
Re-Page Item Level Holds
Our library would like to have pages for item-level holds repeat until they are filled. Currently, the only way to achieve this is by checking the "Do Not Clear" checkbox when running the item paging list each day. However, staff have to remember to toggle this setting every time they run the list, and if they forget, all previous pages will be lost and can't be restored the next time they run the list.
We'd like a way to have item pages persist by default.
5 votes -
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…
2 votes -
Separate summary view property for each of the search functions
This idea is essentially to address a design flaw that goes all the way back to the migration from Millennium to Sierra. The record view property setting was originally designed for the context of Millennium, where there would be entirely separate logins for circ, cataloging, acquisitions, etc...and adjusting the setting would only impact a single search function. But in Sierra when a single user may have multiple workflows available to them that breaks.
When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open…
2 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…
2 votes -
Modify Estimated Price Via Rapid Update
Our Acquisitions staff does not use List Price when ordering, & is hoping that Estimated Price could be modifiable via Rapid Update. At the moment, this would help them modify 200+ order records, which they now have to do manually.
2 votes -
Sorting Searches in Patron Indexes
When creating a new customer record from scratch, or when updating & finalizing those submitted through our online application, we have staff perform some checks to prevent duplicate records.
They'll begin by searching the Name index to make sure that there's no pre-existing record for the same name. Then as backup, they'll try searching by birth date or phone number.
However, when you search by birth date or phone number, the results do not come back in alphabetical order, making things a bit harder than they should be for frontline staff. See example image where the search for the DOB…
1 vote -
Sorting Search/Holds Queries
Staff would like to see the ability to sort results retrieved from queries performed in Sierra's Search/Holds mode.
Say for example they do a keyword search for Star Wars at our Forest Park branch. 124 items are found. The results are displayed alphabetically by default. But if the staff member wants to quickly sort by DVDs, they can't even click on the Format column heading, as it exists currently.
While they can run multiple limits to narrow down the results by format, language, shelving location, publication date, etc., they might just as equally be inclined to SORT the entire list…
2 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.
4 votes -
Use Field long name for create list export
We've updated many of our data fields to have long names that make sense to front end staff who see patron and item records, however Create list sees the long name values when creating a list search, but the export of the data exports the system name. For example PCODE3 is called "Local Library" for our system, but a create list export defaults back to PCODE3. It would be nice to be able to export using the contexual long name so admins and create list users don't have to have a cheat sheet or remember what the system code is…
1 vote -
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 use SQL? SQL allows us to query/export/link fields that cannot be queried in create lists. Querying the database is…
2 votes -
Send patron expiration date in SIP2 response
Our library uses automated lockers to lend laptops to patrons for in-house use. We'd like to block patrons whose cards have expired from borrowing until they come to the desk and renew, while still allowing borrowing for patrons blocked for overdues since these items won't be leaving the library. Our vendor is able to accommodate this for other customers because their ILS sends the patron expiration date in the BW field in the 24 response. Sierra's response only indicates the block in the first position of the patron status element, which includes blocks for all reasons, not just account expiration.…
8 votes -
Two First Names, No Last Name
We periodically have customers that have two first names, but not a last name. When hold slips are printed, Sierra interprets the second name as their last name, but this is not the case. We would like to just have their two first names show up on the holds slip, if possible. We have done a workaround for now to ensure that the name they use is the second name listed so that their holds slips show the first name they use, but it would be better to have both names printed.
1 vote -
Add Patron Type Category Grouping to the New Patron Checkout Limits Table
With the new Patron Checkout Limits table, we have lost the ability to group patron types (ptypes) into a category when configuring checkout limits that also use criteria such as Library Location or Item Location.
Currently, a separate row must be created for every individual ptype, which significantly increases setup and maintenance effort. In environments with many patron types that share the same checkout limits, this results in a large number of duplicate entries.
We would like the ability to define and use Patron Type Categories/Groups within the new Patron Checkout Limits table, similar to the functionality available in previous…
19 votes -
Track User, Time, and Process for Deleted Records
Currently, when a record is deleted in Sierra, the system captures the date via the deletiondategmt, but it doesn't track the exact time, the specific Sierra user, or the process used to delete it. We would like to see this metadata enhanced to include the Sierra user, a timestamp, and the function or process used (Delete Records, API, etc.), with the date.
Tracking these details is critical for consortium management, system auditing, and data integrity. Having this information readily available would significantly improve our ability to handle targeted staff training when records are deleted in error, investigate the…
10 votes -
Allow Patrons to Opt-out of Certain Circulation Notices
Many libraries offer mail delivery services for patrons who are unable to visit in person. Currently, when items become available, these patrons receive a standard "ready for pickup" notification, even though their materials will be mailed to them. This creates unnecessary confusion and may lead patrons to believe they need to come to the library.
Providing the option to customize or opt out of specific notifications, such as "Ready for Pickup" alerts for patrons enrolled in mail delivery, would greatly improve clarity and enhance the user experience.
9 votes -
Add sierra login to the checkout logs
The log files in the system currently have no way of tracking a given checkout to either a specific computer terminal OR to an individual sierra login. We occasionally have reason to need to confirm certain actions by staff members, but the log does not allow us to confirm what staff member performed a given circulation transaction except by stat code.
5 votes -
SAML login page customization
The SAML login page with the option to choose SAML or Library login is very basic and does not convey information to patrons concerning the choice. In addition, the customization have limited options and are only available to Innovative support.
The proposed idea is to provide more customization options for this page and open these customizations to customers through a self-service feature. In addition to the current options available to Innovative such as logo changes and colors, the SAML login page should have options to add a block of text for instructions using HTML so that links could be included.…
1 vote -
Ability to find the most checked out item in a year
Ability to find the most checked out item in a year
Please add a simple way in Sierra to report the most checked out item for a selected year, including the option to show the top five checked out items.
Currently, this is very difficult or impossible to do directly in Sierra because checkout totals are not stored in a way that allows staff to easily rank items by circulation count for a specific year. Create Lists can find items based on fixed fields, item data, and limited transaction-related criteria, but it cannot easily produce a yearly “most checked out”…
7 votes -
Ability to send checkout receipts
It would be helpful if LX Starter allowed for patrons to receive checkout receipts via email. Sierra currently supports customizable checkout receipt emails using Due Slip print templates, but these are difficult to work with.
52 votes
- Don't see your idea?