281 results found
-
Add the ability to create a review file from items in Global Update.
Sometimes I'm working in Global Update and am using the toggle feature or the limit tool. I then want to work with just those records. I don't want to remove the others from the review file, but rather copy the records I want to look at into a new review file so that I can work with them there.
6 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.
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 -
Allow for Customization of Fields Included in Expanded Display of Patron Records
I recently learned that the fields included in the Expanded Display for patron records (when you rollover/click the i next to the record) are hard coded.
I found this unfortunate, because what's shown in the Expanded Display differs depending on where you're viewing it, which in the case of patron records is either going to be in the Search/Find a Patron view or the Check Out mode view.
Examples of where I see room for improvement here:
1) When I search for a patron by name & come up with dozens of people with the same name, an identifier like…
6 votes -
Abililty for Sierra's NCIP responder to be able to parse ISBNs
Right now NCIP for Symphony, Voyager, Polaris, Koha and Evergreen all accept ISBNs, but Sierra's does not.
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 -
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.
-
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 -
Enable API update of patron records to blank out expiry date
Sometimes we want to update a patron record and blank out a date in the expiry date field for a continuing staff member.
The patron API cannot do this - blank values are rejected as invalid JSON e.g.
{"expirationDate": " - - "}
{"expirationDate": ""}
{"expirationDate": "--"}
{"expirationDate": "null"}All we can do is add a date, and for continuing staff we can only use the maximum possible date of 18 Jan 2038.
Enhance the API to accept a blank value in expiry date.
6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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 -
Permit due date extension via the API
Currently the only way to extend item due dates is to run Rapid Update on a review file of those items. I would like to be able to programmatically update due dates via the API. I see two potential benefits of this feature:
Benefit 1: Rapid Update prompts for a single absolute date to apply to a group of items in a review file. There have been many times when we have wanted to extend the due dates of a group of items by "n days", regardless of their current due date. It would be straightforward to write a Python…
5 votes
- Don't see your idea?