165 results found

1. Reinstate Manual Charge

   We would like to be able to reinstate manual charges, whether they're for the collection agency fee, or something like a damaged container or replacement power cable. The reason why we cannot currently reinstate this particular charge type is not stated in documentation & while I may have known at one point, memory fades as we age. Being able to simply reinstate a manual charge would simplify & expedite workflows, whereas now, we have to make like Hall & Oates.

   •  

   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  ·  Circulation, Access Services & Fulfillment  ·  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. Improve/Standardize Information Available When Viewing Holds

   Library staff would like to be able to see more details on holds that have been placed, including how the hold was placed (Sierra Desktop vs. SierraWeb vs. Web vs. mobile app, etc.) and who placed the hold (Sierra login if not the patron).

   Right now, it is not consistent how holds information is displayed.

   If you view holds w/in a patron record (holds tab), you don't see when the hold was placed or how they placed it. However, if you View Cancelled Holds, you see the date/time it was placed, along with the date/time it was cancelled, along with the title, barcode and importantly for staff, what login and program was used to cancel the hold.

   If you go outside of the patron record and go view the Bib and view the holds, you DO see the date/time it was placed. However, you don't see how it was placed or by whom. This is information that would be helpful, when there are questions about a hold.

   Ideally the information you'd see about a hold would be consistent no matter how you're viewing it - from the bib level hold, item-level hold or in the patron record /holds.

   I supposed this could also fall under "Customer Relationship & Account Management."

   Library staff would like to be able to see more details on holds that have been placed, including how the hold was placed (Sierra Desktop vs. SierraWeb vs. Web vs. mobile app, etc.) and who placed the hold (Sierra login if not the patron).

   Right now, it is not consistent how holds information is displayed.

   If you view holds w/in a patron record (holds tab), you don't see when the hold was placed or how they placed it. However, if you View Cancelled Holds, you see the date/time it was placed, along with the date/time it was cancelled, along with… more

   40 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

   8 comments  ·  Circulation, Access Services & Fulfillment  ·  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. Revamp the Hours Open Parameter

   The Situation: Our library's room checkout suddenly shorted to a hard limit of 6:00pm. I discovered that last year's spring break hours were listed in the Hours Open table and last year spring break occurred earlier in March.

   The Problem: Entries in the Hours Open table do not include the year. If the year was included, hour checkout issue wouldn't have been an issue.

   Solution #1: Add the ability to include the year to Hours Open table. Default to the current year but have the ability to change the year.

   Solution #2: Revamp the Hours Open table. Modifying the Hours Open using a table is antiquated. Reprogram the option to include a graphical date picker. Include repeat options like: every Wednesday, the first of the month, monthly, yearly, etc.

   The Situation: Our library's room checkout suddenly shorted to a hard limit of 6:00pm. I discovered that last year's spring break hours were listed in the Hours Open table and last year spring break occurred earlier in March.

   The Problem: Entries in the Hours Open table do not include the year. If the year was included, hour checkout issue wouldn't have been an issue.

   Solution #1: Add the ability to include the year to Hours Open table. Default to the current year but have the ability to change the year.

   Solution #2: Revamp the Hours Open table. Modifying the Hours… more

   9 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  ·  Circulation, Access Services & Fulfillment  ·  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.

4. Ability to alter the Recommends Approval and Denial emails that go to patrons who submit a purchase request

   Problem: The text of emails sent when using the Approval and Denial notifications in Recommends cannot be currently altered. We would like to be able to provide more customer friendly email templates to patrons that allow us to explain why an item was denied or what the process is for items that are approved.

   Impact: Being able to communicate with our patrons at the outset of the process will save staff time by not having to have go back and forth with customers over email to explain processes and reasons for purchase requests. Additionally it will improve the customer's experience with the suggest a purchase process.

   Problem: The text of emails sent when using the Approval and Denial notifications in Recommends cannot be currently altered. We would like to be able to provide more customer friendly email templates to patrons that allow us to explain why an item was denied or what the process is for items that are approved.

   Impact: Being able to communicate with our patrons at the outset of the process will save staff time by not having to have go back and forth with customers over email to explain processes and reasons for purchase requests. Additionally it will improve the customer's experience… more

   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  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

