320 results found
-
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 votesThe product team will review this idea for consideration for a future release.
-
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.
-
Limit Ability to Clear Expired Holds & Holdshelf
So as we've seen repeatedly despite training & periodic reminders to exercise caution, the putrid corpse of liberty can really do a number on the Clear Holdshelf Report. We see disturbingly frequent scenarios where someone at one of our locations is not careful & winds up wiping out the holdshelf report for all 40 other branches. While we're fortunate to have someone here who has created a sort of recovery tool, we'd like to see the potential for such chaos somehow eliminated.
17 votes -
Sorting Search/Holds Queries
Staff would like to see the ability to sort results retrieved from queries performed in Sierra's Search/Holds mode.
Say for example they do a keyword search for Star Wars at our Forest Park branch. 124 items are found. The results are displayed alphabetically by default. But if the staff member wants to quickly sort by DVDs, they can't even click on the Format column heading, as it exists currently.
While they can run multiple limits to narrow down the results by format, language, shelving location, publication date, etc., they might just as equally be inclined to SORT the entire list…
8 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
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.
-
Customising pop ups
It would be nice to have more control over Sierra pop ups. Like if you are checking in a large amount of items it is really annoying to click ok every time the item is set in transit - you most likely already know these items are going in transit!
Also when creating a library card it would be good to be able to set a pop up "are you sure you wish to save a library card without (for ex) PIN code"? Sometimes you don't need that, but that is really rare.
8 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Protect local-only MARC fields that have a specific subfield coding
There are instances where its appropriate to put in a MARC field in the bibliographic record that only pertains to your local institution and you wouldn't want that field erased if the record was overlaid. If that MARC field was designated a local-note, using a $5 then that field would be "protected".
11 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Eliminate the two-tiered (context) logins that identify branch locations and personalized user
Several years ago we adopted context logins. We have established that a 1 tier login will not work for us.
CURRENT STATE : Our Regional Library consists of 39 branches in almost as many cities. To distinguish the branch of our Sierra users we currently use a two-tiered login. This login process allows us to continue to use generic branch accounts while meeting our obligations to protect customer information. The two-tiered login allows us to collect branch-specific data and apply unique user settings, options, and settings.
The drawback is that our staff must login twice and it may pose an…
8 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add a shortcut to print out patron barcode
When staff opens a patron's record, add a shortcut feature that allows them to print out patron barcodes. This will really help when someone comes in and don't have their library card with them, so wants to get their barcode information
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
-
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 -
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.
-
Allow patron to set thaw date of frozen holds
Allow patrons to set a thaw date when freezing holds. Patrons often forget they froze holds and the hold lingers until it expires. Also, make this information available in the API for third party vendors, such as discovery layers.
28 votesThe product manager will review this idea for possible inclusion in 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.
21 votes -
Re-page for item if pickup location has changed
Currently once an item is placed on hold, if the patron changes the pickup location after the item has already been paged for, the item will not be paged for again. With Title Priority Paging and “Prioritizing Hold Fulfillment at the Pickup Location” settings in place, this means a patron could be waiting much longer (depending on the “Pageslips: Number of hours before page can be transferred”) for their hold, even though they have fixed their mistake and reselected their intended pickup location. Additionally, even if the old pickup location pulls the item, they won’t be able to fulfill the…
17 votes -
Allow self-check out of virtual items using Sierra API
Update the Sierra API to allow self-check out of virtual items. We use Bibliocommons app and our customers cannot use the self-checkout feature to check out INN-Reach items.
5 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Separate summary view property for each of the search functions
When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open up the summary view of a record you see item records, in search/holds you see holds, in place orders you see orders and in serials checkin you see checkin records.
If you opt to change that setting however from the record view properties menu (say to change this to view all) it can impact all 4 search functions. It would be better to split this menu out, so that the setting for each…
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Penalty points for patrons who reserve books and then don't pick them up at the library
Currently, on Sierra it is possible to block patrons based on overdue penalty points (OD PENALTY) when they check in or renew overdue items. This is done with the patron fixed field OD PENALTY. The system calculates the penalty points that have to be added to the patron record and when a patron exceeds the maximum number of penalty points allowed by the library, the patron is blocked. More info at https://documentation.iii.com/sierrahelp/Default.htm#sgcir/sgcir_fine_penaltypoints.html
THis feature is very useful. Wouldn't it be a good idea to be able to apply a similar strategy for patrons that request a hold on a bib/item…
10 votesThis idea is planned for Sierra 6.5.
-
Add the ability to require fixed-length fields, not just variable length fields
We require certain information to create a library card, however Sierra does not enforce this requirement at the system level. Since it isn't mandatory, some data simply never gets captured and creates more work on the backend.
Beyond that, having certain information in the record would allow us to build a better understanding of our usership so that we can make better decisions as an organization.
I especially would love the ability to require any and all of the fixed-length fields; especially patron category, birthdate, home library, and notice preference.
16 votes
- Don't see your idea?