243 results found

1. Do not fulfill holds for closed pick-up location

   Background:
   This is a common request from libraries during a shorter term closure (several weeks - a few months). Staff find it frustrating that we cannot stop holds going into transit to their location during the closure. As a general rule we do not batch change patron holds as each patron may choose to respond their own way to the closing through public interfaces (ex freeze, change the pickup location, etc), so batch-changing the staff end Not Before Date is not viable. The closed library asks other libraries to not send and not fulfill holds for their location but in a large consortium that is not practical and many staff do not remember or know how to avoid or undo hold fulfillment.

   Proposal:
   Add a setting that would give a hold pick-up location a value of "closed" (or "do not fill", etc), ideally that can be set in the Pickup Locations table. As part of Sierra's hold filling and priority logic at check-in, if the next eligible hold's pickup location matches a location with a value of "closed", then do not fill and skip to fulfilling the next eligible hold. When determining the eligibility of a hold to begin title-level paging, it should also check and not begin the paging cycle if the value of that pickup location is "closed".

   Note:
   The Days Closed Table is not a good candidate for determining pickup location status and applying this hold filling logic, as it also impacts due dates and hold expiration dates, and does not use precise year-month-day calendar dates.

   Background:
   This is a common request from libraries during a shorter term closure (several weeks - a few months). Staff find it frustrating that we cannot stop holds going into transit to their location during the closure. As a general rule we do not batch change patron holds as each patron may choose to respond their own way to the closing through public interfaces (ex freeze, change the pickup location, etc), so batch-changing the staff end Not Before Date is not viable. The closed library asks other libraries to not send and not fulfill holds for their location but in… 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

   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. Handling Unfilled Pages

   This is a resubmission of a recently expired idea & my continued longing to see some long lost development efforts brought to fruition.

   Following Disney's lead of recycling years old ideas for theme park attractions, I'd like to see an idea I'd had while working with a former employer brought to fruition in Sierra. We had been using Millennium at the time & the Circulation Product Manager had gotten to a point in development that there was a near-working model on III's test environment (I've got screenshots & even a Captivate video somewhere), but I left that employer & the III product manager left III & the idea was abandoned, which is a shame, as it could still be of benefit to Sierra hold management workflows.

   How it was designed to work was as follows:

   1) Staff would complete their title, item, or Rapido paging list, trapping everything that they pulled from the shelf for a local or external hold.
   2) If there were any items they could not locate, they would then access this newly created Unfilled Pages function.
   3) From this new function, they'd select the instance of the paging list from a drop-down menu that showed the time(s) the list was last run. The drop-down would include the title, item, & INN-Reach lists, & for libraries that ran it multiple times a day, each instance of that list.
   4) Their selection would take them to a list of items on that instance of the list that were not pulled & trapped for holds.
   5) From here, they would be able to convert the status of all unfound items to Missing in batch. The intended customer retained their place in the hold queue & the torch was then passed to the next library location where the item was understood to be available.

   This is a resubmission of a recently expired idea & my continued longing to see some long lost development efforts brought to fruition.

   Following Disney's lead of recycling years old ideas for theme park attractions, I'd like to see an idea I'd had while working with a former employer brought to fruition in Sierra. We had been using Millennium at the time & the Circulation Product Manager had gotten to a point in development that there was a near-working model on III's test environment (I've got screenshots & even a Captivate video somewhere), but I left that employer & the… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

3. Max Items A-D, But for the Number of Holds Allowed

   This is another resubmission of a recently expired idea that I had first suggested over a decade ago when at another library that was struggling how to balance its combination of branch & research library users & the sort of requests they might make. While no longer there, I still see it as a potentially useful means for staff to develop their request processes & create limits within limits.

   What I'd like to see is the ability to not only set a hold threshold, where a Patron Type is allowed x holds, but as is the case for the Max Items A-D (or more recently introduced Patron Checkout Limits table) allowed z number of holds on a specific item type &/or group of item types.

   Optimally, this would allow libraries to group batches of ITYPEs together & either exempt them from the overall max holds or assign them a limit within that maximum, & libraries would be able to create whatever local limits & combinations they might desire. For example with a max of 50 holds, while any number within that max can be for books, only 10 can be for DVDs, only 5 can be on Blu Rays, etc.

   This is another resubmission of a recently expired idea that I had first suggested over a decade ago when at another library that was struggling how to balance its combination of branch & research library users & the sort of requests they might make. While no longer there, I still see it as a potentially useful means for staff to develop their request processes & create limits within limits.

   What I'd like to see is the ability to not only set a hold threshold, where a Patron Type is allowed x holds, but as is the case for the Max… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  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. Split Permissions for Hold Blocks

   This is a resubmission of a recently expired idea.

   Currently, the ability to override a hold block is governed by permission 92.

   A hold might be blocked for a number of reasons. Staff might attempt to place more than the max number of holds allowed for a customer. They might place a hold for a customer on an item they already have checked out, etc.

   One scenario especially has been problematic for as long as I can remember:

   A patron finds an item on the shelf & takes it to a service point to check out. It turns out that this item can satisfy a hold placed by another patron. The Sierra client displays the message:

   Message
   Item on hold for another patron .p<xxxxxxx>. Check out item anyway?
   Alternatively, we see situations where a patron sees an item on a shelf that they want & takes it to the service point to be checked out. In this case, they just happened to pull it from the hold shelf, where it was already awaiting pickup by another patron. Here, the Sierra client will display this message:
   Item on holdshelf for another patron .p<xxxxxxx>. Check out item anyway?
   We would really like the ability to allow the first circumstance & prevent the second, across the board, which would mean separate permissions for each, one that we'd assign to staff & one that we'd deny.

   This is a resubmission of a recently expired idea.

   Currently, the ability to override a hold block is governed by permission 92.

   A hold might be blocked for a number of reasons. Staff might attempt to place more than the max number of holds allowed for a customer. They might place a hold for a customer on an item they already have checked out, etc.

   One scenario especially has been problematic for as long as I can remember:

   A patron finds an item on the shelf & takes it to a service point to check out. It turns out that… more

   •  

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

5. Notice Counts Should Reflect The Number of Notices, Not Items Notified About

   This is a resubmission of a recently expired idea. I’ve added insights from other users shared in comments on the original post.

   Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead have the Notice History feature, which shows the number of items for which notices are sent. I feel like it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.

   Beyond metrics, this would aid in the troubleshooting of notice production issues & comparing the volume of notices sent over different time periods, days of the week, months, etc. Those who centrally manage notices for member libraries understand that there can sometimes be substantial difference between their current metrics because the item count & notice count can’t really be thought of in tandem.

   Notice count based on the number of notices, not items included in the notices, would likely be far more useful & informative.

   This is a resubmission of a recently expired idea. I’ve added insights from other users shared in comments on the original post.

   Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead have the Notice History feature, which shows the number of items for which notices are sent. I feel like it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.

   Beyond metrics, this would aid… more

   •  

   •  

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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. Remove duplicate items from paging list

   Remove duplicate items on paging list. This is very confusing for staff. Even if there are 5 holds for an item if my library only has 1 available copy on the shelf then that item should only show up once on the paging list.

   • 

   62 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

   10 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

7. New Skins for Sierra

   This is a resubmission of a just-closed idea that was pretty well-received with 28 votes. New color options might breathe some new life into Sierra & be a fun way to mark its coming 15th anniversary as an ILS!

   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?

   This is a resubmission of a just-closed idea that was pretty well-received with 28 votes. New color options might breathe some new life into Sierra & be a fun way to mark its coming 15th anniversary as an ILS!

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

   •  

   •  

   •  

   31 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  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Add New Patron Block Based on Number of Items Claimed Returned

   This is a resubmission of a just-expired idea that had come close to winning on previous ballots.

   During the Circulation Forum at this week's IUG, a few libraries brought up their continued interest in going fine free, but also shared how they still faced challenges within their respective institutions from those who felt materials would not come back.

   This is a realistic concern, especially for libraries that couple going fine free with the protracted loan periods made possible by autorenewals. It can sometimes be challenging to get customers to return things, so we appreciate the availability of patron blocks that will prevent checkouts, renewals, etc., but not penalize a customer financially, like the ability to suspend borrowing privileges based on the number of days overdue.

   We'd love to see a new Patron Block added based on the number of items a customer has claimed returned. That number would be determined by the library, work in conjunction with the process of claiming an item returned, & be configurable via the Patron Blocks table, so when a customer hits x number of items claimed returned, they're block from borrowing until the items are found & checked in & the counter is reduced.

   This is a resubmission of a just-expired idea that had come close to winning on previous ballots.

   During the Circulation Forum at this week's IUG, a few libraries brought up their continued interest in going fine free, but also shared how they still faced challenges within their respective institutions from those who felt materials would not come back.

   This is a realistic concern, especially for libraries that couple going fine free with the protracted loan periods made possible by autorenewals. It can sometimes be challenging to get customers to return things, so we appreciate the availability of patron blocks that… more

   •  

   •  

   •  

   •  

   27 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

   13 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. Provide An Indicator/Warning When Order Has Already Been Sent to a Vendor

   This is a resubmission of a just-expired idea from Jeremy G.:

   In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.

   As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2) highlight any orders in red or blue where a sent message already exists in an ISBN pick field, similar to how duplicate invoices are colored in the import invoices function.

   The second potential piece of this would be to generate a pop-up message along the lines of "File contains previously sent orders, do you wish to proceed?" that would appear at the point where the individual orders are packaged together into a single file for uploading to the vendor. That message would allow staff the opportunity to back out if they wish and remove any offending orders before proceeding.

   This is a resubmission of a just-expired idea from Jeremy G.:

   In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.

   As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN… more

   38 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

   6 comments  ·  Acquisitions, Serials & 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

