65 results found

1. 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 creating new review files, it's helpful to see, at a glance, how many files you have by increment/max records. For example, if I know I need 2 review files to be >100K records, I like to see how many are available in the various increments and delete unnecessary review files as needed in order to create 2 larger files.

   Currently, I have to sort by # in the SDA, while making changes in the admin app, save and then log out of the SDA, log back in and sort to see what is going to work. A big time waster.

   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… more

   21 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  System Administration (incl APIs)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   
   

2. 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 would cut down on confusion and staff time spent when reviewing the table. For example, when you look to see what the text of notices sent would be for specific loan rules, because the descriptions are so brief, you often have to click into the notice text and read it to confirm that it's the one that should be used.

   We waste a lot of time trying to describe key features/functions with these arbitrary limits.

   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… more

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration (incl APIs)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   
   

3. 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.

   13 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration (incl APIs)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   
   

4. 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 donor user.

   If we had a checkbox to alter this behavior, the recipient could retain all their old permissions while gaining the donor permissions. As the graphic suggests, the result would be an ORing of the two sets of permissions.

   This behavior should likewise extend to Applications, Workflows, Settings, Options and Preferences to the extent possible. Applications and Permissions are straightforward enough. Workflows involve an ordered display and for all I know conflicts may arise in Settings, Options and/or Preferences when combining two users in this way. My request of Mike and the product team is to implement that portion of this request which is readily doable and to not let the potential conflicts kill the whole idea.

   After voting (thanks in advance), please see my other opt-in Idea Lab entry.

   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… more

   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration (incl APIs)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   
   

5. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  3 comments  ·  System Administration (incl APIs)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating