Display Name of Outcome Assigning Department
When assigning an outcome to another unit in the organizational tree the name assigning the outcome will be displayed in the pending connections section of the context panel. This is also the case when an outcome is assigned to a secondary unit, however, the display name still shows from the original assigning unit. As an example, Demo University assigned the outcome Critical Thinking to the Mathematics department. Then the Mathematics department assigning the Critical Thinking outcome to MAT 113, which is a course within the Mathematics department.
As you can see from the screenshot below it appears that Demo University has assigned the outcome to MAT 113 unit, even though the outcome was assigned by the Mathematics department and not Demo University.
Below you can see how this feature now functions with the update. Since the outcome was assigned to MAT 113 from the Mathematics department, it will now be displayed as such in the pending connections area in the context panel.
Outcome Result Data Aggregation
We have released an update to how Outcomes will aggregate data when related items. In the screenshot below, you can see that we have created an Outcome at the accounting department level. We then relate that outcome to two outcomes at the child unit of ACC 141. Then we relate those two outcomes to a single section outcome where the assessment is conducted and results entered.
Since the results are coming from a single assessment at the section level and feeding two other layers (course & department) we expect the results to aggregate in a certain way to ensure accuracy. In the diagram below you can see that the total count of students at each achievement level for the Accounting departments outcome is double that of what the results are at the section level (40 students vs 20 students) where the assessment was conducted.
This is a result of how the outcomes have been related to one another. Until today Outcomes simply saw two separate relationships and calculated the aggregate by combining the result totals from each of the relationships. We are happy to announce that Outcomes now knows to look to look at the relationships and only count a set of results once when there is a single set of results, regardless the number of intermediate layers.
Due to this update, we can see how our aggregated results have changed at our top level (Accounting department) the diagram below. While the given setup in this example has used a department to course to section setup of related items, this holds true for other parent/child relationships. For example, if we had the top level as the institution (replacing the accounting department) and two outcomes related at the College of Business (replacing the acc 141 course) with results being pulled from a department (replacing ACC 141.1 section) would also be a scenario covered by this update.
Deleting an Assigned Outcome
Originally when assigning an outcome to another department to either be assessed, related to another outcome or assigned to a lower unit the outcome would remain even when the original outcome was deleted from the originating unit. This would cause issues where the outcomes "left over" at the lower levels, which is not the intended behavior.
When deleting the original root outcome the copies of the outcome will be deleted from the lower units as well. When deleting the outcome that has associated assessment data the user will be presented with the warning below. If the root outcome is deleted, the assessment that is providing results at the lower level will be deleted as well.