Multi organizational view

Here is a main enhencement proposal. The design is not completed...

Purpose

The purpose is to allow to organize data in different ways. By example, as you build a plan you can organize data according to the timeline of action realization but you can also want to separate action according to organizational units responsible of the realization of the actions.

The secondary view enables to create a hierachy in a special characterisitic (stakeholders in our case).

What it looks like

......

On the left screeshot : the main view that organize data according to timeline.

On the rigth screenshot : the secondary view base on stakeholders organization. All the main view leaves are displayed and additional branch are deduced from main treeview.

Key design elements

• Views should be restrain to choicelist field
• Building a view implies to identify leaves and branches in the main treeview because manipulations on the main view should have impacts on secondary view according to this classification
• Secondary view includes all leaves of the main view and specific branches. Data are unmodifiable except the characteristic of the view.
• Building a secondary view implies that the fieald on which the view is built becomes unmodifiable in the main view.

Main view management impacts:

• Drag a leaf element to consider this element as a detail of another leaf drive to suppress the leaf that becomes a branch in the secondary view
• Drag all the leaves of a branch drive to add the branch that becomes a leaf in the secondary view

Secondary view management impacts:

• Add an action implies to add a data record
• Drag a leaf to become a branch implies to erase the data record

One step beyong...

• Transform secondary view into main view ?