308 results found

1. Allow Pickup Location Changes After Hold Is Activated (with Optional Patron Notification)

   In Sierra, once a hold is activated, the pickup location becomes locked. This occurs even if an error happens or the original location becomes unavailable. The limitation creates workflow issues for libraries that use lockers, shared delivery systems, or multiple branches.

   We are requesting a system enhancement that allows authorized staff to edit the pickup location of a hold after it has been activated, but before it is checked out or expires.

   -Why This Is Needed:

   • Locker and space-based workflows: Staff may discover after trapping a hold that a locker is full or not functioning. At that point, there is no way to reroute the hold without canceling and re-placing it.

   • MeL/INN-Reach and delivery systems: Multi-library consortia and shared systems occasionally fulfill to the wrong location. Currently, Sierra does not allow staff to correct this once the hold is trapped.

   • Staff training errors: If the wrong login or fulfillment location is used during check-in, the item is committed to the incorrect pickup point. While enabling "Priority Paging: Refuse Item Hold" can prevent premature activation, this feature introduces the risk of accidentally canceling INN-Reach holds, which can disrupt patron access and increase staff workload.

   • Patron requests: Patrons sometimes ask to change their pickup location after the hold is already activated. Staff have no way to update the system to reflect this without canceling and re-initiating the hold manually.

   -Proposed Enhancement:

   • Allow staff with appropriate permissions to change the pickup location of a trapped hold, up until the item is either checked out or expired.

   • Log the change in the item or hold history to provide a record for auditing and accountability.

   -Optional but Strongly Recommended:

   • Add an optional "Pickup Location Changed" notice that can be sent to patrons automatically when a change is made. This would help notify them that their item is ready at a different location.

   -Benefits:

   • Reduces the need for manual workarounds and improves the patron experience

   • Provides flexibility in time-sensitive workflows

   • Supports accurate hold management in cases of staff error or patron changes

   • Saves staff time by eliminating the need to cancel and recreate holds or contact individual patrons.

   In Sierra, once a hold is activated, the pickup location becomes locked. This occurs even if an error happens or the original location becomes unavailable. The limitation creates workflow issues for libraries that use lockers, shared delivery systems, or multiple branches.

   We are requesting a system enhancement that allows authorized staff to edit the pickup location of a hold after it has been activated, but before it is checked out or expires.

   -Why This Is Needed:

   • Locker and space-based workflows: Staff may discover after trapping a hold that a locker is full or not functioning. At that point, there is… 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

   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

2. Rearchitect iiirecord.record_metadata to provide improved audit trail accountability

   It is sometimes helpful to see who created, updated or deleted a record. Catmaint provides a lot of detail but doesn't cover many record types. I propose the following solution, which doesn't have particularly burdensome storage requirements:

   1. Build a many-to-many table with an id primary key column, a timestamp, a code indicating the C-R-U-Uprevious-D record operation and foreign keys linking to record_metadata.id and to iii_user.id.
   2. Backfill this new table using the available timestamps in record_metadata, catmaint and any other table like catmaint which might provide record edit history.
   3. Rename record_metadata and drop its four *_gmt timestamp columns. Yes, this creates a chicken/egg catch-22 for the foreign keys created in step 1. Clever Innovative staff find a solution.
   4. Create a view named record_metadata which provides backward compatibility for read operations.
   5. Creates/Updates/Deletes to the former record_metadata now require recoding, which may not be too awful if these operations are currently managed by stored procs and possibly triggers.

   It is sometimes helpful to see who created, updated or deleted a record. Catmaint provides a lot of detail but doesn't cover many record types. I propose the following solution, which doesn't have particularly burdensome storage requirements:

   1. Build a many-to-many table with an id primary key column, a timestamp, a code indicating the C-R-U-Uprevious-D record operation and foreign keys linking to record_metadata.id and to iii_user.id.
   2. Backfill this new table using the available timestamps in record_metadata, catmaint and any other table like catmaint which might provide record edit history.
   3. Rename record_metadata and drop its four *_gmt timestamp columns. Yes, this creates… more
   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

   1 comment  ·  Reporting & Analytics (incl Decision Center)  ·  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. Automatically add date/timestamp to Notes and Messages

   It would be helpful if the system automatically added a date/timestamp to Notes and Messages added to Patron and Item records by staff. Currently, we ask our staff to always add thier initials and date to notes and messages when adding them but it doesn't always happen. There are also inconsistnecies in how these are added and no easy way to search for them. We also find that notes/messages are not always removed after they are addressed.

   If we had an accurate way to determine the date a note/message was added, it would be possible to develop a retention policy and procedures for record cleanup.

   I would like to see a system generated date/timestamp appended to each note/message which can also be searched so that you could search for Notes/Messages added to patron records before a certian date in order to identify Notes/Messages that could be cleaned up in Global update if they are no longer useful.

   It would be helpful if the system automatically added a date/timestamp to Notes and Messages added to Patron and Item records by staff. Currently, we ask our staff to always add thier initials and date to notes and messages when adding them but it doesn't always happen. There are also inconsistnecies in how these are added and no easy way to search for them. We also find that notes/messages are not always removed after they are addressed.

   If we had an accurate way to determine the date a note/message was added, it would be possible to develop a retention policy… 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

   4 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

