60 results found

1. Access to SAML logs

   When using the LDAP authentication option, it was useful to be able to see the authentication logs to diagnose login issues. After switching to SAML authentication, access to the SAML logs is only available to Innovative support.

   I propose granting customers access to the CAS Apereo application logs so that we can see SAML authentication issues. These logs may not be as detailed as the LDAP ones since the authentication is happening at the IdP but they might provide clues to further investigate authentication issues.

   1 vote

   Vote 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 & APIs  ·  Edit…  ·  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

2. Create user permissions/roles for limiting SierraDNA access

   We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.

   What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).

   Beyond the vendor scenario it would also be fantastic to provide limited access to more of our library staff. As a consortia, we have many of our member libraries who could truly benefit from being able to work with their record data but as long as doing so also provides access to things like staff account usernames and the limit network access table we can't open that access up to more of our own users.

   We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.

   What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).

   Beyond the vendor scenario it would also be fantastic to provide limited access to more of our… more

   2 votes

   Vote 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 & 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

3. Separate summary view property for each of the search functions

   This idea is essentially to address a design flaw that goes all the way back to the migration from Millennium to Sierra. The record view property setting was originally designed for the context of Millennium, where there would be entirely separate logins for circ, cataloging, acquisitions, etc...and adjusting the setting would only impact a single search function. But in Sierra when a single user may have multiple workflows available to them that breaks.

   When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open up the summary view of a record you see item records, in search/holds you see holds, in place orders you see orders and in serials checkin you see checkin records.

   If you opt to change that setting however from the record view properties menu (say to change this to view all) it can impact all 4 search functions. It would be better to split this menu out, so that the setting for each of the search functions can be selected individually.

   This idea is essentially to address a design flaw that goes all the way back to the migration from Millennium to Sierra. The record view property setting was originally designed for the context of Millennium, where there would be entirely separate logins for circ, cataloging, acquisitions, etc...and adjusting the setting would only impact a single search function. But in Sierra when a single user may have multiple workflows available to them that breaks.

   When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open… more

   2 votes

   Vote 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 & 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

4. Make Third Party API Transactions More Apparent in Sierra

   Some time ago, an idea was submitted to enhance the Sierra API to provide statistical group information, so that circulation transactions in third party applications could be credited to a statistical group other than 0 None.

   The idea won the "Let's Connect Sierra API Challenge."

   With the release of Sierra 6.0, it then became possible to include a new optional data parameter to specify the statistical group that should be used when recording a transaction performed using the APIs.

   My library was excited to hear this, as we'd recently begun using the self-checkout feature in the Bibliocommons' app not long before this & found it frustrating that credit for the transactions wasn't being assigned to a dedicated statistical group & just lumped into the default of 0 None. That Bibliocommons requires separate statistical groups for checkouts & renewals made it all the more frustrating.

   After some back & forth involving both Bibliocommons & III support & developers, we began seeing these transactions assigned the desired statistical group in Web Management Reports (see stat groups 908 & 909 in image bibstat1). This is enough to help those keeping track of metrics.

   However, this does not address the need of frontline staff who may need to see where an item was checked out. Normally, they'd do this in the SDA, by looking at the Checkout Location field in the item record.

   Unfortunately, this still displays the 0 None value (see image bibstat2).

   Apparently, this is because Bibliocommons does not currently support the username field in the API coding for their checkouts, which Sierra currently requires. In order for our library to take full advantage of our chosen app from its use to the resultant metrics, we're hoping that the stat group functionality could work without necessarily specifying the username.

   Some time ago, an idea was submitted to enhance the Sierra API to provide statistical group information, so that circulation transactions in third party applications could be credited to a statistical group other than 0 None.

   The idea won the "Let's Connect Sierra API Challenge."

   With the release of Sierra 6.0, it then became possible to include a new optional data parameter to specify the statistical group that should be used when recording a transaction performed using the APIs.

   My library was excited to hear this, as we'd recently begun using the self-checkout feature in the Bibliocommons' app not long… more

   •  

   •  

   2 votes

   Vote 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 & 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

5. include PostgreSQL scheduled patches and upgrades in roadmap and upgrade documents

   Sierra 6.6 includes an upgrade to PostgreSQL 16. Innovative should be more specific and tell us that we are upgrading to PostgreSQL 16.10. PostGres 16.14 was the last version in this cycle.

   Does Innovative upgrade PostgreSQL with each Sierra upgrade? Will they patch between upgrades with any security fixes?

   Libraries need to know Innovative's plans PostgreSQL development, and I am unsure if they are always included in the upgrade notes.

   4 votes

   Vote 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 & 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

