Settings and activity
46 results found
-
54 votes
Jennifer Moakler
supported this idea
·
-
38 votes
The product team will review this idea for consideration for a future release.
Jennifer Moakler
supported this idea
·
-
3 votesJennifer Moakler
shared this idea
·
-
26 votes
The product team will review this idea for consideration for a future release.
Jennifer Moakler
supported this idea
·
-
8 votesJennifer Moakler
shared this idea
·
-
8 votesJennifer Moakler
shared this idea
·
An error occurred while saving the comment -
27 votes
An error occurred while saving the comment Jennifer Moakler
commented
We would also like to be able to limit both individually as well as by groups of iTypes. Our tool collection is broken into two iTypes: Power Tools and Other Tools. We want to let patrons borrow a max of 1 Power Tool and 3 tools of either type (so, either 3 Other Tools or 1 Power Tool and 2 Other Tools). Neither the old ItemA-D nor the new item type blocks quite meet our needs on their own.
Jennifer Moakler
supported this idea
·
-
5 votesJennifer Moakler
supported this idea
·
An error occurred while saving the comment Jennifer Moakler
commented
Agreed, though our library would like a shorter time period for notices to be cleared automatically. This sounds similar to our earlier submission here: https://ideas.iii.com/forums/951985-lx-starter/suggestions/49737857-ability-to-clear-notice-history
-
17 votesJennifer Moakler
supported this idea
·
-
22 votesJennifer Moakler
supported this idea
·
-
6 votesJennifer Moakler
shared this idea
·
-
8 votesJennifer Moakler
shared this idea
·
-
5 votesJennifer Moakler
supported this idea
·
-
16 votes
The product team will review this idea for consideration for a future release.
Jennifer Moakler
supported this idea
·
Jennifer Moakler
shared this idea
·
-
10 votesJennifer Moakler
supported this idea
·
-
34 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Jennifer Moakler
commented
We've just encountered a problem with this behavior in the opposite direction as well — we have some titles on order for an exhibit, and all copies will be non-holdable when they arrive. Since Sierra can't apply that behavior until the items actually arrive and get attached, patrons are (incorrectly) able to place holds in the OPAC in the interim.
Jennifer Moakler
shared this idea
·
-
31 votesJennifer Moakler
supported this idea
·
-
45 votesJennifer Moakler
supported this idea
·
An error occurred while saving the comment Jennifer Moakler
commented
We have a scenario where it's more helpful to continue showing the message when the account is opened (instead of only when trying to collect payment): in our libraries, payments aren't accepted at the service desk but only at the selfcheck kiosks and on our website, and the lock can interfere with those transactions. Having this popup appear when the patron's record is opened at the desk can help staff identify why a patron is having trouble making a payment on the kiosk. I agree that clearer wording would be very helpful, as we frequently get questions about this.
-
15 votesJennifer Moakler
shared this idea
·
-
26 votesJennifer Moakler
supported this idea
·
Our library uses automated lockers to lend laptops to patrons for in-house use. We'd like to block patrons whose cards have expired from borrowing until they come to the desk and renew, while still allowing borrowing for patrons blocked for overdues since these items won't be leaving the library. Our vendor is able to accommodate this for other customers because their ILS sends the patron expiration date in the BW field in the 24 response. Sierra's response only indicates the block in the first position of the patron status element, which includes blocks for all reasons, not just account expiration. We would like Sierra to also send the expiration date in the 24 and 64 responses so we can distinguish expired accounts from other blocks.