4. Add 'Previous' button to Receiving

   Staff are really appreciating the addition of a 'Previous' button to the record creation process which allows them to back up and fix a mistake without having to go all the way through the process before returning to make a correction. Staff would like to see similar functionality within the Receiving process. We receive using the process that combines creating the item with receiving.

   Currently, for receiving an item, it will prompt you through the boxes to fill in the required information.  As you proceed through, if you make a mistake or skip something you have to cancel and start over. Staff would like to be able to go back and fix something without starting over.

   Staff are really appreciating the addition of a 'Previous' button to the record creation process which allows them to back up and fix a mistake without having to go all the way through the process before returning to make a correction. Staff would like to see similar functionality within the Receiving process. We receive using the process that combines creating the item with receiving.

   Currently, for receiving an item, it will prompt you through the boxes to fill in the required information.  As you proceed through, if you make a mistake or skip something you have to cancel and start… 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

   1 comment  ·  Acquisitions, Serials & Item/Issue/Inventory 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

5. Improve clear hold functions for integrated systems

   When a hold has been cleared or is defunct, the information Sierra provides integrated integrated systems (IMMS for our example) over API is not consistent In particular, when clear holds is run in Sierra. During clear holds, the item status either remains at ! On holdshelf or changes to another item status. When it remains as !, IMMS sees the hold is still active and does not instruct staff to clear the item from the hold shelf. Daily and weekly processes are needed to update the item records for IMMS to recognise the changes.

   Can the clear hold function in Sierra be developed for consistency of information provided to integrated systems? e.g. Change all the the item statuses when clear holds is run, or provide another in the API that is robust for notifying integrated systems of the update.

   When a hold has been cleared or is defunct, the information Sierra provides integrated integrated systems (IMMS for our example) over API is not consistent In particular, when clear holds is run in Sierra. During clear holds, the item status either remains at ! On holdshelf or changes to another item status. When it remains as !, IMMS sees the hold is still active and does not instruct staff to clear the item from the hold shelf. Daily and weekly processes are needed to update the item records for IMMS to recognise the changes.

   Can the clear hold function in… 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

   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

