29 results found
-
NCIP activity should update Circactive
Currently, authentication using the NCIP protocol does not update the CIRCACTIVE attribute in the patron account. We use this protocol to authenticate to a statewide ILL service and we'd like to know when cards are being used in this union catalog and not just our own.
We use CIRCACTIVE to determine which cards are being used and which ones aren't. This is useful for statistical purposes, but is also linked to our patron database purge process.
8 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Require authentication to view Sierra API documentation
Enhance cybersecurity by not revealing the api methods through the swagger interface to unauthenticated users. For example, a potential hacker can view the swagger interface which shows all methods and explains how to use them. This is an issue on all api endpoints including the iii sandbox. My idea is to only reveal the swagger methods to authenticated users.
https://sandbox.iii.com/iii/sierra-api/swagger/index.html#!/patrons
6 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Ability to disable a user with one click in Admin Corner
The ability to log into admin corner, view all users and with one click disable them (not delete, but deny them log in access) would be helpful for those with revolving part time employees.
We have student employees that change out regularly, but sometimes they come back as graduate student help, etc within a short time.
Being able to simply turn off an employees access and review it within a year or less to determine if it should be deleted or held would be helpful for keeping our staff accounts cleaned up.
18 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Make OpenAPI definition document (previously known as Swagger specification) available for Sierra's APIs
There SHOULD be an OpenAPI definition document available for Sierra's APIs via Swagger, but currently, there is not.
The OpenAPI definition document (https://swagger.io/specification/) is a standardized format for describing the structure and behavior of an API. It is a machine-readable document, usually written in JSON or YAML, that provides a comprehensive blueprint of an API's endpoints, operations, input/output parameters, response formats, authentication methods, and other essential details.
For comparison, here is an example for the Polaris API / Swagger install (on an iii training server):
https://polaris-training.polarislibrary.com/PAPIService/swagger/v1/swagger.jsonBenefits of an OpenAPI Definition Document:
…* Standardization: Provides a consistent format30 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Sierra should send an email notification when Offline Files are Uploaded
As the system administrator overseeing a 54-member library consortium, managing Offline File Processing is a routine responsibility. However, we often encounter delays in processing files because libraries don't consistently notify us when they upload offline files. This results in files remaining unprocessed until the next library contacts us, potentially causing unnecessary checkout delays. If we process the files too many days after uploading, additional errors may occur, making it challenging to track items adequately.
An email notification for Offline File Processing would ensure timely handling of uploaded files. We could proactively monitor file uploads, swiftly process them, and promptly address…
18 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Release Item Price Field in Sierra Item Record for SIP2
Libraries using SIP2 connections for self-checks cannot have due slips that have "You Saved" information because the Item Price field is not available via SIP2.
While due slips with this information can be used at a staff station with the SDA, as more and more libraries move to self-check, the lack of this field's availability in SIP2 is a barrier.
Use case: a library has a self-check machine that uses SIP2 and wants to include "You Saved" information on their due slips.
12 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Staff activity log
We occasionally have issues with staff abusing their ability to waive fines or deleting items inappropriately or accessing patron accounts outside of acceptable library operations. We would like to have a way to view these actions within a log file associated with each Sierra login (or filterable by login) so that these activities could be periodically audited by managerial staff and retroactively be reviewed when inappropriate system activities are believed to have taken place.
29 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 voteIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
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 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Add a Note Field in the RFID Pad Server Options Table
As ILS administrators of a large consortium, we would like the RFID Server Options Table to have an additional field/column to add notes (library name, dates, staff initials). When one of our member libraries needs to change RFID entries, we sort through nearly 200 lines to determine which one needs updating. Many entries use IPs without identifying library information. We must read through old library correspondence to discern which IPs belong to the library. This task takes up valuable time when we are trying to assist a library with troubleshooting or adding and removing entries.
An additional free-text field to…
15 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Ability to change password on login page of SDA
Many libraries are creating individual logins for each staff member. Staff needs the ability to change their password in case they forget it. At this point, they need to be logged into the SDA to change their password which doesn't help if they can't remember it.
18 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
- Don't see your idea?