The Management Information Dashboard (MI Dashboard) - List Coverage is designed to help you quickly establish which Schools, Faculties or Departments within your institution are engaging well with Talis Aspire, and where increased engagement activity may be necessary. This is of benefit to all institutions, but particularly if you are new to Talis Aspire and are looking to roll out the system, as you can identify where reading lists have quickly been adopted, and look to build on that practice with other departments.
The chart is a visual representation of the different nodes within your hierarchy. Each of the circles within the chart represents a node within your hierarchy, gradually branching out from the centre which marks your institution. The size of the circle represents the coverage of lists within that node so for example, a department where all modules have a list will appear larger than one where only half the modules do. Hovering your mouse over a circle will also cause more detailed information about that node to appear.
To get the maximum value from the List Coverage MI Dashboard, it helps if you have a well-structured hierarchy in your tenancy, as a flat hierarchy where modules are simply linked directly to the institution node won't provide the level of detail you'll need to assess where list coverage could be improved. For more information on updating your hierarchy, do take a look at Hierarchy - upload full process.
The raw data which drives the chart is also available to you from this screen and is fully exportable. The export contains exactly what's on screen. Access to the data is also available through Advanced MIS if you wish to use it outside of Talis Aspire, or to combine with other datasets.
What order does the table use?
Hierarchy nodes with the most list coverage will appear at the top of the screen.
Why do the total lists differ from my all list items report for Published, Published with unpublished changes and draft?
If individual lists are attached to multiple nodes (course, units or modules) on the List Coverage chart and data these are counted against each node they are attached to, lists can be attached to any node, these may appear under multiple branches of the hierarchy tree.
How come the list coverage percentage at Faculty level is lower than it's constituent parts?
The percentage coverage is measured at the percentage of childless nodes that have at least one list attached (this chart does not show those that haven't). For example is Node: ABC has 28 children, of those 28 children only 23 of them have at least one list, this means that the percentage coverage is 82%. The child nodes of ABC show at 100% because they have no children without a list attached.