241 results found
-
always be able to freeze a hold in catalogue(s)
Provide Libraries with the option to "always be able to freeze a bib or item level hold".
If circulation/OPAC rules allow a customer to place a hold, the customer should always be able to freeze it.
At this time, customers cannot freeze a bib level hold if there is an item attached to the bib that could fill the hold. Customers tell us that they want to manage their holds. They are unsure of a "Not Needed Before" date, but they know that they do not want to fill the hold immediately.
This is important for libraries that split out…
19 votesThe product manager will review this idea for possible inclusion in a future release.
-
Scan barcodes directly into Create List review file
The "import records" within Create List was a game changer. But going a step further would be adding the ability to direct scan barcodes into a review file. This would save time in circumstances where you have only a few records you need to update.
25 votesThe product manager will review this idea for possible inclusion in a future release.
-
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…
7 votesThis idea will be reviewed by the product management team for possible inclusion in 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…
3 votes -
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…
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Allow SIP2 AF field to offer alerting patrons to pending expiration.
That way other devices such as self checks can show that warning to the patron in the case of them checking out items and having the due date shortened to their expiration date instead of the full borrowing period for the item. If they were alerted they could contact staff to update their account and any item due dates that were shortened to their prior expiration date.
6 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
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.
25 votesThe product manager will review this idea for possible inclusion in a future release.
-
Limit Pickup Location Based on Item Type
We have three pickup locations: lockers, curbside and hold pickup shelves inside the library. For our Library of Things item type we would want to eliminate the lockers as an option because they cannot hold those items because of space.
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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…3 votes -
It's about time to make Holds APIs first-class citizens
Idea Description
It would be far nicer to have the ability to work with hold data directly--in contrast to having to retrieve hold data via the patron APIs. For example: currently, in order to (reasonably) find the "pickupByDate" values for holds with status "(Bib, Volume, Item) hold ready for pickup" you would have to use a combination of the Sierra SQL feature (to first find all the patron record numbers possessing such a hold) and then filter all the holds for the list of patrons (from the previous step) having the "pickupByDate" key in the response object. Once you have the holds,…12 votes -
Cascading Holds
Over a decade ago, III mentioned work being underway on "cascading holds" functionality. Meant for Millennium at the time, the feature seemed to disappear from their development plan due to staff transitions or some other reason, but I'd love to see it brought to fruition.
The feature would give patrons the ability to place a hold on a series (of books or a multi-disc DVD set) & receive the items sequentially), making the request process much more convenient for them & giving libraries the ability to more effectively manage hold fulfillment.
At the time, I was working in an environment…
20 votesThe product manager will review this idea 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, '')">
3 votes -
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.3 votes -
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.
19 votes -
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.
-
More name fields in get patron API
At present, we can only see the full name field in get patron endpoints. For some systems that connect via api, it would be highly beneficial to have other fields available relating to patron information. For example, separated first and last names.
This is due the some systems relying on the information it can read from Sierra and not process further to define a first name.
4 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Create a Review File endpoint
Idea Description
This idea is based in part on one submitted back in 2019 by Andy Helck. Create an endpoint that will provide the list of records included in a specified review file from Create Lists. I essentially envision this as the API version of the bool_set SQL table.Idea Value
This would provide outside systems the means of retrieving lists of titles that staff maintain within create lists and can provide a means for services to access data without having to work out how to create Json queries.11 votesThis idea has been accepted for inclusion in Sierra 6.3.
-
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.
7 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
15 votes -
Include zero results for selected locations in all reports in Decision Center
Currently Decision Center only returns data for a location parameter if there was activity for the selected time period and does not return a zero placeholder for locations without activity. This creates extra work for staff when working with the resulting Excel files. They can't easily reference the cells in Excel consistently.
13 votes
- Don't see your idea?