Settings and activity
315 results found
-
10 votes
Shawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
62 votesShawn P. Farrell
supported this idea
·
-
27 votesShawn P. Farrell
shared this idea
·
An error occurred while saving the comment An error occurred while saving the comment Shawn P. Farrell
commented
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.
An error occurred while saving the comment Shawn P. Farrell
commented
@G.Wise, when this item was reviewed & scored by III's Engineers, that was indeed one of the functional requirements. See Mike's summary below. Staff would be required to perform an override (& their action would be recorded in the circulation overrides table). Hopefully, the idea will return on a future ballot.
An error occurred while saving the comment Shawn P. Farrell
commented
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.
An error occurred while saving the comment Shawn P. Farrell
commented
This was functionality we had in a previous ILS, long before the fine free craze had captured the attention of so many. I would imagine, if introduced, it would be as optional/configurable as any other block.
When a library has a clearly communicated policy for items claimed returned & staff are trained to & actually do follow through with shelf checks, it can be as effective as any other block. At CHPL, in addition to immediate shelf checks when a customer claims an item returned, we run regular reports for staff to act on, that help minimize the number of items that have actually been returned. We also reset the counter annually for those with no active claims on their account.
An error occurred while saving the comment Shawn P. Farrell
commented
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.
-
40 votesShawn P. Farrell
shared this idea
·
-
17 votesShawn P. Farrell
shared this idea
·
-
7 votesShawn P. Farrell
shared this idea
·
-
25 votesShawn P. Farrell
shared this idea
·
-
17 votesShawn P. Farrell
shared this idea
·
An error occurred while saving the comment Shawn P. Farrell
commented
Further refinements, as requested by NYPL/BookOps:
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.An error occurred while saving the comment Shawn P. Farrell
commented
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.
-
3 votesShawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
7 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
-
2 votes
An error occurred while saving the comment Shawn P. Farrell
commented
The usefulness of additional/customizable transaction types came up again in a meeting today. We got a request for the addition of a Technology Instruction category & Patron Account category.
Shawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
10 votesShawn P. Farrell
supported this idea
·
-
19 votesShawn P. Farrell
supported this idea
·
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.