Blank stat_cat_entry in actor.stat_cat_entry_usr_map

[[e-mail]]

EG2.2 & 2.2.5

Records with blank stat_cat_entry (not NULL) are created in the above-mentioned table when there is no input for stat_cats with allow_freetext set to FALSE and required set to FALSE.

Tina Ji
Sitka

[Ben Shum (bshum)]

Well that's not good... confirmed for me as well.

[Ben Shum (bshum)]

SQL used to find some of these bad entries:

SELECT astat.name, COUNT(*)
FROM actor.stat_cat astat
JOIN actor.stat_cat_entry_usr_map asceum ON asceum.stat_cat = astat.id
WHERE astat.allow_freetext = FALSE AND astat.required = FALSE
AND asceum.stat_cat_entry = ''
GROUP BY 1
ORDER BY 1;

[Jason Boyer (jboyer)]

Just dropping in to say this still affects 2.11. There's no way to "remove" an actor stat cat entry map like you can on assets. This causes confusion when running reports on actor stat cats and for any non-free-entry stat cat requires you to create a blank/none/dontcare/etc. entry.

[Andrea Neiman (aneiman)]

"needstest" tag is used to indicate code that needs an automated test included

[Elaine Hardy (ehardy)]

I found that out after I used it for several of these ancient bugs. I
haven't had the time yet this morning to change them.

The tag needs to be clearer and one for testing by people would be good.

J. Elaine Hardy, PINES and Collaborative Projects Manager
------------------------------

Georgia Public Library Service

1800 Century Place, Suite 580 | Atlanta, GA 30345

[phone] | <email address hidden>

[phone] | Cell

<https://www.facebook.com/georgialibraries>
<https://www.twitter.com/georgialibs>

Join our email list <http://georgialibraries.org/subscription> for stories
of Georgia libraries making an impact in our communities.

On Fri, Mar 8, 2019 at 12:15 PM Andrea Neiman <
<email address hidden>> wrote:

> "needstest" tag is used to indicate code that needs an automated test
> included
>
> ** Tags removed: needstest
> ** Tags added: statcats
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: <email address hidden>
> https://bugs.launchpad.net/bugs/1130389
>
> Title:
> Blank stat_cat_entry in actor.stat_cat_entry_usr_map
>
> Status in Evergreen:
> Confirmed
>
> Bug description:
> EG2.2 & 2.2.5
>
> Records with blank stat_cat_entry (not NULL) are created in the above-
> mentioned table when there is no input for stat_cats with
> allow_freetext set to FALSE and required set to FALSE.
>
> Tina Ji
> Sitka
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1130389/+subscriptions
>

[Michele Morgan (mmorgan)]

Just realized this is happening on our 3.1 production system (xul client). A library staff member noticed erroneous stat cats with blank values listed in the patron summary.

This appears to be an issue in the xul client only. When creating or editing a patron record in an org unit that has Patron Statistical Categories set with allow_freetext FALSE and required FALSE, rows are created in actor.stat_cat_entry_usr_map with blank stat_cat fields.

Testing in a 3.2 web client, no rows with blank stat_cat fields are created in actor.stat_cat_entry_usr_map when a patron is created or edited, so this does not seem to be an issue in the web client. Adding a fixedinwebby tag and if others can confirm, this should be set as Won't Fix.

Also adding a reference to this in bug 1789263 and removing tag "cataloging" and adding "patron" since this is an issue with patron rather than item stat cats.