6. SAML login page customization

   The SAML login page with the option to choose SAML or Library login is very basic and does not convey information to patrons concerning the choice. In addition, the customization have limited options and are only available to Innovative support.

   The proposed idea is to provide more customization options for this page and open these customizations to customers through a self-service feature. In addition to the current options available to Innovative such as logo changes and colors, the SAML login page should have options to add a block of text for instructions using HTML so that links could be included. Or at the very least, provide an option to link to another page (or popup) that provides additional login information.

   The SAML login page with the option to choose SAML or Library login is very basic and does not convey information to patrons concerning the choice. In addition, the customization have limited options and are only available to Innovative support.

   The proposed idea is to provide more customization options for this page and open these customizations to customers through a self-service feature. In addition to the current options available to Innovative such as logo changes and colors, the SAML login page should have options to add a block of text for instructions using HTML so that links could be included.… more

   1 vote

   Vote 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 & 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

7. Have CAS Apero metadata re-ingest automatically once the validUntil date is reached

   It would be useful to have CAS Apero enhanced to either:

   1. re-ingest the metadata automatically once the validUntil date is reached or

   2. have a setting to ignore the vaildUntil date.

   We are currently implementing OpenAthens which has a daily metadata refresh meaning the validUntil parameter is also changing daily.

   As Sierra cannot currently auto re-ingest metadata or be configured to ignore the validUntil parameter, we are currently hosting an edited metadata file on our web server (with a really long validUntil date) as a work around.

   1 vote

   Vote 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 & APIs  ·  Edit…  ·  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

8. Extract attached media files in bulk

   Create the ability to extract attached media files in bulk from Sierra.

   1 vote

   Vote 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 & 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

9. Add Days Closed Table to SierraDNA

   We are interested in being able to tap into the Days closed table programmatically but it is inaccessible to both the APIs and SQL, and doesn't even have a native export feature (though you can copy and paste it easily enough).

   Creating a SQL View for it seems the most straightforward solution, just provide access to the existing table, along with row numbers to preserve the ordering.

   12 votes

   Vote 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 & 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

10. Remove leading diacritic from normalised author fields

    Sierra currently removes any leading apostrophe for example from the normalised author fields on bibs. For example, normAuthor over API. Other diacritics such as ʻokina (ʻ) is not removed from normalised fields. Because of this, any systems that use norm fields over API are not alphabetising the author correctly.

    It would be great if Sierra could remove the ʻokina (ʻ) from the normalised author fields. Specifically normAuthor.

    2 votes

    Vote 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 & 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

11. Translate item status and OPAC message codes in Summary View

    Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.

    •  

    6 votes

    Vote 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 & 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

