70 results found

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

   •  

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

   23 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

   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

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

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

   •  

   •  

   4 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 & 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. 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

   •  

   •  

   •  

   •  

   1 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

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

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

   •  

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

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

   1 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

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

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

    10 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

    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

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

    2 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  ·  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. Permit writing a pre-encrypted PIN via the API without additional encryption

    For testing purposes, it would be beneficial to be able to make a backup of a patron PIN, assign a new temporary PIN, perform the testing from the patron's perspective, and then restore the original PIN. This way we would not have to inconvenience the patron by asking them to reset their PIN when testing has completed.

    We can retrieve the encrypted PIN with this API GET request:
    https://library-app-server:443/iii/sierra-api/v6/patrons/patron-record-number?fields=varFields
    but the PIN string will be re-encrypted if we attempt to write it back using the patron record PUT request. We would like to have the option of passing a directive to the PUT request to bypass the encryption step, perhaps like so:
    https://library-app-server:443/iii/sierra-api/v6/patrons/patron-record-number?option=noencrypt

    We acknowledge that the ability to temporarily swap out a PIN using a UI such as the SDA would benefit more Sierra libraries as not all Sierra admins are comfortable working with the API. This enhancement request is intended to require less development effort than a new SDA feature and therefore improve its chances of being realized sooner.

    For testing purposes, it would be beneficial to be able to make a backup of a patron PIN, assign a new temporary PIN, perform the testing from the patron's perspective, and then restore the original PIN. This way we would not have to inconvenience the patron by asking them to reset their PIN when testing has completed.

    We can retrieve the encrypted PIN with this API GET request:
    https://library-app-server:443/iii/sierra-api/v6/patrons/patron-record-number?fields=varFields
    but the PIN string will be re-encrypted if we attempt to write it back using the patron record PUT request. We would like to have the option of passing a directive… more

    4 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 & 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. Abililty for Sierra's NCIP responder to be able to parse ISBNs

    Right now NCIP for Symphony, Voyager, Polaris, Koha and Evergreen all accept ISBNs, but Sierra's does not.

    6 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  ·  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. /v6/patrons/{id}/holds/requests/form API endpoint should accept item record numbers as parameters in addition to bib record numbers

    The form endpoint is used to identify cases in which a patron must place a volume level hold or is restricted to an item's home library as a pickup location. Both of those involve item level specifics and yet the endpoint only works with bib records. This is an issue in particular with multi-location libraries/consortia who use the home pickup feature.

    As an example, a sample bib record has two attached items, one which uses the home pickup feature such that it may only be picked up at library A, and one that does not restrict pickup locations so may be picked up at libraries A, B, or C. Because the endpoint returns valid pickup locations for title level holds, it will always return the full list of locations and there is not a way for the end user to know that one of the items may only be picked up at library A.

    Allowing the endpoint to provide item level details would resolve that, though it would also mean testing out individual item records in advance of actually placing holds in all cases in order to see if this restriction is in place...which I don't love. So I'm open to alternative suggestions to fix this feature but this seemed like the smallest ask to me.

    The form endpoint is used to identify cases in which a patron must place a volume level hold or is restricted to an item's home library as a pickup location. Both of those involve item level specifics and yet the endpoint only works with bib records. This is an issue in particular with multi-location libraries/consortia who use the home pickup feature.

    As an example, a sample bib record has two attached items, one which uses the home pickup feature such that it may only be picked up at library A, and one that does not restrict pickup locations so may… more

    6 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  ·  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

