Creating a View

A View is a read-only extract of a Dataset.  Views can be used for analysis and visualization, but the underlying data cannot be edited.  Views enable dataset integrity to be maintained.

Multiple views can be created from the same Dataset.  The illustration below shows the scope of different Views created from the same dataset:

1. The full dataset:  every property (column) and every node (row) is included.
2. Defined subgroups:   only the nodes (rows) which are in a defined subgroup are included.  Every property is included. 
3. Specified properties:  only specified properties are included (e.g., sensitive personal data is excluded).  Every node (row) is included.
4. Defined subgroups and specified properties.  only the nodes (rows) which are in a defined subgroup, and only specified properties are included.

How to create a View

Note: 

1. If the view being created is to be based on a subgroup of the organization (example ‘b’ in the illustration above), the properties used to define subgroups must be tagged ‘aggregate’.
2. If ‘Ghost nodes’ are to be included in the View, the parent ID property must be tagged ‘index’.  ‘Ghost Nodes’ are outside the defined scope of the View but included to maintain the organizational hierarchy.  You can specify which property values are included for ghosts. 

In the following example, a View is created for the R&D function, with the Salary property excluded.  The starting dataset has:

1. 381 people overall.
2. 143 in the R&D Function.

In Workspace with the ‘Datasets’ tab selected:

1. Select the icon for the dataset which the View will be created from.
2. Select ‘Create View’.

This starts the Create View wizard.

3. Enter a name for the View.
   1. Enter a description (optional).
   2. Provide any tags (optional).
   3. Specify whether a Draft is to be created to accompany the View.  (Because Views are read-only, an accompanying Draft provides users with the ability to model changes.  See Views and Drafts explained). 
      A separate article explains how to create a Draft.  In this example the option is deselected.
4. Select ‘Next’.

5. Enter the User Groups which will have access to this View.  In this example the ‘OD’ and ‘R&D’ User Groups will have access.
   Ignore the ‘modify access’ and ‘manage access’ fields.

6. Specify whether to ‘Hide’ of ‘Show’ individual properties.  In this example, the ‘Salary’ property will be hidden.
7. Select ‘Next’.

• If the scope of the View is to be limited to specific nodes (organizational subgroups):

8. Select the property which defines the subgroup (in this example, ‘Function’ is selected).  Only properties with the tag 'aggregate' will be available to select.
9. Select the property value for the selected property (in this example, ‘R&D’ is selected).

10. If required, select the option to 'Show Ghost Nodes in the view'.  ‘Ghost Nodes’ are outside the defined scope of the View but included to maintain the organizational hierarchy.  If this option is required, the Parent ID property must be tagged 'index'. 
11. If Ghost Nodes are to be shown, specify which properties will be included for these cases.  It's typical to include only properties required to label 'ghosts' and maintain the hierarchy.
12. Select ‘Create’.

The View can now be seen:

1. In Settings when the ‘Views’ tab is selected.
2. In Workspace when the ‘Datasets’ tab is selected and the card for the dataset it was created from is selected; and
3. In Workspace when the ‘Datasets’ tab is selected, and the list view is selected.

Selecting the View in Workspace (‘b’ or ‘c’, above’) triggers the opening of an existing pack, or the creation of a new pack with the View. 

The illustrations below show the slide presented at the start of this article after the same pack is opened with the newly created View:  

1. The scope is limited to positions in the R&D Function
2. The CEO is included as a ‘Ghost node’ to maintain the structure (in this example, the Chief Product Officer and the Chief Technology Officer are both in the R&D function and direct reports of the CEO)
3. No values are shown for the CEO position (based on the selection made at step X, above)
4. The ‘Salary’ property is not included in the View.  This property cannot be selected.
5. Property values cannot be edited. (Views are always read-only).

 
Related Articles:

• Creating a Draft
• Views and Drafts explained
• Orgvue Data Security
• Adding users to a tenant
• Assigning dataset permissions
• Applying property permissions
• See the effect of Permissions granted to Users