Action/Trigger Event Defs (e.g. Notices) Would Benefit for Optional "Description" Field

[Bill Erickson]

Evergreen 3.11 / Wishlist

The main use case is for display in the staff client patron editor, where opt-in notices are displayed. I could also imagine the descriptions displaying in the patron catalog. (Or, having 2 fields, one for staff and one for patrons).

For example, we have some notices that are only delivered to certain groups, some that are only delivered if other variants of the notice cannot be delivered, etc. I imagine there are other uses for a general purpose description field directly on the A/T event def.

These could be externally documented, of course, but it's handy to have them right in the patron editor interface, maybe collapsed by default to save vertical space.