239 results found
-
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.
-
New Linked Patron logic : Link a patron record to a second patron with no reciprocal link.
Why is it important to link patrons?
- Without linked patron functionality someone that is authorized to pick up a hold on another account is complicated. This is manually done by staff using patron notes, and the authorized patron signs out the book leaving the original hold on the other patron record.
- Parents visiting the library with children would like to jump to the record of each child rather than using the child’s cards.
Current privacy and circulation workflow issues:
- Someone could link to the child record without authorization. If a patron is sharing their circulation details with someone, they should…
8 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Fix truncated Z39.50 server names in SDA
Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.
The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.
As-is, the "Selected Databases" dialog can be dragged wider by the…
4 votesThis idea will be implemented in Sierra 6.7.
-
New function to scan items into Sierra to change an Item status to "in transit"
Our branches select which items should be sent to another library for stock rotation. Before items are sent to another branch, staff change the item statuses to "in transit". For various reasons, the branch staff cannot use Mobile Worklist to batch change these items to "in transit". The staff use Circa, but would prefer a Sierra integrated solution.
Why integrate this solution in Sierra:
Circa is aging out. We cannot limit Circa permissions to only change Item status to "in transit".
We want to use the "item status update date" to track when items last moved to a branch.
We…
1 voteThe product team will review this idea for consideration for a future release.
-
Allow for Diacritics in E-mail Receipts
We've been exploring new ways that our library, as an institution, can meet the evolving interests of DEI efforts. One very small but meaningful way we thought we might do this is to allow for the inclusion of diacritic characters in customer names in Sierra.
Their inclusion appears as desired on the customer record when created/displayed in Sierra (images dia1 - dia2).
They do not appear to impede searching for the customer by name - the search just ignores them (images dia3 - dia4).
They appear as desired in the name display in the Classic Catalog (image dia5).
They appear…
11 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add alt tags to improve accessibility
A lot of alt tags appear empty by default and other accessibility issues seem to be outstanding. These two are examples that cannot be corrected by admins.
Add relevant tags to improve the accessibility of the search results page briefcit.html. The search box form has no labels that can be read by screenreaders:
Element Location: #searcharg
<input type="text" name="searcharg" id="searcharg" size="30" onchange="return searchtoolSubmitAction()" maxlength="75" value="[search term]">
The search history select element has no accessible name:
Element Location: .navigationRow[align="center"]:nth-child(5) > form > select[name="HISTORY"][onchange="onSelectChange(this, '')"]
<select name="HISTORY" onchange="onSelectChange(this, '')">
4 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.
-
Increase minimum server account password length to 15 characters to meet PCI requirements
The automated tool employed by Clarivate support to update iii and iii-root passwords every 30 days has an 8 character limit, which falls short of PCI requirements (15 characters). The Sierra application server, which hosts the web page connecting to PayPal is in scope for PCI, and therefore login credentials that can edit that web page need passwords of 15 characters or more.
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Save Query As - Alphabetical by Query
When using Create Lists and using Retrieve Saved Query, you are able to sort the list in ascending order. When you go to Save As a query, it goes in and there doesn't appear to be any sort of order (in the past I swear it went in the order it was added/saved). So if you have to tweak your query and need to Save As again, good luck finding it, esp. when you have 100+ saved queries. Ideally you could sort the list of queries, like you can when you initially retrieve them.
3 votesThe product team will review this idea for consideration for a future release.
-
Make printer option defaults available by workflow, and have "send to email address" send only to staff email addresses
This is two fold. First, we would like to be able to set a default printer option determined by the staff users workflow (circulation workflow/function would default to "email to patron", and cataloging function would default to local printer, etc). So staff log in and select their function area and the system uses a specific printer default accordingly.
Secondly, we would like to have the "Send to email address" printer option changed somewhat. When selected, it would have a drop down of emails available to send to. These would be set up by the system admin. It would reduce the…
3 votesThe product team will review this idea for consideration for a future 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.
-
Disable Reprint bills button In Sierra
We can’t use this button because we don’t use print templates for our bills.
We would prefer them to look pretty with Print Templates instead of the plain text we currently have. To avoid staff confusion, it would be great if this we had the ability to disable/grey out this button.3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
New "Booked" status for items scheduled in the Booking Module
Idea: create a new status that references a scheduled booking for an item.
Value: Currently, Sierra does not change the status of an item that has a scheduled booking. When using the API to reflect the status of an item on a catalog, the item will show as status - (On Shelf) even though the item is not available because it has a scheduled booking for that time. This makes it seem as if the item can be scheduled for a specific time when it is already booked. When an item has a booking, changing the status to "Booked" when…
2 votesThe product team will review this idea for consideration for a future release.
-
Preferences font settings can affect catalog display
When you increase the font size to 20 for cataloging, it enlarges all the other information except the title line which remains the same. As a result, the title line appears smaller in comparison to the other information. It would be great is the title also displayed in the larger font.
13 votes -
Allow use of spine label print templates in Create Lists
Spine Label Queues are only available in the current session and do not save. We are able to print spine labels (sheet or continuous) from Create Lists, but cannot apply print templates with this function. Can we either have the option to apply print templates when wanting to print batches of labels via Create Lists and/or have the option to hold on to our spine label queues for more than just the current session?
21 votesSelected for the Sierra 6.7 release by MEEP enhancement process
-
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 -
Correct 0 date values in SQL views to NULL values
In circtrans and finespaid views (and maybe more views) there are several dates that are showing a value of 0 (which displays as 1969-12-31 due to UNIX date formatting).
Dates do not have a value of 0, they can however, have a value of NULL, which is already how things work with other dates in the system, like the bib record cataloguingdategmt.
This should be fixed for any dates in the system, not because anyone may or may not vote for it, but because it is both inaccurate and inconsistent.
I logged this as a ticket,…
14 votes -
Delete and modify identity providers during SAML configuration
It is better to provide the option to delete the identity providers and modify the name of the identity provider by the administrator during SAML configuration.
1 voteThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Alerts for when indexing stops
Currently there are no alerts when indexing stops working. We would like to see some put in place.
We recently had our keyword indexing stop working. It wasn't completely obvious to us for few months that there was a problem with indexing as it didn't seem to be every record.
Idea Value
Having an alert to III would save time troubleshooting if it's a metadata problem and raising tickets for something that could have an alert on it.37 votes
- Don't see your idea?