Use cases for configuration interface

In order for the block to be fully useful, it must be possible for a teacher to narrow down the items that are shown so that they only see work which they have been allocated to mark. The following cases are examples when this would be necessary. These example apply to both groups and cohorts unless otherwise specified.

• Teacher teaches a Moodle course with many groups, but only some groups are actually their classes. The other groups need to be hidden.
• Teacher teaches only part of a Moodle course to all of the students, so some activities need to be hidden.
• Combining the two options above: teacher is only allocated work for some groups and some activities (e.g. a single seminar within a large university course)

Some courses are very large, so the hassle of clicking through dozens of activity is significant, even though it is a one-time process. To ease this, course defaults need to be possible, so that a teacher can e.g. set everything to be hidden at course level and set a single activity to 'show' as an override.

Adding many complex settings can leave it difficult to work out what items have been shown/hidden at deeper levels of the tree. There needs to be an easy way for the overrides to be seen and reset if necessary.

There are two ways to show or hide things - at the start of term, before any work is submitted (when timetable allocations are made) and during term, when reorganisation is done. This implies that we need an overview of everything, as well as the ability to hide stuff on the fly from the actual marking tree e.g. via right-click context menus.