Hi Darcy,
I noticed a few missing notice types, mainly to do with requests:
·
Awaiting pickup/on hold reminder-there should be an automatic courtesy notice reminding a patron that an item has still not
been picked up. For example, we send the initial “item is awaiting pickup” notice and then send another notice 2 days before the hold expiration date to remind them to pick up the item. This one is the most important for Chicago.
·
Awaiting pickup/on hold expiration—these can be sent automatically when a request is closed because it has reached the on
hold expiration date. Chicago does not send these notices and would not need them, but others may. We find they are problematic and prefer to only send the awaiting pickup reminder notice.
·
Request expiration notice - unfulfilled – this notice is sent out automatically when a request is closed because the request
has expired unfulfilled and never became awaiting pickup.
·
Request cancellation notice-when staff cancel a request manually, this should be sent to the patron and include any reason
staff selected at the time of cancellation-these reasons are predetermined but also include an optional free text that staff can enter.
·
Delivery request fulfilled-this would be sent to a patron when a delivery request is fulfilled and automatically loaned to
their account and routed for delivery to, for example, their campus address. Chicago does not offer a delivery service, so I can’t be sure if this is necessary, but I would assume so. The language would need to be different than the awaiting pickup notice.
I also just want to clarify that courtesy and overdue notices both need to be configurable so that you can send multiple ones on different dates. For example, we send 3 courtesy notices prior
to a due date, and then several overdue notices. I assume that’s a given, but just want to clarify it’s needed for both types, not just overdue.
As far as the claims notices go, I’m not sure if we need to include in the “found” notices whether staff found the item or it was returned by the patron, or if we simply use the “no fines owed”
for the former and if returned by the patron but no fines are charged and “fines owed” for the latter. This might need some more clarification.
I’ll look at the language and mockups and provide feedback under separate cover.
Best,
David
- - -
David W. Bottorff
Head of Collection Management and Circulation
The University of Chicago Library
From: folio-ra@ole-lists.openlibraryfoundation.org [mailto:folio-ra@ole-lists.openlibraryfoundation.org]
On Behalf Of Darcy A. Branchini
Sent: Thursday, June 28, 2018 1:20 PM
To: folio-ra@ole-lists.openlibraryfoundation.org
Subject: Patron notices - please review
Hi all,
Last week Thursday, I provided an update regarding patron notices and there were a couple of documents that I requested your review and/or feedback on:
A list of notices being defined with a flag on those that will be included out of the box. Notices can be cloned/copied and there’s no restriction on the number of a particular type of notice.
https://docs.google.com/spreadsheets/d/1MOpnDvO-3WuHKMJWimFSicVxVQ5MxnW8TiCEO_RivbM/edit?usp=sharing
For out of the box or predefined notices, the language has been defined here. The language can be customized by institutions. These are just a starting point, but I just want to be sure there isn’t a blatant
problem and/or omission, etc.
https://docs.google.com/document/d/10SKhGndn7jdVkgwSmzcoz4XuVBXPqvE-ITMSINjk18Q/edit?usp=sharing
User stories are here (might not be as interesting to you… intended more for developers):
https://issues.folio.org/browse/UICIRC-70
And lastly, mockups are here:
https://drive.google.com/drive/folders/1jOPde19CbRRiNrx4sEPLX7oMV7m1lPgm.
If you can take a look and if you have questions or concerns let me know by commenting on the documents themselves and/or sending me an email. If you could have it by the end of the day Thursday, July 5th,
I’d appreciate it. Thanks!
Darcy
To unsubscribe from this list please go to
http://www.simplelists.com/confirm.php?u=HlPdNmMDsk02fL31CnSAJArYoxM5Hzwp