21 results found
-
Connect Global Update with Scheduler
We complete many repetitive tasks in cataloging and patron record management each day. This entails using Create Lists to generate the list, and then using Global Update to perform the same set of edits each time. We need Scheduler to be able to connect into Global Update to perform those tasks automatically.
This may require enhancement of Global Update to save the Command Input, or it might mean adding the Command Input choices to Scheduler.
Example:
Scheduler runs an updated Create List using a saved search query to identify items that need their suppression code updated.
It then uses a…3 votes -
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.
1 vote -
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.
2 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.
4 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…
2 votes -
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).
6 votesThe product manager will review this idea for possible inclusion in a future release.
-
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…3 votesThe product manager will review this idea for possible inclusion in a future release.
-
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.
8 votesThe product manager will review this idea for possible inclusion in a future 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.9 votes -
Sierra 6.1 - Sierra Admin - Allow Export of Permissions
Provide system administrators the ability to export a user's permissions - both assigned and available. I am trying to provide an employee's manager with a list of the permissions her employee has, so she can see what should be added. There is no easy way to do this. I can't even copy/paste; when you highlight the permissions it just allows you to move them around vs. copying.
6 votesExporting a table of user permissions for one or more users is a feature in development for Sierra 6.1. Here is a link to the feature on the Sierra product roadmap: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/338-export-a-table-of-user-permissions
-
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.
3 votes -
Make API loader allow bad MARC
One of the major advantages of Sierra is it's flexibility. Particularly the Sierra fixed fields. Sierra allows those fixed fields to be used in non-standard ways, but the API loader does not have that flexibility. If you try to load records with unexpected data with the API, the load will fail. The API MARC loader does not have to validate MARC. Sierra has never really validated MARC. Don't start now. The API should allow the same weird non-standard data as the rest of Sierra.
5 votesThe product manager will review this idea for possible inclusion in a future release.
-
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,…
9 votes -
Manage Reading History through RESTAPI
Currently patrons can opt in and out of Reading History our public catalog (Bibliocore) but we get many requests from patrons who want to manage that reading history by removing items from Reading History but the RESTAPI doesn't allow users to do that, they have to log into their accounts on WebPac in order to manage the titles in that history. We would like to see full Reading History management currently available in WebPac added to the RESTAPI.
6 votes -
Admin App - Edit Username
Once a user is created in the admin app, you are not able to update the username. You may update the password, permissions, etc., but not the username itself.
All of our clerk-level positions are part-time, so there is a lot of turnover. Each time an employee leaves, his/her account must be deleted and a new one created for the replacement. When the new account is created, you then must import all of the permissions, options, locations served, etc., of a comparable employee for the same location.
Ideally, we would simply be able to edit the username and password and…
49 votesThis idea has been reviewed with Engineering and could be implemented as a medium-sized project. Product Management will keep this issue under consideration for a future release.
-
Make Review Files in Admin App Consistent w/SDA & Sierra Web
In Sierra - SDA and Web - you can sort review files in Create Lists by the column header, i.e., file #, current records, max records, type, status, login and created.
In the Admin App (BACK END MANAGEMENT > Review Files), the only columns displaying are file # (which doesn't appear to match the file # in the SDA/Sierra Web), number of records (= max records), current and name. Sorting by column is not an option.
The display, labeling and function for managing review files should be consistent.
Idea Value
When managing review files in the admin app, particularly when…18 votes -
Record Creation - Add "Back" option vs. just "Next" or "Cancel"
When you create (a) new item(s) while cataloging -- or create any records actually! -- the pop-up that guides you to enter the data step-by-step should have a back button. Currently, if you make a mistake and click Next you either have to cancel and start over or keep going and fix the mistake on each item record individually after saved/completed. It can be quite tedious when you are adding multiple items at once.
Idea Value
Save time! What would just take a few clicks/seconds to fix can sometimes mean a lot more time, especially if you Cancel and have…
50 votes -
Increase Character Limits for Data Fields
The Notice Type data field in the Text of Circulation Notices table is a mere 20 characters long. As we've had to create a number of new notices for temporary changes in operating hours, policies, etc., due to COVID, we'd like to make the description a bit more descriptive than 20 characters allows.
Also, because you cannot delete any of the old/test notice types, you already have to use up some of the characters to note that it's old/test/not used.
This runs along the same lines as Loan rules: increase the limit beyond 20 characters to loan rule names. This…
7 votes -
Upgrade OpenSSH version
Currently INN-Reach and Sierra servers are bundled with OpenSSH 7.1, which is over 7 years old as of this writing. There is a sorting bug (https://bugzilla.mindrot.org/show_bug.cgi?id=2694) that impacts the Scheduler functionality that would be fixed by upgrading to at least OpenSSH 7.6. Also assume that multiple security vulnerabilities exist in 7.1.
11 votes -
Make Sierra User Profile Imports Additive, at least Optionally
In the Sierra web-based admin utility, in Authorizations and Authentication Admin, when importing permissions from one Sierra user to another, the "donor" settings overwrite those of the recipient user. I propose adding a checkbox to allow these to be imported in an additive manner.
Idea Value
Recently two of my coworkers in Technical Services and Collection Development received promotions and shifted into different roles. When using the feature to assign the permissions of users similar to the new roles, old but still valid permissions were lost due to the way the feature overwrites the recipient permissions with those of the…32 votesThis idea has been reviewed with Engineering and could be implemented as a medium-sized project. Product Management will keep this issue under consideration for a future release.
- Don't see your idea?