5. Add eReceipts as an option in LX Starter.

   The only option for eReceipts is plain text. It would be a fantastic feature to customers to be able to build a nice HTML email for them.

   9 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  ·  1 comment  ·  Circulation, Access Services & Fulfillment  ·  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. Statistics - Saved Queries Should Retain Cross-Tab Selections

   Saved Queries in the SDA should function the same as they do in SierraWeb.

   In the SDA:

   If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on the same record type, then the selection of the two fields in the Cross-Tab Field Selection panel will be retained when switching to another bibliographic review file in Sierra SDA.

   If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on a different record type (e.g. item record), then the selection of the two fields in the Cross-Tab Field Selection panel won't be retained when switching to another item review file in Sierra SDA. Very frustrating. Have to remember the criteria you used and toggle to those 2 inputs again.

   SierraWeb:

   However, in Sierra Web, the selection of the two fields is always retained, regardless of the first record type.

   Saved Queries in the SDA should function the same as they do in SierraWeb.

   In the SDA:

   If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on the same record type, then the selection of the two fields in the Cross-Tab Field Selection panel will be retained when switching to another bibliographic review file in Sierra SDA.

   If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record),… 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

   UNDER REVIEW  ·  0 comments  ·  Reporting & Analytics  ·  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. Lock Commands in Rapid Update

   When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands in place, this would prevent staff from inadvertently inputting additional commands and prevent the errors that occur.

   This enhancement would help eliminate unnecessary errors using the Rapid Update Individual Items function. It would save the time and frustration of having to backtrack and fix errors that may occur due to an incorrect command being entered by accident. It would also ensure that items retain valuable information, such as Itypes, which directly affect circulation.

   When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands… more

   13 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  ·  Cataloging & Metadata Management  ·  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. System Option to Disable Transit Slip Printing by Default

   In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.

   Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of paper for us. We'd like to have a system option to NOT print a transit slip by default so staff can page through multiple pop-ups efficiently. Ideally, this option would be controllable by the library in case we need to temporarily re-enable transit slips, e.g. if the sorter goes down.

   In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.

   Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of… more

   16 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  ·  Circulation, Access Services & Fulfillment  ·  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. Increase Max System Display Limit for Fines

   Our library has very generous allowances for both checkouts & holds on patron accounts. This can sometimes come into conflict with Sierra's seemingly arbitrary system limits. For example, when these items go unreturned & result in replacement charges, which then cannot be added because of the imposed limits. Like my waist can no longer accommodate 32" pants, Sierra cannot currently accommodate the lending policies taken advantage of by some of our more active borrowers.

   I'm sure there are other examples where these limits can manifest, but attached is an example message recently seen by staff which reads:

   CANNOT ADD FINE TO RECORD. SYSTEM MAX EXCEEDED. WAIVE CHARGE?

   We don't want staff forced into waiving a legitimate charge, but have no choice with these limits, so we'd like to see them increased or eliminated.

   Our library has very generous allowances for both checkouts & holds on patron accounts. This can sometimes come into conflict with Sierra's seemingly arbitrary system limits. For example, when these items go unreturned & result in replacement charges, which then cannot be added because of the imposed limits. Like my waist can no longer accommodate 32" pants, Sierra cannot currently accommodate the lending policies taken advantage of by some of our more active borrowers.

   I'm sure there are other examples where these limits can manifest, but attached is an example message recently seen by staff which reads:

   CANNOT ADD FINE… more

   •  

   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

   UNDER REVIEW  ·  0 comments  ·  Circulation, Access Services & Fulfillment  ·  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. 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

11. Make the "New PINs do not match" message configurable in PIN reset flow

    In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.

    This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.

    Suggested improvement:
    Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQPINSDONTMATCH key to also apply in the reset flow.

    This change would improve internationalization, accessibility, and consistency for all users, particularly in multilingual environments.

    In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.

    This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.

    Suggested improvement:
    Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQ… 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

    UNDER REVIEW  ·  1 comment  ·  Discovery & OPAC  ·  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. Hold Pickup Reminder/Courtesy Notice

    Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.

    Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want the item or aren't able to pick it up in time, they can inform the library. Then the item can move on its way and space can be created for other holds without the item lingering until the pickup by date. It also enhances the patron's experience because it prompts patrons again about their holds, which they may have forgotten about since receiving the first notice.

    Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.

    Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want… more

    37 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

    5 comments  ·  Circulation, Access Services & Fulfillment  ·  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.

