Skip to end of metadata
Go to start of metadata

Overall Design Principles for UI
Dominic 9.3.2012: I have done a little thinking on this. Please can i have comments. I have made a few changes to location of items.
This is for BVA comment but shows my thinking on providing the principles and structure for navigation.

Name Size Creator Creation Date Comment  
Microsoft Word Document Overall Design Principles for 491 kB Vladimir Alexiev Mar 12, 2012 11:37  

Overall Design Principles for UI – Stage 3


Author: Dominic Oldman


Date: 8 March 2012


Draft: 0.2 (unfinished)







1                 Navigation Flow and Aids


·        The user logs in to the system

·        They arrive at their dashboard


1.1           The main RS menu


·        This menu holds the main environment items. These are to do with leaving the project environment or initiating the main tools.


·        It also holds the menu item for initiating the data basket. The data basket is the only tool that operates within its own window rather than a tab. The data basket pops up on top of the ResearchSpace environment and can operate within all tool environments.


·        If the user starts the search tool from the main menu then a tab is opened. The tab gets focus and the user is confronted with the search screen.


·        If the user starts the data annotation tool the system will simply provide a warning that there is no object to annotate. Likewise for other tools that require a subject. The exception is the forum tool in which you can choose a forum once the tab is open. i.e. It can start without a forum selected.


1.2           The user can use dashboard links to open tools when they relate to a resource.


· The user can open the forum tab using the forums activity box. The forum tab is opened with an active forum ready to post to.


· The user can use an alert which has come about because of activity within a particular tool, For example an annotation has been made to an object. The activity alert provides a direct link, opening a data annotation tab with the object in question in focus.


· Lastly, the user can select something from the data basket. Again the environment or tool in which the data basket entry was made will provide a link back to that tool with the specific resource in focus.


1.3           The Tools Tabs


·        When tools are initiated and occupy a tool tab they can be removed using the X icon on the tab.


·        If the user has been in the middle of an operation within the tab then the user will receive a warning and given an opportunity to activate the tab and complete the unfinished operation.


·        Each tool should have its own close button.


·        Tools can be opened in more than one tab. For example, two data annotation tools which are operating on two different objects can be initiated. The user can switch between the two tabs.


·        A tool can have its own quick link to open another related tool using the same object  as the focus for that tool. For example, the data annotation tool can open the image annotation tool. Some tools also lend themselves to opening tools like the forum and search tool. This are described below.


·        It is possible that limits should be placed on the number of tool tabs that can be open at the same time.



2                 The Environment Menu


2.1           Project


The Project menu allows a user to switch between projects should they be a member of more than one. This may also provide some features for project wide user preferences.


2.2           Tools


All components, including platform infrastructure components, are treated as individual menu items with their own tab environments. This includes the document and image libraries that contain raw materials.


2.3           Username


This item allows displays the user’s name and allows the user to logoff the system , taking them back to the logon screen.


3                 The ResearchSpace tools tab




3.1           Dashboard


·        This is the only item on the tools tab that cannot be closed. The user should always be able to get back to dashboard.


·        The active item in the tool tab should be highlighted.


·        There should be an indication on the tab is there is modified data which has not saved.


·        The remove tab icon allows items in the tools tab to be closed.


·        Warnings should be issues when removing a tab that has unsaved data.


3.2           Tool Specific Tabs and Menus


Each tool will have its own set of functionality, tabs and menus.



4                 Tool menus and tabs

4.1           Data Annotation



5                 Search Screen




1.     A new search

2.     A pre-existing search


Blank Search Screen











Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.