CPD3 Edit Directive Structure

Directive author (initials)

Directive descriptive comment

Disable/delete the directive and do not apply it to data

Directive change history log

The keys immediately below this are array indices. These are indexes into an ordered list, with the first element being zero. For example, #0 is the first element of the array. The paths represented here use #0 as a placeholder for all indices.

Time the event occurred at

s

Time the event occurred at

This is an absolute point in time specified as the number of seconds from the Unix epoch (1970-01-01T00:00:00Z).

Environment description the change was made in

Software revision description the change was made by

The type of the input

This is an enumeration value. It accepts a single string (not case sensitive) from a list of possible choices. Possible values:

Reported effective user name the change was made by

The history of the directive before creation (e.x. derived history)

The keys below this one have an arbitrary structure. That is, the exact contents are not directly interpreted by the system so they are defined by conventions or subsequent usage.

The profile (variable name) of the directive before the change

The end time of the directive before the change

s

The end time of the directive before the change

This is an absolute point in time specified as the number of seconds from the Unix epoch (1970-01-01T00:00:00Z).

The start time of the directive before the change

s

The start time of the directive before the change

This is an absolute point in time specified as the number of seconds from the Unix epoch (1970-01-01T00:00:00Z).

The end time of the directive after the change

s

The end time of the directive after the change

This is an absolute point in time specified as the number of seconds from the Unix epoch (1970-01-01T00:00:00Z).

The start time of the directive after the change

s

The start time of the directive after the change

This is an absolute point in time specified as the number of seconds from the Unix epoch (1970-01-01T00:00:00Z).

The directive parameters before the change

The keys below this one have an arbitrary structure. That is, the exact contents are not directly interpreted by the system so they are defined by conventions or subsequent usage.

The directive extension before the change

The keys below this one have an arbitrary structure. That is, the exact contents are not directly interpreted by the system so they are defined by conventions or subsequent usage.

The author of the directive before the change

The comment of the directive before the change

The priority of the directive before the change

The system internal state of the directive before the change

Edit action

An edit action is an operation performed on the data stream. The most common example is imply invalidation: setting the affected data to explicitly missing values.

Split archives

Consider the metadata archive to be part of their parent definition instead of a separate variable

Consider statistics flavors to be part of their parent definition instead of a separate set

Split flavor sets

Split stations

Split variables

Fragment incoming values to the directive time bounds

EBAS flags to set when the edit is applied

Trigger to apply the edit

An edit trigger is a means of detecting a condition in the data stream. For example, it can compare a value to a threshold and only take action when the value exceeds the threshold.

Split archives

Consider the metadata archive to be part of their parent definition instead of a separate variable

Consider statistics flavors to be part of their parent definition instead of a separate set

Split flavor sets

Split stations

Split variables

Application priority in the editing filters

Hide the directive in the default display by indicating it is an internal system edit