10. Allow Rapid Update of Order Status

    This is a resubmission of a just-expired idea from Thanyani M:

    Rapid or global update to update all Order Status at once.

    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

    1 comment  ·  Acquisitions, Serials & 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

11. Expand to Different Order Statuses for the Sierra REST API

    This is a resubmission of just-expired idea from Cecelia.

    The Sierra REST API does not return the order record for the bib if the order status is "a" (fully paid). It will only return information if it's "on order".

    Patrons are unable to place holds on new materials using Innovative Mobile for bibs with paid order records that do not yet have items attached.

    7 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  ·  Acquisitions, Serials & 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

12. Introduce a 'Cancel' Button in the 'Item Already Paid for' Pop-Up Warning

    This is a resubmission of a recently expired idea from Nicole T.:

    In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding further, returning the user to the search results list. The "CANCEL" option prevents inadvertent payments on the wrong order records, reducing errors in fund allocation and duplicate payments. It improves the user experience for all staff members, especially those new to invoicing, by providing a clear option to cancel erroneous actions. Staff members could correct their mistakes immediately, reducing the likelihood of paying for items on the wrong record. It saves time and effort that would otherwise be spent rectifying mistakes, such as reversing payments. Enhances overall efficiency in invoicing, contributing to smoother operations in a multi-branch library environment with numerous fund codes and multiple copies of items.

    This is a resubmission of a recently expired idea from Nicole T.:

    In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding… 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

    8 comments  ·  Acquisitions, Serials & 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