6. Add "permanent location" field in item record and function to change to it

   We have shelves for new materials, and item location codes for these ("new mysteries," "new fiction," "new DVDs," and lots more). Moving items from the new shelves to the regular shelves is a chore, both in handling materials and in knowing (and selecting) what location to change them to. It would be great if you could just get into a function in Sierra that would change the current item location (the "new" one in my example) to the permanent item location (a new field that would be added with this idea, which would catalogers would populate when the item was cataloged). Then, in this function, anyone could just scan a stack of items, one after the other, without having to look up what the "not-new" location was or choose it or anything. A "permanent location" field could be used in other ways, maybe for displays.

   We have shelves for new materials, and item location codes for these ("new mysteries," "new fiction," "new DVDs," and lots more). Moving items from the new shelves to the regular shelves is a chore, both in handling materials and in knowing (and selecting) what location to change them to. It would be great if you could just get into a function in Sierra that would change the current item location (the "new" one in my example) to the permanent item location (a new field that would be added with this idea, which would catalogers would populate when the item was… 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

   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

7. A "full Payment History file" event should log an error to the Admin App's System Messages log

   Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.

   Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged, but with scope creep in mind let's just start with this one. 😊

   Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.

   Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged,… more

   •  

   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  ·  Acquisitions, Serials & Item/Issue/Inventory 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

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

   •  

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

9. Limit the number of holds to the total count of copies in that Bib

   There must be a configuration in Sierra to limit the number of holds can be placed at the bib level. We want to limit the hold count to number of copies in the Bib.

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

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

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

11. Allow for Customization of Fields Included in Expanded Display of Patron Records

    I recently learned that the fields included in the Expanded Display for patron records (when you rollover/click the i next to the record) are hard coded.

    I found this unfortunate, because what's shown in the Expanded Display differs depending on where you're viewing it, which in the case of patron records is either going to be in the Search/Find a Patron view or the Check Out mode view.

    Examples of where I see room for improvement here:

    1) When I search for a patron by name & come up with dozens of people with the same name, an identifier like DOB would be useful in finding the correct patron record, at a glance, but DOB doesn't appear in this view.

    2) When I bring up a patron's record in Check Out mode (before entering View or Edit mode), DOB does show in the Expanded Display, despite it already appearing in the Sierra window (at least in our case).

    3) We have some local policies where the number of items claimed returned factors in to a patron's borrowing privileges & having that available at a glance in the Expanded Display would be more useful than a half dozen different entries in note fields.

    4) If it's a question of screen real estate, in the case of the Expanded Display for Search/Find a Patron, their name appears twice. First, as (for example) Farrell, Shawn P above their pNumber & then as Last: Farrell First: Shawn Middle: P directly beneath it.

    The ability to customize what's shown & in what order, like we are with the record creation wizard, would allow libraries to take better advantage of the Expanded Display view to suit local needs.

    I recently learned that the fields included in the Expanded Display for patron records (when you rollover/click the i next to the record) are hard coded.

    I found this unfortunate, because what's shown in the Expanded Display differs depending on where you're viewing it, which in the case of patron records is either going to be in the Search/Find a Patron view or the Check Out mode view.

    Examples of where I see room for improvement here:

    1) When I search for a patron by name & come up with dozens of people with the same name, an identifier like… 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

    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

12. Send To: Globally Purge Charges

    It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to Globally Purge Charges.

    The state of Ohio has a statute of limitations on debt collection that has us purging money owed longer than 5 years on a weekly basis. While this is bazonkers IMO, apparently it's also the law of the land, & it would make the process much more quick & convenient if we could select a file in Create List, navigate to Tools - Send To in the Sierra top menu, & choose Globally Purge Charges (along with either Rapid & Global Update & Delete Records).

    It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to Globally Purge Charges.

    The state of Ohio has a statute of limitations on debt collection that has us purging money owed longer than 5 years on a weekly basis. While this is bazonkers IMO, apparently it's also the law of the land, & it would make the process much more quick & convenient if we could select a file in Create List, navigate to… 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  ·  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

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

14. Create a pop-up when you are about to overwrite a review file in create lists.

    It is very easy to accidentally overwrite a review file in create lists. There should be a pop-up that asks if you want to overwrite the file so that you know you're doing it.

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

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

    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

16. add location column in Count Use function

    Under the count use function, is it possible to add a location column? Currently, we have Title / Barcode / Count / Status. This way, when staff collects used but not checked out items and counts their usage, they can also see - at a glance - if the item belongs to a different floor/location and can separate it on the spot.

    This added information will save staff time and minimize the chance of something being misplaced.

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

    •  

    •  

    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  ·  Reporting & Analytics (incl Decision Center)  ·  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. 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.

    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

    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

19. Deposit Functionality

    Ability for patron to add money to their Sierra patron account (via self-check) to pay for future fines, fees, and printing. We are looking to go mostly cashless, but some patrons aren't able to get credit cards (like our young patrons here after school). Our self-check machine takes cash, which would allow patrons to print and pay fees/fines with cash, even if the staff doesn't have a cash register.

    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  ·  Customer Relationship & Account 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

20. Add "mark damaged items" workflow to checkin

    Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.

    All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.

    Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like to see it (button beside the backdate option)

    Possible Mark Damaged Item behaviour within check-in function:
    1) Staff would select the "mark damaged items" button before they check-in the damaged item. It would not "stick" and apply to the next item.
    2) Item is checked in
    2) The "mark damaged items" pop-up would appear
    3) Staff would choose one of the following options: mark damaged, mark damaged and add charge, mark damaged and add bill, or cancel.
    4) A permission could be added to select this option at check-in so that it is optional for libraries.

    Thank you,
    Elizabeth

    Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.

    All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.

    Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like… 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

    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