72 results found

1. Create a GET API endpoint for circulation transactions

   This idea came from a discussion at the IUG2025 Sierra Reporting Forum.

   It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to have access to tables that should remain secured.

   This idea came from a discussion at the IUG2025 Sierra Reporting Forum.

   It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to… 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

   4 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

   The product team will review this idea for consideration for a future release.

2. Add a Stat Group When Creating a Patron API Key for Vendors

   This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or inflated statistics, which is particularly problematic when the library intends to track circulation usage via the API but cannot do so effectively.

   To expand tracking capabilities, it would also be beneficial to explore the feasibility of retroactively assigning a Stat Group to existing API keys. The implementation of this feature could leverage the workflow used for SIP2 license logins as a model for designing the Stat Group selection process when creating new API keys. Additionally, hold requests currently store the stat group within the body of the request rather than in the URL. Understanding this distinction may help in designing the stat group functionality for API keys in a way that aligns with existing data structures and workflows.

   The implementation of this proposal would provide several benefits. It would enable staff to categorize API keys by vendor, allowing more precise tracking and facilitating data collection and reporting using existing tools such as Web Management Reports and Decision Center. It would also improve visibility into vendor-specific API key usage, supporting data-driven decision-making and reducing reliance on stat group 0 as a catch-all category, ultimately leading to more accurate circulation statistics.

   This enhancement would streamline reporting efforts and provide better insights into vendor-specific API key usage, ultimately improving resource management and decision-making processes.

   This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or… more

   17 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

   4 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

   The product team will review this idea for consideration for a future release.

3. Create RestAPI with a Patron Validate role that updates the “last circ activity date” in patron record 

   Our library wants to provide the patron validate role to our vendors.
   But, we do not want to give the vendors any read or write roles.

   We do this now with several vendors, but the authentication does not update the "last circ activity" field in the patron record.

   Is it possible to add a new permission that would only allow authentication but update the "last circ activity" field in the patron record.

   Why add this feature?
   Our library purges patron that don't circulate for X number of years. We don't want to delete patrons that are actively using our eVendor content.
   We want to give our eVendors as little read/write permissions as possible.

   Thank you.

   Our library wants to provide the patron validate role to our vendors.
   But, we do not want to give the vendors any read or write roles.

   We do this now with several vendors, but the authentication does not update the "last circ activity" field in the patron record.

   Is it possible to add a new permission that would only allow authentication but update the "last circ activity" field in the patron record.

   Why add this feature?
   Our library purges patron that don't circulate for X number of years. We don't want to delete patrons that are actively using our eVendor… more

   15 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

4. Add ability to extend the hold Pickup By date to the /v6/patrons/holds/{holdId} API endpoint

   Currently the only hold parameters one can modify via the API are

   PatronHoldPut {
       pickupLocation (string, optional): the hold's pickup location code,
       freeze (boolean, optional): whether the hold should be frozen (suspended)
   }

   It would be very helpful if the Pickup By date – and while you're at it, the Hold Note – were added as modifiable parameters.  There have been many times when unscheduled branch closures or problems in sending hold pickup notices have caused us to want to extend hold Pickup By dates for items on the holdshelf.

   Having this functionality in an API endpoint would permit a programmatic solution for mass-extending Pickup By dates instead of the tedium of manually modifying each affected hold, which can and has taken me many hours to slog through.

   As for the Hold Note, I can't think of a particularly compelling application for that parameter addition right now, but I'm sure someone would benefit from that.  And like I said, while you're in the code adding the Pickup By date, why not add Hold Note too?

   Currently the only hold parameters one can modify via the API are

   PatronHoldPut {
       pickupLocation (string, optional): the hold's pickup location code,
       freeze (boolean, optional): whether the hold should be frozen (suspended)
   }

   It would be very helpful if the Pickup By date – and while you're at it, the Hold Note – were added as modifiable parameters.  There have been many times when unscheduled branch closures or problems in sending hold pickup notices have caused us to want to extend hold Pickup By dates for items on the holdshelf.

   Having this functionality in an API endpoint would permit a… 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

   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

5. Batch Check-In Should Not Update Circactive Date

   Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.

   We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.

   Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.

   This may apply to other batch, administrative tasks that are completed by the library and not the actual patron.

   Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.

   We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.

   Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.

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

   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
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   The product team will review this idea for consideration for a future release.

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

   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

   UNDER REVIEW  ·  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

