260 results found
-
Globally purge charges by itype
Idea: add a limiting feature to Globally Purge Charges that allows for choosing which fines to clear by itype.
We use itypes to delineate lending in addition to the location code. With libraries transitioning to fines-free policies and seeking to waive existing overdue fines for patrons on some items (but not all), the current function structure complicates matters, as it only allows for limiting by location code, rather than by item type. There are ways to work around it but they are cumbersome.
5 votes -
Block particular bib records from having their URLs checked by use of a suppression code
Block particular bib records from having their URLs checked by use of a suppression code
5 votes -
Statistics - Saved Queries Should Retain Cross-Tab Selections
Saved Queries in the SDA should function the same as they do in SierraWeb.
In the SDA:
If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on the same record type, then the selection of the two fields in the Cross-Tab Field Selection panel will be retained when switching to another bibliographic review file in Sierra SDA.
If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record),…
5 votes -
5 votes
-
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 -
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…5 votes -
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 -
Add a backdate option to the /v6/items/checkouts/{barcode} endpoint for checking in items
I would like to add an optional parameter to the Sierra API endpoint for checking in items to allow for backdating those transactions as you can within in the client as it may help with automating some projects.
For an immediate example, I have identified a number of items that were not removed from the checkout table correctly due to locked patron records, where the were placed in transit and I can see a time the checkout ought to have occurred via the in transit message. I would like to write a script to correct these failed checkins once they…
5 votes -
Notice scheduling
Currently, the notices for Current Checked Out Items allows for daily or weekly scheduling, but it would be handy to have the ability to set this at a longer time frame such as monthly, quarterly or by semester as most of our materials check out for much longer periods of time (16 weeks or longer generally), and some users find the weekly reminders tedious.
Either the option to set the automated notices to a longer time period, or the ability for patrons to choose a longer reminder period (opt in to weekly, monthly, etc notice) would be very helpful.
5 votes -
Automatically email due slips from Express Lane
Do you want all of your patrons to receive due slips by email, every time they check out an item?
Express Lane can be configured to automatically print a due slip, or allow patrons to choose between some combination of print or email due slips with an option to decline, but cannot be configured to automatically send an email due slip with no option to decline.
In our special library, it is desirable to always send email due slips with no option to decline. We want our patrons, who are all employees, to receive this documentation for every loan for…
5 votesThe product team will review this idea for consideration for a future release.
-
Validate tickler date field to prevent miltickle failures
When a tickler has invalid data in the "Date (YYYYMMDD)" field, Sierra's nightly tickler process will fail and any ticklers on order records not already processed will not be sent. This failure will keep happening every night until the problem is discovered.
For example, dates entered with dashes separating the elements ("YYYY-MM-DD") or with additional characters following the date ("YYYYMMDD - Note text here") will cause this kind of failure.
In the absence of an easy way to search for invalid data in the tickler date field (e.g., Create Lists), it would be very desirable for Sierra to validate user…
5 votesThis development is planned for Sierra 6.7.
-
Allow Requiring SAML for Sierra Web
Sierra now supports SAML for authenticating staff, but still allows users to authenticate without MFA using the less secure Sierra legacy authentication method. Sierra should allow administrators to require SAML authentication instead of always allowing users to choose SAML or Legacy.
5 votesThe product team will review this idea for consideration for a future release.
-
Unfilled Pages Function
Following Disney's lead of recycling years old ideas for theme park attractions, I'd like to see an idea I'd had while working with a former employer brought to fruition in Sierra. We had been using Millennium at the time & the Circ Product Manager had gotten to a point in development that there was a near-working model on III's test environment (I've got screenshots & even a Captivate video somewhere), but I left that employer & the III product manager left III & the idea was abandoned. Sure, it's not as exciting as Disney's announced "Villains Land" or a boat…
5 votesThe product team will review this idea for consideration for a future release.
-
Provide direct access to Decision Center's Title Details page
One of the nicest features in Decision Center is the title details screen, which you can access by clicking on a title in the handful of reports that include title entries such as the Popular Titles Report.
However, if you're logged in and happen to know the URL structure for those pages (https://[your Decision Center URL]/report/titleDetails/[bibnumber]) you can actually pull up the information for any title in your database directly.
I'd like to see a means for navigating to that screen more directly and just expose this awesome feature of the platform that already exists. I envision a simple page…
5 votesThe product team will review this idea for consideration for a future release.
-
globally update bibliographic records with multiple branch codes
We would like to be able to globally add an additional bibliographic branch code to a subset of bibliographic records harvested through "create lists." This is because currently (Sierra 6.1), it is possible to change a bibliographic branch code, but not add additional ones while retaining the original branch.
The reason is that we have records for electronic resources that should display under a relatively new scope set up for a new branch. With only the original branch in the bibliographic record, it is necessary to view the entire collection (or the original branch) to access the item in the…5 votesThe product team will review this idea for consideration for a future release.
-
SAML matchpoint with patron variable field
We implemented Patron SAML and uses a patron variable field to be the matchpoint. This field contains the patron's email address. Our IdP accepts dots, dash and underscores in patrons' email address. Due to Sierra indexing rules where symbols (including dots, dash and underscores) will be dropped, different patrons with the same letters in their email address but have different symbols in different positions won't be able to authenticate through Patron SAML.
e.g. Patron A's email = abc.def@test.com, Patron B's email = abc_dec@test.com . Both will fail authentication as Sierra will use abcdef@test.com and return both patron records.5 votesThe product team will review this idea for consideration for a future release.
-
Expand to different order statuses for the Sierra REST API
The Sierra REST API does not return the order record for the bib if the order status is "a" (fully paid). It will only return information if it's "on order".
Patrons are unable to place holds on new materials using Innovative Mobile for bibs with paid order records that do not yet have items attached.
5 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
give libraries the option to exclude ratings from Homebound circulation workflows
Our homebound customers love the Sierra reading history functionality, but tell us that they do not want the Library to give them a checkout receipt that includes an option to rate the title. They also tell us that they do not want their personal information on the receipt (and the library cannot edit the Homebound receipt template).
Additionally, circulation staff workflows are hindered because if a stack of homebound items are returned, they have to use the keyboard / mouse to move past the checkin rating prompts.
5 votesThis idea will be reviewed by the product management team for possible inclusion in a future 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.
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.
4 votes
- Don't see your idea?