Application Layout

=Application Layout=

Applications (starting with PubMan R4) will appear in a new application layout. The common layout is based on a horizontal menu set.



Header Section
The header contains all persistent elements. A short header is still not defined as a component for R4 (used in FACES and VIRR based on GUI 1.8).

Component: Skip Link Navigation

Used to meet accessibility requirements.

Component: The Meta Menu and the logo alternate

It is a horizontal, persistent menu which did not change, except in colours and style compared to GUI V1.8. As some Solutions already make use of a short header there is a second component (short header).

In addition to the logo there is a possibility to change/add graphical details to the logo (Seasonal stuff).

Component: The Search Menu and the Logo

The eSciDoc project logo is placed here, and can be customized using LAYER 3 - the vendor specific CSS with:


 * Varieties of solution specific logos
 * Institute related logos
 * Logos in combination with visuals

Simple search did not change, except in colours and style compared to GUI V1.8.

Component: Main Menu

It is a horizontal, persistent menu replacing the main menu of GUI V1.8. The main menu has one level and does not change within one workspace. This is sufficient for all roles and existing functionality.

Content Section
The content area contains all content and related actions or information.

Action Menu/Content Menu

The sub menu is not necessarily a second level of the main menu. It is a temporary menu, depending on user role and the current page displayed (e.g. Sorting, Display type, ...). If necessary the menu can offer two levels.

Breadcrumb

Dependent on the outcome of breadcrumb concept the area is offered here.

Title

The title is similar to the title used in GUI V1.8. It is not used to display metadata like item title, genre or physical page names. It contains short and clear names of functional areas, meaningful to the user.

WS

Role dependent eSciDoc components do appear differently depending on roles. The content area therefore has an exclusive part for workspace related elements (e.g. Item status). Any components that contain WS relevant elements should make use of these areas if possible.

Main Content

e.g. Items, Lists, ...

Public Repository
The public repository does not show areas defined for workspaces.



Workspaces
After a user has logged in to the system, a starting page with existing workspaces will appear. The start page informs the user:


 * What role he is in
 * What can be done with the priviledges of the role
 * Any other roles PubMan offers

At this point in time the menus change and all functionality is available. If possible the user should be able to decide if the page is always shown after login or on demand.



From the workplace start page the user enters his workspace and gets additional areas (e.g. Item Status)



Look and Feel
Additionally the look and feel is different from PubMan R3. The image above shows an example of how it might look. The application is now designed on component level and not on page level. The final appearance of a page depends on the components working together. Vertical spacing is subject to change. Most components are in work now and will be introduced separately.