13. Increase Invoice Limit for Downloaded Invoices

    This is a resubmission of a just-expired idea that had come close to being selected in previous rounds of voting. I feel like it's needed even more now that we're using Amazon Business.

    The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.

    Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.

    Not all shipments are dealt with sequentially, which further complicates matters.

    We do not know the number of invoices in each file. If the system hits the limit during the load, some of the invoices are not loaded as the system stops before completely loading the file. We have no way of knowing what was missed until we manually check the file against the vendor’s emails. If invoices are missing and we reload, the system loads duplicates that will count against the limit on the day that it is reloaded. If we do not catch a missed invoice while it is on the vendor’s site, we will have to load it manually. In some cases, the vendor sends multiple small invoices and, when these load, the limit prevents us from loading larger invoices. Several staff members are loading invoices each day and have reported not being able to load 99 invoices if other staff have hit the limit.

    -I want to be able to load the entire invoice file.
    -I would like to know how many invoices are in a file. If there is an issue, I would like to know which invoices did not load.
    -I want staff to be able to load invoices reliably before they are removed from the vendor's site so that we do not have to input them manually.

    This limit slows down processing of invoices for us as we have several staff members who need to load invoices every day and as a result of the limit, we need to balance when they can do so. Quickly importing invoices is critical with several of our vendors as they only leave our invoice files on their site for a short time - in some cases only one week, making this a more complicated and slower process if we miss that window.

    This is a resubmission of a just-expired idea that had come close to being selected in previous rounds of voting. I feel like it's needed even more now that we're using Amazon Business.

    The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.

    Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.

    Not all shipments are dealt with sequentially, which further complicates matters.

    We… more

    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

    8 comments  ·  Acquisitions, Serials & 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

14. Make Apache logs available sooner

    When I look for the Apache logs in the SDA client under Web Master, the logs are a week old. This does not help when the server is suffering under increased bot activity or a DOSS attack. As software only, I can SSH into the server and download the logs but it would be more convenient if the SDA had the logs available immediately. I propose updating the available logs in the SDA to the day before.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Export RFID Pad Server Settings

    At my library, the installation of RFID equipment & the entry of the required IPs in Sierra are handled by two different departments. Typically, I'll see a ticket that a new PC/RFID pad has been added & receive a request that the IP be added to Sierra.

    In addition to the RFID Pad Server Settings table in Sierra, we maintain a separate spreadsheet of assigned IPs, machine names & information on when & whom the request came from to add or replace them.

    While adding & replacing more than 20 IPs this morning, it dawned on me that this process, or at least a periodic check to make sure that only valid/in use IPs are included in the table & that what's in the table matches other records that we keep (like that spreadsheet) would be improved if we could export what's in the table to more easily compare what's recorded elsewhere.

    At my library, the installation of RFID equipment & the entry of the required IPs in Sierra are handled by two different departments. Typically, I'll see a ticket that a new PC/RFID pad has been added & receive a request that the IP be added to Sierra.

    In addition to the RFID Pad Server Settings table in Sierra, we maintain a separate spreadsheet of assigned IPs, machine names & information on when & whom the request came from to add or replace them.

    While adding & replacing more than 20 IPs this morning, it dawned on me that this process,… more

    •  

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Allow Scheduler to send a file of records to an email address

    Allow Scheduler to send a file of records to an email address. At the moment it will only ftp a set of records, which is fine for some purposes but not for others.

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

17. Automatically email Manage Holds results to library staff

    Have the results of Manage Holds automatically on a regular schedule (ie. each morning).

    This would let staff pick holds even if they don't have Sierra open or available. The automated emails could be set up within the Manage Holds function itself, or could be accomplished if Scheduler worked with Manage Holds (right now Scheduler only works with Create Lists and Data Exchange).

    10 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

18. Add a column for Loan Rule # to Loan Rule Table instead of using seq # in the table

    Today the Loan Rule Number is the position in the Loan Rule Table. This means when we need to keep a lot of old and often Inactive rows in the table so that the loan rule numbers below don't change.
    
    If you added a column with a loan rule number separate from the sequence in the table that the Loan Determiner table would point to, we could still mark old rules inactive until we are sure there are no more checkouts, but after we confirmed that we could delete the row completely and keep a much neater cleaner table with only active and recently inactivated rules.

    Today the Loan Rule Number is the position in the Loan Rule Table. This means when we need to keep a lot of old and often Inactive rows in the table so that the loan rule numbers below don't change.
    
    If you added a column with a loan rule number separate from the sequence in the table that the Loan Determiner table would point to, we could still mark old rules inactive until we are sure there are no more checkouts, but after we confirmed that we could delete the row completely and keep a much neater cleaner table with… more

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

19. Tooltip/Info Bubble for Loan Rule Names

    We've currently got 55 loan rules in Cincinnati. Not the most I've seen, but also not the least. At a certain point, it becomes difficult to remember, or better yet, know at a glance, their purpose & what loan rule governs what. The character limit to the name entry for loan rules limits how descriptive we can be.

    A number of Sierra releases back saw the addition of the tooltip rollover when searching patron records. I'd love to see something similar applied, so when I'm scrolling & rolling over loan rules, I can see a 2 or 3 sentence free text description that offers enough detail to understand what in some cases are decades old rules.

    We've currently got 55 loan rules in Cincinnati. Not the most I've seen, but also not the least. At a certain point, it becomes difficult to remember, or better yet, know at a glance, their purpose & what loan rule governs what. The character limit to the name entry for loan rules limits how descriptive we can be.

    A number of Sierra releases back saw the addition of the tooltip rollover when searching patron records. I'd love to see something similar applied, so when I'm scrolling & rolling over loan rules, I can see a 2 or 3 sentence free… 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

    7 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

20. loan rule determiners by agency

    It would be nice to be able to choose location agency and leave location blank in the determiner table for some situations. In our case we have 4 partner library systems and one has 7 branches. Each of these branches has the exact same loan rules to allow certain items to circ to the whole consortium, and others to limit to only their system. If we could use agency, we would only have to create one set of those rules instead of one for each branch location prefix (in this case their branches are pri, max, bar, col etc. Instead it could be Agency 1).

    It would be nice to be able to choose location agency and leave location blank in the determiner table for some situations. In our case we have 4 partner library systems and one has 7 branches. Each of these branches has the exact same loan rules to allow certain items to circ to the whole consortium, and others to limit to only their system. If we could use agency, we would only have to create one set of those rules instead of one for each branch location prefix (in this case their branches are pri, max, bar,… 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