Stat Cat Filter not working properly in Item Holdings Editor

[Dale Rigney]

Tested in Evergreen 3.9.0

Items editor screen will only display Copy Stat Categories when owed by the registered workstation or in the direct org tree path of the Copy Stat Cat owning library. If you change the Stat Cat Filter to a library with a Copy Stat Category outside the workstations registered path the Copy Stat Categories will not display.

To test Create two Copy Stat Cat one owned by SYS1 and one Owned by SYS2. Log into the web client with a registered workstation at SYS1. Edit a copy, you will see the Copy Stat Cat for for SYS1. Change the Stat Cat Filter to SYS2. All Copy Stat Categories will disappear. Change the Stat Cat Filter to CONS and you will only see the Copy Stat Cat for SYS1.

When tested on 3.8 the Stat Cat Filter will change which Copy Stat Categories display. IF you Select CONS all Copy Stat Categories would display.

[Jason Boyer (jboyer)]

I'd like for there to be a little bit of discussion around this before just throwing a working branch up, especially from locations that do some amount of centralized cataloging. It's a super-simple change to just show all stat cats to everyone again and just use the filter to clean things up but that kind of defeats the purpose of SC ownership. (Existentially, what does it mean to *own* a stat cat, man?)

Should the entries you see instead be limited to the locations where you're allowed to edit items? Everyone sees everything all the time? Some other middle thing I'm not thinking about, etc.?

[Lindsay Stratton (lstratton)]

We are a multiple outlet consortia with central bib cataloging, central control of creating and maintaining stat cats, local holdings maintenance including application of stats cats, staff are only allowed to edit their own libraries' item records, and a large number of staff who work in multiple libraries.

The vast majority of our item stat cats are "owned" at the CONS level to be visible to all outlets, they are used for standardized reporting so we Very Strongly Recommend all item records have the appropriate stat cats, although the stat cats themselves are not required.

We have one library that uses a local stat cat.

IMO, stat cats should display based on the staff user's workstation library and automatically display all CONS, SYS, LIB, and BR stat cats as applicable, without the "Statistical Categories > Filter by Library" field.

For our purposes, hiding/filtering out the CONS stat cats would be really counterproductive, since staff can only edit their own items they don't need to access another library's stat cats in an item record, and most staff who work in libraries with branches and do holdings maintenance have working location permissions for the branches.

[Elizabeth Thomsen (et-8)]

We use statistical categories extensively. We have a few required ones at the consortium level used for statistical reporting, and libraries create and use their own for a variety of purposes related to statistics and reports, gifts, grants, retention, and all kinds of projects. Using the filter to turn off the display of consortium level statistical categories would be a big problem for us, and displaying other library's local statistical categories would be useless and highly annoying.

We agree with what Lindsay wrote in Comment 2: "stat cats should display based on the staff user's workstation library and automatically display all CONS, SYS, LIB, and BR stat cats as applicable, without the "Statistical Categories > Filter by Library" field."

But we may be missing something here -- what is the use case for having the statistical category filter, and how is it used? It may be important to site with a different set-up and workflow than ours, in which case I hope there's a way to address that as an option.

[Mike Rylander (mrylander)]

I don't use the interface directly, but based on my understanding from those that do, and the comments from Lindsay and Elizabeth, I think there should be a filter applied, and that the filter should be what is internally referred to as the "full path" org set for that workstation location. That is, the workstation location, all its ancestors, and all its descendants. The same would go for the stat cat entries available in each dropdown.

[Christine Morgan (cmorgan-z)]

Confirmed based on comments.