7. Ability to view history for item and volume records.

   It would be helpful for us to have access to the history of item and volume records, including details of their creation and any subsequent edits. This would improve our ability to track changes and ensure accountability if any issues come up.

   16 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 (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

   The product team will review this idea for consideration for a future release.

8. 2038 issue

   We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.

   24 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

   6 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

   The product team will review this idea for consideration for a future release.

9. Insert/Update Location Codes from a CSV file

   Develop a utility to add new location codes to the so-called Branches table using a CSV file as input. Optionally permit updates (overlays) of existing location code entries so that the branch_code_num, name and/or is_public columns may be reassigned values in this way.

   Our library has very granular location codes which describe branch (or collection subset of a branch such as a display area), audience, format and genre, loosely speaking. This amounts to 220-250 location codes per branch (or collection subset). We currently have over 5,000 distinct location codes in our Sierra database, and every time a new branch is established or renamed, a lot of manual effort is required to add or update those location code entries one at a time.

   Using SQL to extract current location codes, and SQL, Excel or a text editor to perform string substitutions, a CSV file can be prepared fairly quickly. This utility would not have to be customer-facing; supplied with a CSV file uploaded as part of a Service Commitment, Support could run it. This would save development effort on a pretty user interface.

   Develop a utility to add new location codes to the so-called Branches table using a CSV file as input. Optionally permit updates (overlays) of existing location code entries so that the branch_code_num, name and/or is_public columns may be reassigned values in this way.

   Our library has very granular location codes which describe branch (or collection subset of a branch such as a display area), audience, format and genre, loosely speaking. This amounts to 220-250 location codes per branch (or collection subset). We currently have over 5,000 distinct location codes in our Sierra database, and every time a new branch is… 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

   UNDER REVIEW  ·  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

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

    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 (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

11. Automatic SSL Certificate Renewal

    Keeping our systems secure with SSL certificates is essential. Certificates need to be renewed and there is a service commitment to handle this process. But there is a better way. SSL providers can be setup to automatically renew and deliver an updated SSL certificate to our systems when their expiration time approaches.

    This idea is for Innovative to support software-only site with setting up an automatic SSL renewal process thereby keeping our systems safe from expiring certificates and making the process worry-free.

    11 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

    The product team will review this idea for consideration for a future release.

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

    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 (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

13. Make OpenAPI definition document (previously known as Swagger specification) available for Sierra's APIs

    There SHOULD be an OpenAPI definition document available for Sierra's APIs via Swagger, but currently, there is not.

    The OpenAPI definition document (https://swagger.io/specification/) is a standardized format for describing the structure and behavior of an API. It is a machine-readable document, usually written in JSON or YAML, that provides a comprehensive blueprint of an API's endpoints, operations, input/output parameters, response formats, authentication methods, and other essential details.

    For comparison, here is an example for the Polaris API / Swagger install (on an iii training server):
    https://polaris-training.polarislibrary.com/PAPIService/swagger/v1/swagger.json

    Benefits of an OpenAPI Definition Document:

    * Standardization: Provides a consistent format for describing APIs.
    * Documentation: Automatically generates interactive API documentation (e.g., Swagger UI).
    * Client Generation: Allows the generation of client libraries in various programming languages.
    * Validation: Ensures requests and responses conform to the defined schema.
    * Interoperability: Facilitates integration between different systems by providing a clear API contract.
    

    Access to this document is ESSENTIAL for development and integration purposes, especially when using tools like Python and other programming languages with the APIs.

    Having this document for Sierra would significantly enhance the development experience and improve integration capabilities, and should be considered essential.

    There SHOULD be an OpenAPI definition document available for Sierra's APIs via Swagger, but currently, there is not.

    The OpenAPI definition document (https://swagger.io/specification/) is a standardized format for describing the structure and behavior of an API. It is a machine-readable document, usually written in JSON or YAML, that provides a comprehensive blueprint of an API's endpoints, operations, input/output parameters, response formats, authentication methods, and other essential details.

    For comparison, here is an example for the Polaris API / Swagger install (on an iii training server):
    https://polaris-training.polarislibrary.com/PAPIService/swagger/v1/swagger.json

    Benefits of an OpenAPI Definition Document:

    * Standardization: Provides a consistent format

    … more

    •  

    30 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

    7 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

    The product team will review this idea for consideration for a future release.

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

    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

    UNDER REVIEW  ·  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

15. Add date/time stamp to the "Restart a process/terminal" display

    We'd like to see a date/time stamp on the "Restart a process/terminal" display in the Admin Corner and be able to sort by it. We sometimes run out of licenses because staff don't sign out of their SDA sessions at the end of their shifts, and we have to contact Innovative and request that connections older than the current day be closed. It would be helpful to be able to do this ourselves. Currently, we can preemptively reset all connections early in the morning before staff arrive, but if a problem arises during the day we don't want to cause further disruption by closing newer connections.

    We'd like to see a date/time stamp on the "Restart a process/terminal" display in the Admin Corner and be able to sort by it. We sometimes run out of licenses because staff don't sign out of their SDA sessions at the end of their shifts, and we have to contact Innovative and request that connections older than the current day be closed. It would be helpful to be able to do this ourselves. Currently, we can preemptively reset all connections early in the morning before staff arrive, but if a problem arises during the day we don't want to cause… more

    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 (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

    The product team will review this idea for consideration for a future release.

16. Limit access to Login Names & Parameters via permissions

    We'd like to be able to limit access to the Login Names & Parameters section of the Admin Corner (especially the Limit Network Access tables) via permissions. Certain functions, such as load tables, require certain staff members to have access to the Admin app, but having the login names and parameters unrestricted leaves an unnecessary hole in security. There are other functions in Admin Corner that require separate permissions and prompt users to enter their credentials, but not this one.

    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 (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

    The product team will review this idea for consideration for a future release.

17. Expand the 1,000 location code capacity of Locations Served (portloca) groups

    I currently have a need for a Locations Served group which can accommodate 1,245 location codes. The limit imposed by Admin Corner is 1,000 location codes, and per case #08077395, Support asserts that Sierra will not support more than 1,000 location codes per Locations Served (so it's not simply a limit of the Admin Corner interface).

    Increasing this limit will potentially lead to a modest increase in memory consumption by any and all circulation processes which hold these Locations Served tables in memory, but do we really need to be concerned about Kilobytes of RAM in 2025? Other Sierra configuration tables have had their capacity extended over the past several years, so precedent exists.

    For anyone about to pose the question, No, configuring it as a Locations NOT Served group of codes will not work in this case. Thanks anyway for the thought.

    I currently have a need for a Locations Served group which can accommodate 1,245 location codes. The limit imposed by Admin Corner is 1,000 location codes, and per case #08077395, Support asserts that Sierra will not support more than 1,000 location codes per Locations Served (so it's not simply a limit of the Admin Corner interface).

    Increasing this limit will potentially lead to a modest increase in memory consumption by any and all circulation processes which hold these Locations Served tables in memory, but do we really need to be concerned about Kilobytes of RAM in 2025? Other Sierra configuration… 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

    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
    PLANNED  ·  AdminMike Dicus (Product Manager, Innovative) responded

    This idea will be developed for Sierra 6.5.

18. Add a backdate option to the /v6/items/checkouts/{barcode} endpoint for checking in items

    I would like to add an optional parameter to the Sierra API endpoint for checking in items to allow for backdating those transactions as you can within in the client as it may help with automating some projects.

    For an immediate example, I have identified a number of items that were not removed from the checkout table correctly due to locked patron records, where the were placed in transit and I can see a time the checkout ought to have occurred via the in transit message. I would like to write a script to correct these failed checkins once they have been identified and ideally use the timestamps from those messages to make those corrections.

    I would like to add an optional parameter to the Sierra API endpoint for checking in items to allow for backdating those transactions as you can within in the client as it may help with automating some projects.

    For an immediate example, I have identified a number of items that were not removed from the checkout table correctly due to locked patron records, where the were placed in transit and I can see a time the checkout ought to have occurred via the in transit message. I would like to write a script to correct these failed checkins once they… 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

    UNDER REVIEW  ·  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

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

    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

    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

20. New Skins for Sierra

    Can we get some new skins to choose from for the SDA/Sierra Web?

    There are currently two: Half Dome & Glacier Point.

    We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.

    Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?

    •  

    22 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

    The product team will review this idea for consideration for a future release.