Review available information in Event table.

[jamoore]

Currently the Event type consists of :

• status
• time
• type (enum)

Though the user information is available on the rows that the EventLogs point to, that information is mutable. Each Event should carry Experimenter and Group information and possible other types as well.

[jmoore]

Will get to it during the security milestone.

[jmoore]

From a 2.21 OME db:

                                        Table "public.module_executions"
       Column        |            Type             |                         Modifiers
---------------------+-----------------------------+------------------------------------------------------------
 module_execution_id | integer                     | not null default nextval('module_execution_seq'::regclass)
 status              | character varying(16)       |
 r_time              | double precision            |
 iterator_tag        | character varying(128)      |
 dependence          | character(1)                | not null
 timestamp           | timestamp without time zone | default now()
 x_time              | double precision            |
 image_id            | integer                     |
 w_time              | double precision            |
 experimenter_id     | integer                     | not null
 virtual_mex         | boolean                     | not null default false
 module_id           | integer                     |
 dataset_id          | integer                     |
 input_tag           | text                        |
 error_message       | text                        |
 group_id            | integer                     |
 new_feature_tag     | character varying(128)      |
 t_time              | double precision            |

[jmoore]

Now that Event is a system type (without permissions, users, etc.) the following are pretty obvious additions:

• umask
• user
• group

Timing figures such as r_/w_/x_time might be of value but could also possibly be put in another object. Similarly with inputs. Though it is still underdeveloped, the concept of container events (mexes and virtual mexes) would suggest adding a containingEvent field. Where null, the event is top-level.

[jmoore]

r969 updates the event table. The basic request from client devs was "Who did what when?" Other use cases will most likely be supported by related tables : EventStatistics? and EventInputs? jump to mind. Closing until further fields are needed.