Acq: Use scope to constrain choice of lineitem alerts user/senator/lp996033
authorLebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Tue, 8 May 2012 18:20:24 +0000 (14:20 -0400)
committerLebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Wed, 9 May 2012 16:30:16 +0000 (12:30 -0400)
commitfb851832a5e6fef87d6a6c2f4f78a01ccace86db
tree940971738b5bc2eade1cada372e9ff3699d1f120
parentbd190b0b66baaeb669f042b90053732596771311
Acq: Use scope to constrain choice of lineitem alerts

This commit addresses this launchpad bug:
https://bugs.launchpad.net/evergreen/+bug/996033

The controlled vocabulary of acq lineitem alert text is set up in an
interface labeled "Line Item Alerts" in the staff client admin menu. In
the PO and selection list interfaces (where alerts can be applied), we
will limit the user to selecting alerts from those owned at the user's
workstation org unit (or its ancestors).

When we display applied alerts, we can also display the shortname of the
org unit at which the alert text is defined (the owning_lib column).
This should help clarify what's going on with alerts that have already
been applied using alert text from another org unit.

[Amended since original reference on Launchpad to also show the
owning_lib's shortname when confirming alerts at receive time.]

Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Open-ILS/web/js/ui/default/acq/common/li_table.js