Record and allow reporting on empty lists, course or modules, or missing parts of the hierarchy
This will allow customers to detect dead ends for users and take action outside the system boundary to rectify.
Later we could think about what activities could occur within the system boundary, e.g. request a list, email notification etc.
We have now created a new tenancy stats prototype, and we’ll be demoing it at the user group meeting on the 4th March. We have included the ability to report on empty nodes/modules, empty lists and also orphaned lists (i.e. those not attached to a module). There is also some basic stats reporting such as the amount of total lists in the system and the spread of resource types across the system.
Richard Cross commented
Without 'dynamic hierarchy updating' it seems to me really important that administrators can report on the gaps and mismatches in the Tenancy, without that we're administrating blind