Show Advanced KnowledgeHide Advanced Knowledge

Filter Revision in Manual Scoring

1 Requirements

By now, there is a filter in the manual scoring in tests that consists of four options:

• Active User Only
• Inactive Users Only
• Scored Participants
• Unscored Participants

In my view, both of the first options are weird. It might be useful to filter for this criterion but:

• It seems quite a random choice to offer this very special user account data field as a filter here while ignoring any other possible field.
• In that case, inactive users should be automatically hidden, like they are hidden or deactivated in many other functions.

 
However, there is much more useful use case for a similar feature:
Filter active participants, i.e., those who haven't finished the test yet (because in this case, a corrector has to expect that those users will still change their entries, so judging the entries made so far might fall obsolete).
 
So, my suggestion is to review the filter and change the "(In)Active User Only" filter to a filter "(In)Active Participants Only" that covers all cases where participants have started the test but didn't finish it yet, meaning that either:

• The "Finish Test" button has not been clicked in a test run and/or
• There are still test runs left they could take.

2 Status

• Scheduled for: Not scheduled yet (will be set by Jour Fixe)
• Funding: Required
• Maintainer: (will be set by Jour Fixe)
• Implementation of the feature is done by (company, developer)
• Contract settled: No
• Tested by / status: tbd

3 Additional Information

Contact the following persons if you want to know more about this feature, its implementation or funding:

• Information about concept: Florian Suittenpointner (suittenpointner [at] qualitus [dot] de
  
• Information about funding: tbd
• Information about implementation: tbd

4 Discussion

BH 03 Nov 2014: I fully second the explanations of Florian.
 
I thought the active/inactive status relates to the fact wether a participant is active/inactive within the corresponding test all the time. When I had a look to the corresponding code I noticed that this active/inactive status relates to the active/inactive status of the user in general. I cannot imagine that any situation requires this filter. As Florian mentioned, users, who are inactive in general should be hidden implicitly.
 
What about filtering inactive users, that aren't scored yet? When it is really important to have the possibility to filter the general active/inactive status of users, this filter should not be mixed up with a filter comparing the fact of (not) done scoring.

5 Implementation

...