Browser client (websocket) logins not tracking user activity

[Bill Erickson]

Evergreen 3.2

Logins to the staff client are not represented as rows in actor.usr_activity. This is a result of missing config.usr_activity_type rows for websocket logins.

Proposal is to add 4 new activity types:

ewhat login, ehow ws-translator-v1
ewhat login, ehow ws-translator-v2
ewhat login
ewhat verivy

The latter 2 ensure that new ingress options are represented going forward even when new activity types are not specifically added for them.

[Bill Erickson (berick)]

And ws-translator-v* 'verify' entries.

[Bill Erickson (berick)]

Additions here:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1818153-websocket-activity-types

[Bill Erickson (berick)]

To test, apply the SQL changes, then login to the browser client. There should now be an entry in actor.usr_activity for the logged in user of either etype of 25 or 26, depending on which websocket gateway is active.

[Michele Morgan (mmorgan)]

I applied the sql changes and am now seeing rows added to actor.usr_activity for web client logins. My signoff branch is at:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mmorgan/lp1818153_websocket_activity_types_signoff

[Bill Erickson (berick)]

Thanks, Michelle. Merged to 3.1 and above.