250 results found
-
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Support SFTP for WebPAC file upload
Organizations with restrictive security policies may be unable to use FTP over port 1021 (or any other port) for file transfer to Sierra WebPAC, since FTP is an inherently insecure protocol. For the same reasons, FTP should ideally not be in use at all (even where permitted by the customer's organization) since it entails sending login credentials in cleartext which makes it subject to interception and abuse.[1]
Without FTP, the only alternative is to use Web Master within Sierra Desktop App to upload files to make changes to Live or Staging WebPAC screens.
If Innovative implements Secure File Transfer Protocol…
6 votesThe product team will review this idea for consideration for a future release.
-
Connect Global Update with Scheduler
We complete many repetitive tasks in cataloging and patron record management each day. This entails using Create Lists to generate the list, and then using Global Update to perform the same set of edits each time. We need Scheduler to be able to connect into Global Update to perform those tasks automatically.
This may require enhancement of Global Update to save the Command Input, or it might mean adding the Command Input choices to Scheduler.
Example:
Scheduler runs an updated Create List using a saved search query to identify items that need their suppression code updated.
It then uses a…26 votes -
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.
-
Show recall info in Manage Holds
When using Manage Holds, information about any recalls that have been issued for items on hold is not displayed.
This information can be found by consulting the item record (right click, "Edit item", then open the item) and checking for a "Recall Date" value, but it would be very helpful for us if this information could be included directly in the Manage Holds results. For example, the "Hold Status" column could include indication of recalls to provide a fuller picture of the situation at a glance.
This idea could be incorporated in work on the following related suggestion:
https://ideas.iii.com/forums/951745-ils-sierra/suggestions/48633872-improve-standardize-information-available-when-vie4 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.
-
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?
8 votes -
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.
-
Add "last status update" to low & high circulation weeding report results
A "last status update" column in the low & high circulation weeding report results would help identify items for weeding or stock rotation.
Why would this field help us weed or identify items for stock rotation?
This item field identifies the last date an item changed their status. Many libraries change an item's status to "in transit" when they move an item from one branch to another. To that end, this field could help identify items that have either newly been received to a branch, or have sat on the shelf for some time.Items moving around systems with stock…
1 voteThe 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.
-
Save title and author info in reading history after title is deleted
Customers want to know what titles they've checked out even if the library no longer has it. It would be ideal if Sierra (and subsequent discovery layers can pull the info) could save the title and author in the record metadata so that even if the bib record is deleted, the customer can see it.
28 votes -
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.
- Don't see your idea?