72 results found
-
Implement SAML SSO for Circa
Circa is a web application running on the main Sierra's webserver and is available from anywhere that https is available, yet it still only supports legacy Sierra only staff accounts and not SSO via SAML. Changing all staff login functions to require SSO and disabling legacy Sierra only account support is an important step towards Sierra being a secure ILS at the enterprise level. Not supporting SSO creates extra burden on staff by requiring another password, removing the ability to enforce strong authentication, and adds extra account support costs for a busy and non-technical team.
2 votesCirca has been replaced with Mobile Worklists and is no longer receiving enhancements.
-
Module data on the library catalogue (Online Reading List)
We are using Talis Aspire as our Online Reading List.
We are looking for ways to synchronise module code and module name data from Talis Aspire with our library catalogue so that we can easily identify whether a book on our catalogue is on a reading list.
Attached please find the example that captured from other library.
May I know if there are any updates ? I had submitted the same request last year.
2 votesProduct Management has reviewed this request and determined that this idea is too narrowly focused to be included in the product roadmap.
-
Elevated credentials do not work in Data Exchange
If a computer is logged into the SDA with a set of credentials that do not allow access to Data Exchange, the system prompts the user to login with appropriate credentials. When the user logs in with the elevated credentials, the SDA does not function properly. The Data Exchange dropdown list is unavailable for the newly elevated user. The user has to completely log out of the SDA in order for Data Exchange to work. I believe this is a bug in the system. If elevated credentials are prompted, then the functionality should work after the login. Otherwise, do not…
2 votesI'm closing this in Idea Exchange since it sounds like a bug and should be investigated by our Support team.
-
Superuser account with access to all accounting units from one log in?
Could we have an enhancement option to create a Sierra user administrator account that has access to all accounting units? I am the only system administrator and cataloger for a library system with multiple accounting units and I would very much appreciate the ability to do everything I need to from one log-in (managing/creating new check-in records, for example).
10 votesThis idea is no longer under consideration because implementing it would require significant changes to accounting units in Sierra.
-
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…
23 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.
-
REST API security enhancement request: Assign granularity to API role permissions
Objective: Allow Libraries to assign granularity to API role permissions.
When Libraries give a 3rd party vendor read access, we want to be able to restrict the endpoints associated with the role. In addition, we want to restrict the fields that can be returned. Ideally, the implementation of the requested features below will provide an interface to the Innovative clients where the vendor access will be managed.
There are endpoint and field restriction examples below to show how assigning granularity to API role permissions would allow libraries to improve access management.
Endpoint restriction example:
We would like to be able…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.
-
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.
32 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.
-
Decision Center: Pooling Report not based on demand
The Pooling Report generates a list of titles where "the pooling branch has more copies than it needs to meet 150% of demand". This is not the only reason that multi-branch libraries with floating collections have pooling collections.
Items in a floating collection can be returned to any location.
Could we have a pooling report that identifies:
1) Titles that have never been assigned or checked out at the location of the drought location
AND/OR
2) Titles not held at the drought location
Thank you,
Elizabeth2 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.
-
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 votesThis idea is no longer under consideration because it would require significant changes to the holds logic in Sierra.
-
Customize default item view based on function
It is currently an option to be able to set the default view of an item record across Sierra. However, it would be nice to be able to have a different default view set for the different functions in Sierra.
For example:
When in the Circulation function - I'd prefer the default view to be Hold.
When in the Cataloging function - I'd prefer the default view to be Item.
When in the Acquisitions function - I'd prefer the default view to be Order.I understand that I could just have multiple windows open and set the default view differently…
22 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.
-
Restrict Location Code Edits to Locations in Scope (especially in Rapid Update)
There is currently a setting allowing us to prevent logins from editing records with a location code outside of their current scope. However, users are able to edit records in their scope to have location codes outside of their scope, which then blocks them from being able to edit the records again. This happens accidentally sometimes, and is particularly a problem in Rapid Update. It would be great if item location dropdowns in Rapid Update, and possibly the item record as well, only showed locations in the user's scope in order to prevent this problem. Alternately, the system could prevent…
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.
-
Granular Permissions on Item Record
We would like to see more specific permissions on items records to allow staff who don't have access to edit entire item records to be able to do basic things like add and delete item messages or change the status of the item.
Frontline staff are discovering outdated item messages or finding that items are missing, and it's inefficient for them to have to contact someone else to change the status of the item, or delete an item message attached to it.
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.
-
Add ability to add/store PDF documents in patron records
I know that there is a product called External Patron Images that would allow patron photos to display in their records. I am wondering if a similar product exists for documents (such as PDF)? For some of our lending items, patrons must sign a user waiver to agree to the terms and conditions, and we currently have a two step process to verify if this has happened each time they come in. It would be good to be able to add the scanned image of the waiver to a patron record for easier verification.
7 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 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 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.
-
"Both" Option for Due Slip Delivery
The first request we got after releasing emailed Due Slips was for the option to generate both an email and a print slip. Some people like the physical reminder in the form of a printed slip (that doubles as a bookmark!) and an electronic version that they can use as a reminder or a fallback.
19 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 Global Update of Fund Codes
Allow for Global Update of fund codes. I work in an academic library and will often get purchase lists from our liaison librarians for a specific department. The records are brought in and the attached order records are edited in GU with the correct vendor, and selector, etc. It would be a time-saver if I could also update the fund code (which are tied to academic departments) at the same time.
16 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 sorting options for API Results
An example of this is the Items/GET API appears to sort the results based on catalog date/item id of the item. It would be nice to specify a different sort parameter that would allow the current sort or a new sort which would return them in the same sorting specified in the Cataloging function in Sierra.
This might be nice for other APIs as well.
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.
-
Insert name, date of birth and address using an ID scanner
I am wondering if Sierra can be adapted to automatically insert name, date of birth and address using an id scanner, such as those used at grocery stores when verifying a person's age. This would save staff the time of manually entering this information into the appropriate fields. It would also allow less typos and/or other mistakes when inputting the information. Of course, having the manual option would still be necessary.
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.
-
Check out circulation desk - add filter for home library or statistical group
We have a large consortia set up. Many clients are not required to bring their library card to the library circulation desk/s. When the library staff are searching for patrons with common surnames, quickly identifying their branch's patrons can be difficult - staff suggest adding a filter for home library or limiting the browse to their statistical group in their logins will limit the number of mistaken attempts to open the incorrect borrower record.
7 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 an additional multi-character fixed-length field for patron records
Add an additional multi-character fixed-length field for patron records
Our library would like to be able to track the branch at which a library card was issued separately from a patron's home library/preferred pickup location. Currently, we only have the "home library" field to store this information.
There isn't an available fixed-length field for us to adapt for this purpose, and we expect a variable-length field will be prone to too many variations, typos, etc. over time to be reliable.
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.
- Don't see your idea?