12. Provide full Branches table and full Location code list via Sierra REST API

    Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.

    Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the Branches table. Fiona (BiblioCommons) also confirmed the current Branches API is insufficient and has requested III improve it to return a full representation of the Branches table.

    Current behavior

    When calling:

    GET /v6/branches/?fields=%2C

    We receive only two branch entries and an API response showing:

    "total": 2 (implying only two branch records exist), even though our environment contains many more branch/location entries in the Branches table.

    The response includes a locations array, but only for locations linked to Branch Address table entries.

    Example (truncated):

    {
    "total": 2,
    "start": 0,
    "entries": [
    {
    "id": 1,
    "name": "Poudre River Public Library District",
    "locations": [
    { "code": "adult", "name": "Adult" },
    { "code": "afic", "name": "Adult - Fiction" },
    ...
    ]
    },
    {
    "id": 2,
    "name": "Interlibrary Loan"
    }
    ]
    }

    Desired behavior

    Provide a REST API mechanism to retrieve a complete, authoritative list of:

    All Branches table entries (not only Branch Address table entries that have names populated), and/or

    All location codes as defined in the Branches table, including their display names/labels and other relevant metadata used by integrations.

    Why this matters (impact and use cases)

    This enhancement would significantly improve Sierra interoperability with third-party vendor products and local applications by enabling real-time retrieval of location configuration data.

    Primary use case: Discovery layers

    BiblioCore, Aspen Discovery, and Vega Discover (and similar products) need accurate location codes and labels to support:

    facets and scoping

    branch/location-based availability display

    collection/location grouping rules

    pickup location logic

    suppression or “hidden” locations behavior where applicable

    Right now, when a library:

    adds a new location code,

    renames a location display label,

    retires/deprecates a location,

    …they typically must manually communicate those changes to the discovery vendor (often via spreadsheets/emails/tickets). That adds delay, introduces errors, and makes “near real-time” configuration synchronization impossible.

    Secondary use cases (beyond discovery)

    internal analytics/reporting tools that want to label circulation/hold data by location

    AMH/bin mapping, routing, or sorting optimization tooling

    self-check, RFID, or third-party circulation peripheral integrations

    custom staff apps and dashboards that need the live location dictionary for validation and display

    Proposed solution options

    Any one of these would solve the problem. More than one would be even better.

    Option A: Enhance /v6/branches to represent the full Branches table

    Return all branch/location records stored in the Branches table, not just those tied to Branch Address entries with names.

    Add a way to request “Branch Address fields” separately (since Branch Address and Branches table are distinct concepts in practice).

    Option B: Add a dedicated endpoint for locations

    For example:

    GET /v6/locations

    GET /v6/branches/locations

    Option C: Provide an “includeAll” style flag
    If III wants to preserve current default behavior, add something like:

    GET /v6/branches?includeAll=true

    GET /v6/branches?source=branchesTable vs source=branchAddressTable

    Improving access to the Branches table / locations dictionary via REST API would be a major interoperability win for Sierra. The main theme is discovery layer integration (BiblioCore, Aspen Discovery, Vega Discover), but the same capability would benefit many other integrations and local applications that need accurate, real-time location metadata.

    Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.

    Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the… more

    39 votes

    Vote 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

    4 comments  ·  System Administration & 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

13. Restart a Range of Terminals

    Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.

    Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a box next to listed sessions to restart several at once, but it's much easier to say, "Restart everything from line 30-142."

    Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.

    Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a… more

    •  

    •  

    23 votes

    Vote 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 & 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

14. Restart a Range of Sessions/Processes in Admin App

    Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.

    Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a box next to listed sessions to restart several at once, but it's much easier to say, "Restart everything from line 30-142."

    Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.

    Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a… more

    •  

    •  

    •  

    •  

    5 votes

    Vote 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 & 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

15. Add timestamp to "Suspended" field in user account

    Problem:

    Our practice is to suspend user accounts when a staff member leaves, rather than delete it, so that we can copy the necessary permissions when a replacement is hired. We then try to delete the accounts after 6 months, but there is currently no method within the Admin App or SQL that tells you when a login was suspended, so we have to track that manually.

    Value: adding a timestamp to this field would enable us to more seamlessly manage user accounts for our large consortia and ensure that unnecessary logins are periodically purged.

    10 votes

    Vote 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 & 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

16. Improving Hold Shelf Management in Sierra and IMMS

    We at the Libraries of Malmö would like to suggest that Innovative and Lyngsoe develop an interaction between Sierra and IMMS to help clear hold shelves.

    The issue: Currently, we have hold shelves at our libraries that are numbered between, for example 100 and 120. Each day we clear the holds that have expired the previous day. When we first implemented IMMS, we noted the shelf to clear down on a paper almanac and then wrote them off a week later.

    However, we have since then coded a very simple application to keep track of this for us. The application takes the holds that have expired the previous seven days (this is due to varying opening hours at our libraries), grabs the related barcodes from Sierra, and sends them to IMMS to retrieve the hold shelf. It then reports to the user, for example, “clear the shelves 101 and 103”.

    The application can also report the shelves used on a specific date, to help staff keep track of which shelf to use for new holds.

    Due to its simplicity, the app is prone to human error and not entirely reliable. For example, clearing the holds in Sierra will make it impossible to retrieve the shelves from IMMS, because the application uses the status ! in the item, which is cleared when the clear expired holds and hold shelves function is used. We feel that a better solution would be for Innovative and Lyngsoe to develop this functionality within the Sierra Library Management System.

    We at the Libraries of Malmö would like to suggest that Innovative and Lyngsoe develop an interaction between Sierra and IMMS to help clear hold shelves.

    The issue: Currently, we have hold shelves at our libraries that are numbered between, for example 100 and 120. Each day we clear the holds that have expired the previous day. When we first implemented IMMS, we noted the shelf to clear down on a paper almanac and then wrote them off a week later.

    However, we have since then coded a very simple application to keep track of this for us. The application… more

    •  

    14 votes

    Vote 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 & 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

