4.5 Dashboard

Dashboard is the nexus. It is the central hub for tracking down everything that is happening with the projet. THe dashboard yields itself to an interaction :

[Icon Fan Image]

This interaction as outlined in the overview part of this section allows for a consistent navigation pattern to explore all of NCLVerse

Notifications

Will be displayed on the icons this mwould be enabled by using websockets since websockets would allow for doing realtime updates and is much better than AJAX for polling. From a user's perspective this means that they can at a glance get to know where the activity is happening and hence make an informed decision. The ordering of the apps are to be determined in the order of most recent notification. One of the short comings of this view is that only a limited amount of apps can be displayed using this style, even though this can be exteneded with the helpo fo arrows a better extensible pattern is to be formed when the number of applications increase beyond.

Write about mobile considerations.

Another approach was but this was escheewed in favour of the currevt interaction as it seemed like a good metaphorical fit for the student as an astronaut in space metaphor that was invoked earlier.

What?

The frontend for all activity happening inside the NCLVerse.

Why?

Inform students about topic distribution and act as a consolidated archive for exam papers. Provide additional meta data over the existing Crypt exam vaults.

How?

Enables labelling of question papers.

When?

Mostly required during exam times.

For Who?

For students who are facing their exam. Acts as a prioritizer for their exams.

Design

A dashboard that invokes the metaphor mentioned. Cross link to the universe metaphor.

Cumulate all notifications then filter them based on the tag. Does a tree based navigation make sense here?