273 results found
-
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.
-
Always renew a checked out item in SDA if there is an available item (without pop-up)
By default in the SDA, items are blocked from renewal if a hold is placed on the associated title or volume.
If the Renew Title Holds feature is enabled, the system gives you the option to OVERRIDE the block on renewing held titles and volumes. The system does not consider frozen holds when blocking items from renewal.
Staff will always select "yes" to a renewal if there is an available item. They do not want to continually select "override" when they are renewing multiple holds.
Can there be an option to always renew if there is an available item (without…
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.
-
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…
6 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Improving loan history
Our patrons are curious about their loan history. They would like to sort it by author or title in addition to the checkout date. We have told them to export it. But exporting the checkout history loses the checkout date! Could more sorting possibilities be added to the catalogue and checkout date added when exporting?
6 votes -
Improve item title display on patron-facing devices by adjusting SIP2 parameters
Skip certain MARC subfields when preparing data for SIP2 connection.
Specifically:
When Sierra needs to send information to display an item title on a patron-facing device (automated materials handler, self-checkout kiosk, etc.) via SIP2, it currently appears to concatenate all occupied subfields of MARC field 245 and remove the delimiters. This means that certain information not intended to be patron-facing can end up appearing in the title the patron sees on screen (e.g. "880-01 Desu nôto 2..." appearing instead of just "Desu nôto 2...", where "880-01" is not actually part of the title, but rather a reference to another field…6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Expand Locations field for bibs, holdings, and orders API responses
Currently, the bibs, holdings, and orders APIs do not return the expanded Locations fields for records with multi locations. The multi location value that is returned is useless without the expanded values.
6 votes -
Allow an option for patrons to choose a different default pickup location in Encore instead of it defaulting to the patron's home library.
Currently, when a patron is logged into their Encore account and they place a request, the system will default to their home library for the pickup location. If they want to pick up somewhere else, they have to manually choose that option from the dropdown menu.
We want to keep the home library field limited to physical library locations, but allow for alternative pickup options that aren't specifically a home library (community pickup location, or hold lockers, etc). Right now, if you want to pick up somewhere other than your home library, you have to choose from a dropdown option.…
6 votes -
Warning at Hold Placement for Homebound Patrons
Description:
Sierra’s “Check Reading History During Homebound Checkout” feature is very helpful, but many homebound materials in our workflow are supplied through holds from other branches. At the hold placement stage, no warning is shown if the patron has previously borrowed the same title, which leads to unnecessary requests and inter-branch transfers.Requested enhancement:
Add an option to display a warning when a hold is placed for a homebound patron if their Reading History shows a previous checkout of the same item or another item attached to the same bibliographic record.Benefits:
- Avoids unnecessary item movement
- Saves staff…5 votes -
Update Expected Format Requirements for Email Variable Length Field
Idea: update the expected format requirements for the email variable-length field to account for modern, non-standard email domains.
Relevance: The prevalence of non-standard email domains is growing. Currently, Sierra accepts some non-standard formats, like .me, but rejects others like .health. This prevents the saving of the patron record and requires that the patron provide another email or change their notice preference.
5 votes -
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
-
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 -
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
- Don't see your idea?