15. Create Granular Permissions for Editing Permissions for Select Group of Users

    We would like to see more granulated permissions for user administration, especially with assigned permissions, settings, options, workflows, etc.

    We would like the ability to assign a particular group of user accounts (e.g., circ student employees) to a specific admin (e.g., head of circulation) without assigning ALL system administration. It would be helpful for troubleshooting and having this department be able to assign macros, specific permissions, and print settings to different accounts.

    Ideally, this "group admin" would have the ability to edit settings on accounts for options, settings, and workflows. It would be great if they could clone and create a new account from within their group as well.

    I am thinking about Springshare's LibStaffer software and how the app's overall admins can be different than the individual schedule admin. That sort of granularity for user accounts here would be useful.

    This would enable us to allow our supervisors more ability to assist their employees when troubleshooting before forwarding it onto sys admins.

    We would like to see more granulated permissions for user administration, especially with assigned permissions, settings, options, workflows, etc.

    We would like the ability to assign a particular group of user accounts (e.g., circ student employees) to a specific admin (e.g., head of circulation) without assigning ALL system administration. It would be helpful for troubleshooting and having this department be able to assign macros, specific permissions, and print settings to different accounts.

    Ideally, this "group admin" would have the ability to edit settings on accounts for options, settings, and workflows. It would be great if they could clone and create… more

    9 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  ·  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. Clear and Set Permissions at one go

    We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope faster way to change the user. At this time you must first remove previous user (Admin - Clear Permissions) and then add new user (Admin - Set Permissions). Staff suggested one function that would both Clear previous and Set new Permissions. E.g. Set Permission could remove the old user and then ask the new user. We set up macros for both functions so staff can use them instead of drop-down menu. However, I suppose it’s not possible/recommended to create a macro to do both functions in succession.

    We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope faster way to change the user. At this time you must first remove previous user (Admin - Clear Permissions) and then add new user (Admin - Set Permissions). Staff suggested one function that would both Clear previous and Set new Permissions. E.g. Set Permission could remove the old user and then ask the new user. We set up macros for both functions so staff can use them instead of drop-down menu. However, I suppose… more

    3 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  ·  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. Login indicator

    We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope better indicator (e.g. color) so it would be easier to notice if personal login/permissions is added or not (or if someone has forgotten to remove their personal login/permissions). At this time when you open Sierra using the library login you can see "Sierra" and "local system name" on the upper left corner (in our case Sierra Helmet). When you add personal login your name (user account full name) will display too (in our case Sierra Helmet Firstname Lastname) but staff says it's not distinctive enough. Maybe the color of the text or the color of the upper bar could change when the personal login is added/removed.

    We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope better indicator (e.g. color) so it would be easier to notice if personal login/permissions is added or not (or if someone has forgotten to remove their personal login/permissions). At this time when you open Sierra using the library login you can see "Sierra" and "local system name" on the upper left corner (in our case Sierra Helmet). When you add personal login your name (user account full name) will display too (in our case… more

    1 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. Add filtering parameters to the GET /v6/bibs/search API

    Hello Everyone,

    We are currently using the GET /v6/bibs/search API to take advantage of the AWS search integration, which has been working well. However, we’ve encountered limitations in filtering the search results by Material Type, Collection, Language, and Location.

    It would be highly beneficial if this API supported additional filtering parameters to narrow down results at the source. Relying on the client or webhook server to apply these filters adds complexity and can introduce delays in presenting results to the end user.

    Thank you.

    2 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  ·  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

19. More universal accessibility features

    Improving universal accessibility features for users/employees with diverse accessibility needs.

    For example, for employees with visual impairments :
    - High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.

    Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.

    Even just the high contrast would help a lot. Additionally, it would be helpful if users could personalize their accessibility settings through their individual initials, without affecting the default settings for all users using the same login.

    Improving universal accessibility features for users/employees with diverse accessibility needs.

    For example, for employees with visual impairments :
    - High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.

    Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.

    Even just the high contrast would help a lot. Additionally, it would be helpful if users… more

    14 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  ·  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

20. Add API endpoint to update MARC Leader fields

    Our consortium would like an automated way to update the encoding level to help with managing load profiles that use the encoding level priority function. It would be very helpful to add an API endpoint for updating all the MARC Leader fields. The 008 MARC field can only be used for updating some of the Leader fields.

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