56 results found
-
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.
-
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.
-
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.
-
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.
-
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.
-
Dark contrast display option for the SDA
We see the Sierra 6.0 Release Notes features new Accessibility improvements in the SDA. It is unclear if this includes a high contrast display option which staff recommend to support use of the software by many different types of staff.
14 votes -
Allow the "remember me" in Sierra Desktop App login screen to remember passwords as well as username (as previous versions of Sierra did)
Previous versions of Sierra (version 5 and below) allowed the saving of usernames and passwords in the Sierra desktop app login screen. Since upgrading to 6 this functionally has been lost.
10 votes -
NCIP Authentication - Add support for optional blocking
We recently started using NCIP authentication for our new ILL service. We learned after implementation that NCIP login is blocked for any of the reasons in the Patron Block Table. This makes sense when the block is for an expired card, or for fees over the threshold. This makes less sense when they have reached their maximum holds in Sierra.
What we're seeing is that patrons cannot log into the system at all when any of the block parameters are true. We would like to be able to enforce certain blocks but not others for account login.
We can increase…
3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
MFT support in data exchange
Prior to Sierra 6.0 and the introduction of MFT, it was possible to use FTP to transfer files though data exchange within Sierra. This is no longer possible as MFT is not supported in data exchange.
Please add support for MFT in data exchange in the same way as support for MFT has been added in scheduler.11 votes -
Make the hold status information updatable in API
There is currently no way to update the status of a hold in the API.
It would be very useful to change the status from
"status": {
"code": "0",
"name": "on hold."
},to
"status": {
"code": "i",
"name": "Requested item ready for pickup."
},Enhancement to be integrated into https://ideas.iii.com/forums/951745-ils-sierra/suggestions/47618129-it-s-about-time-to-make-holds-apis-first-class-cit ?
4 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 -
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,…
13 votes -
assign 1st and 2nd tier timeout permissions (for those using context logins) : SDA and Sierra Web
In the SDA OR Sierra Web, the Sierra 2-tier login workflow allows administrators to set a "time-out" setting to the 2nd tier (personalized) login. This setting determines if the session will time out or close after a specific amount of time.
This is an excellent workflow except that there is no setting to manage 1st tier inactivity. This means at the end of the day we have many Sierra licenses that remain open and the Library must manually force close the desktop applications using the "restart a process" in Admin Corner.
Please configure context logins so that Libraries can determine…
4 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?