17. Sierra API : add /users/groups/ endpoint to "GET number of users by group"

    It can be useful to check the number of users in each group currently logged in to Sierra. In our case, there is a self-checkout group that should have a specific number of logged-in users throughout the day that requires monitoring.

    The number of users in each group logged in to Sierra over the course of the day is available by SSH (in Admin Corner, "Number of INNOVATIVE users by hour").

    Monitoring this information in an automated way is not straightforward. Admin corner can send an email, but only from an interactive SSH session. It is possible to automate an SSH session with a script, but this is complicated. Right now, I have to manually login to Admin Corner and enter an obscure sequence of keystrokes to get this information and even then the data is only aggregated once per hour. Only staff with Admin Corner access are able to perform this monitoring, which takes time away from other duties.

    Enhancing the /users API to add a new endpoint (e.g., GET /users/groups/{group}) which returns the number of users by group would make monitoring user groups much easier. Indeed, it could make user groups more useful broadly speaking.

    In our case, polling such an API periodically would empower us to act when there are too few (or too many!) self-checkout users logged in. The same concept would apply to other user groups that merit monitoring for operational reasons.

    Alternatively, a built-in Sierra feature that sends a notification when the number of logged-in users per group is greater or less than arbitrarily defined values would be helpful for my specific use case.

    It can be useful to check the number of users in each group currently logged in to Sierra. In our case, there is a self-checkout group that should have a specific number of logged-in users throughout the day that requires monitoring.

    The number of users in each group logged in to Sierra over the course of the day is available by SSH (in Admin Corner, "Number of INNOVATIVE users by hour").

    Monitoring this information in an automated way is not straightforward. Admin corner can send an email, but only from an interactive SSH session. It is possible to automate an… more

    2 votes

    Vote 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  ·  0 comments  ·  System Administration & 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

18. Improve server security by supporting Apache module mod_security

    With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.

    4 votes

    Vote 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 & 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

19. Add an API endpoint which permits writing to review files

    Currently, when a query is beyond the capabilities of Create Lists, it is usually possible to use a SQL query with Python to produce a report. Such a report might list record numbers of bibs/items/orders/patrons/etc which bear further examination and correction by library staff, but staff must copy record numbers or barcodes in the report and paste them into the SDA to pull up the records in question. It would be much easier if an API endpoint permitted those record numbers to be written to a review file so staff can go through them one-by-one in the SDA.

    Another use case for such an endpoint would be the development of record import routines with features which do not exist in the current Create Lists record import facility.

    Currently, when a query is beyond the capabilities of Create Lists, it is usually possible to use a SQL query with Python to produce a report. Such a report might list record numbers of bibs/items/orders/patrons/etc which bear further examination and correction by library staff, but staff must copy record numbers or barcodes in the report and paste them into the SDA to pull up the records in question. It would be much easier if an API endpoint permitted those record numbers to be written to a review file so staff can go through them one-by-one in the SDA.

    Another use… more

    11 votes

    Vote 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

    2 comments  ·  System Administration & 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

20. RFID switching

    One of our branches uses shielded RFID pads, and the software could hook in to their previous ILS and context switch the current RFID action (tag on, tag off, no change) depending on the active function screen by overlaying a screen over the ILS to track the toggling.

    Can support for this functionality be offered for Sierra? I assume it would involve working with the RFID vendors to get it up and running.

    The current workaround is to use Sierra macros to trigger the RFID function change, but this is reliant on staff remembering to press the keys which may not always happen during busy periods at the desk. The macros also sometimes fail to trigger and it doesn't really work if staff use the 'check in' tab from the Check out function.

    We would love to see this as an efficiency improvement, given it was working on their previous ILS so moving to Sierra has been a step backwards in this area for them.

    One of our branches uses shielded RFID pads, and the software could hook in to their previous ILS and context switch the current RFID action (tag on, tag off, no change) depending on the active function screen by overlaying a screen over the ILS to track the toggling.

    Can support for this functionality be offered for Sierra? I assume it would involve working with the RFID vendors to get it up and running.

    The current workaround is to use Sierra macros to trigger the RFID function change, but this is reliant on staff remembering to press the keys which may… more

    3 votes

    Vote 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  ·  0 comments  ·  System Administration & 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