13. Fix "Tile Vertically" so the bottom of the records don't get hidden behind the taskbar on Windows 11.

    In Sierra, on Windows 11, when you click "Tile Vertically" so you can see multiple records at the same time, it makes the windows too long, so that the bottom of the windows get hidden behind the taskbar if it is locked. It does not do this if you maximize a record window, or if you use snap. It only seems to be the "Tile Vertically" function.

    We use this function a lot to compare records for deduplication, and it is really annoying to have to manually resize windows so you can see the whole thing.

    17 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  ·  Cataloging & Metadata Management  ·  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. On all drop down search menus, move barcode to near top
    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

    UNDER REVIEW  ·  0 comments  ·  Circulation, Access Services & Fulfillment  ·  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. Time to Holdshelf Delay Period Not Reflected in SDA Holds Status

    The Time to Holdshelf feature in Sierra is useful in keeping patrons from showing up too early to pick up their holds. As seen in the attachment "Discovery Layer View" – which in our case happens to be BiblioCore – the availability status correctly reflects that the recently checked-in item "Easter Mice!" is not ready for pickup because the item is en route to the pickup location (which in this case is a set of freestanding pickup lockers in a remote area of the county).

    However, the holds status as displayed in the SDA incorrectly reports the item as being READY FOR PICKUP as seen in the "SDA Holds View" attachment, even though the specified Time to Holdshelf delay is still in effect. If a patron were to, say, call the library to inquire on the status of this item during the delay period, a Public Services staff member would tell the patron the item is ready for pickup when in fact it may not be ready. This runs counter to the intended purpose of the Time to Holdshelf table.

    The Time to Holdshelf feature in Sierra is useful in keeping patrons from showing up too early to pick up their holds. As seen in the attachment "Discovery Layer View" – which in our case happens to be BiblioCore – the availability status correctly reflects that the recently checked-in item "Easter Mice!" is not ready for pickup because the item is en route to the pickup location (which in this case is a set of freestanding pickup lockers in a remote area of the county).

    However, the holds status as displayed in the SDA incorrectly reports the item as being… more

    •  

    •  

    25 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

    3 comments  ·  Circulation, Access Services & Fulfillment  ·  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. Money Owed Data Point for Billed Notices

    Idea: add the money owed fixed field as an option for a data point in the Bills Notice Data Library for print templates.

    Value: Some libraries would like to be able to call out to users how much in total they owe on their account, not just the total of the items on that particular bill. Adding this field to the data library would enable them to do so.

    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

    UNDER REVIEW  ·  0 comments  ·  Circulation, Access Services & Fulfillment  ·  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. Add an Option to restrict Bibliographic Records within the Sierra System ( specific permission)

    Problem:
    In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:

    • Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.

    • Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.

    • Recommendation:
      Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra system itself. This would be managed through permissions-based access controls to ensure only authorized users can view or edit these records.

    Key Features:

    • Record Hiding: Enable a “Hide Record” option to restrict access to selected records. Hidden records would not appear in the search results or cataloging workspace for general catalogers.
    • Role-Based Permissions: System administrators can assign specific permissions to authorized users (e.g., cataloging supervisors) to view, edit, or unhide records.

    • Audit Tracking: Maintain a log of any actions related to hidden records, such as who hid, unhid, or edited them.

    • Benefits:

    • Error Prevention: Minimize accidental editing or publishing of restricted or sensitive records.

    • Controlled Access: Ensure that only authorized users can interact with restricted records.

    • Improved Workflow: Allow safe and organized record auditing without interference from other catalogers.

    • Proposed Implementation:

    • Add a “restricted Record” option in the record management interface, available only to users with specific permissions.
      Provide a “View Hidden Records” module accessible to authorized users.

    • Ensure hidden records are excluded from standard searches and workflows for catalogers without the necessary access rights.

    This feature would enhance Sierra's control over sensitive records, improve cataloging accuracy, and streamline workflows involving restricted or under-review records.

    Problem:
    In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:

    • Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.

    • Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.

    • Recommendation:
      Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra… 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  ·  Cataloging & Metadata Management  ·  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.

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

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.

    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

    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

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

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

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