Comment 6 for bug 1617318

From some discussion in IRC, because I'm too lazy to retype it all...

[12:08:21] <miker> maybe I'm being too simple, but why not just show
the in-collections information as a stopsign alert? no need to
generate notes or anything, afaict
[12:09:03] <miker> as in, the list of orgs that have placed the user
in collections currently. it's there, it's authoritative...
[12:09:04] <berick> miker: i was musing the same thing
[12:09:14] <berick> and I think that's a better long-term solution
[12:09:28] <berick> use the data we have
[12:09:48] <miker> and easier, I'd think, than writing code to write
note (that will be ignored because notes are terrible ;) )
[12:10:27] <berick> well, UI dev is its own special thing (especially
with 2 active UI's) so I get the desire not to go down that path
[12:10:38] <berick> but, yeah..
[12:11:04] <berick> if we showed the tracker data, we could also show
dates applied
[12:11:15] <miker> I can attest that the stopsign page in webstaff is
not particularly hairy. it's the first preexisting one I touched :)
[12:11:16] <berick> and per-instance UMS notes (when they exist)

--
Mike Rylander
 | President
 | Equinox Software, Inc. / Open Your Library
 | phone: 1-877-OPEN-ILS (673-6457)
 | email: <email address hidden>
 | web: http://www.esilibrary.com

On Fri, Aug 26, 2016 at 12:00 PM, Bill Erickson <email address hidden> wrote:
> To further clarify, PATRON_IN_COLLECTIONS is created via the collections
> API, but it's removed the same as a PATRON_EXCEEDS_FINES penalty, only
> presumably with a different threshold.
>
> --
> You received this bug notification because you are a member of Evergreen
> Bug Wranglers, which is subscribed to Evergreen.
> https://bugs.launchpad.net/bugs/1617318
>
> Title:
> Collections API should create a standing-penalty-based note
>
> Status in Evergreen:
> New
>
> Bug description:
> Currently the open-ils.collections API creates an old-style patron
> note (actor.usr_note) on the patron account to indicate that the
> patron is in collections. These notes require several clicks to view,
> and aside from the "(See Notes)" indicator in the XUL client (not sure
> about the web client here), there is not a way for staff to know that
> a patron is in collections. My suggestion is that we add a new
> subroutine in Collections.pm that creates an ALERT_NOTE standing
> penalty that would show up when the patron record is accessed.
>
> I'm sure there's more to consider here, but that's what I've got at
> the moment.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1617318/+subscriptions