Skip to content

Allow relevant reductions from project level reducers #1502

@lcjohnso

Description

@lcjohnso

Current Behavior: Reducer configurations can specify relevant reductions, additional input information necessary for reducer computations. Example: For PH TESS, its subject reducer can define relevant user reductions via the user_reducer_keys configuration item. However, it is implicitly assumed in the code that the relevant reduction shares the same reducible as the reducer -- for the above example, the workflow.

Desired Behavior: Allow a configurable reducible_id that accompanies the reduction key input via [subject,user]_reducer_key. In most cases, this should default to the same reducible_id as for the reducer where it is being configured, but allowing a different reducible_id & reducible_type will allow project level reductions to be imported for use by a reducer. Example 1: a project level user reduction could be import by a workflow level subject reducer (e.g., project level user skill reductions imported into a workflow level subject probability reducer). Example 2: a workflow level subject reduction could be imported by a project level user reducer (e.g., workflow level subject difficulty reduction imported into a project level user skill reducer).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions