As pointed out by @rcwelsh , all json files constructed by workers (including the jsonRegSession worker) should include information about the user who ran them.
All workers call parse_arguments, which sets a ${USEREMAIL} variable, which can be a stand-in for the current user. This should be logged in the dB as an additional key-value pair attribute of the op or registration.
As pointed out by @rcwelsh , all json files constructed by workers (including the
jsonRegSessionworker) should include information about the user who ran them.All workers call
parse_arguments, which sets a${USEREMAIL}variable, which can be a stand-in for the current user. This should be logged in the dB as an additional key-value pair attribute of the op or registration.