config.circ_matrix_matchpoint and config.hold_matrix_matchpoint need a description field

Agreed, this would be nice.

---Sent from iPhone

** Changed in: evergreen

   Importance: Undecided => Wishlist

** Changed in: evergreen

    Milestone: None => 2.next

--
You received this bug notification because you are subscribed to

Evergreen.

Matching subscriptions: evergreenbugs

https://bugs.launchpad.net/bugs/1545115

Title:

  config.circ_matrix_matchpoint and config.hold_matrix_matchpoint need a

  description field

Status in Evergreen:

  New

Bug description:

  Circ and hold rules are extremely complex. It would be quite helpful

  to have a field for people to add comments, notes, or descriptions

  that help when reviewing these rules in either the staff client or the

  db.

To manage notifications about this bug go to:

https://bugs.launchpad.net/evergreen/+bug/1545115/+subscriptions

After talking with Dyrcona at the conference about this I went to find that not only is there one but I had commented on it! I tossed together a simple branch for this on the db level available at user/rogan/lp1545115_matrix_descriptions

I tested it and it worked fine for me. Included is a pg_tap test to test for the prescence of the columns which I tested as well.

Awesome! Thanks, Rogan. Quick question, would that new column just automatically start to display in the staff client? Or would there need to be some additional configuration there?

Hi Jane,

That patch is just for database support which would help those who do admin in db and is a pre-req for staff client. The staff client requires a small (and I mean very small) additional bit of work to support it.

I took a shot at it and I admit my testing was very quick but this worked on my test box for adding the description field to the display grid and editing interfaces in the staff client for the hold and circ match points:

user/rogan/lp1545115_matrix_desciptions_w_staff_client

I also added the patch this time.

Oh, I should mention the second commit branch I posted is squashed to have the database stuff in it as well so you would only need the second patch / branch I posted.

Thanks for all your work on this, Rogan. What would it take to get this into master/future releases?

Hi Jane,

If you're interested, I could load Rogan's code on a Sandbox to give you an opportunity to test and sign off on it.

Kathy

Hi Kathy,

Sorry for the delayed response! I'd be happy to test it in a sandbox!

  -Jane

Tested and signed off. The signoff branch includes a couple follow-up patches that (a) consolidate the database updates into one script and (b) add release notes: user/gmcharlt/lp1545115_signoff

I'll give this a whirl, since I recall speaking to Rogan about it at the 2016 conference and thinking it was a good idea.

The field just shows up in the staff clients.

All of the tests succeed and I was able to add and edit the description field in the webstaff client as well as the XUL staff client.

That's good enough for me. Pushed to master for 3.0.

Nice. Thanks for submitting this, Jane.

We've long been using/abusing the script_test field for that purpose in our circ rules, and wishing there were something equivalent for hold rules.