Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS Design 214145"

(Design)
(Design)
Line 74: Line 74:
 
Each tab will contain a table that will show the contents of the node or edge.  There will be two version of the the table.  There will be a detail table and simple table.  The simple table will show a list of record meta data. Each row can expand to show the contents of the record.  The detail table will show all the information capture in the CMDBf response structure.   
 
Each tab will contain a table that will show the contents of the node or edge.  There will be two version of the the table.  There will be a detail table and simple table.  The simple table will show a list of record meta data. Each row can expand to show the contents of the record.  The detail table will show all the information capture in the CMDBf response structure.   
  
Tables that represent node content will be made of rows that represent a single record.  <b>Note that the table normalizes the <item> structure in the CMDBf query response to flatten the CMDBf graph structure</b>
+
==Simple Table Mockup==
  
Tables that represent edge content will be made of rows that represent a single record.  <b>Note that the table normalizes the <item> structure in the CMDBf query response to flatten the CMDBf graph structure</b>
+
[[SimpleCollapse.png]]
 +
 
 +
Simple view with rows collapsed
 +
 
 +
[[SimpleExpand.png]]
 +
Simple view with rows expanded
 +
 
 +
[[DetailCollapse.png]]
 +
 
 +
Detail view with rows collapsed
 +
 
 +
[[DetailExpand1.png]]
 +
Detail view with item rows expanded
 +
 
 +
[[DetailExpand2.png]]
 +
Detail view with record rows expanded
 +
 
 +
Tables that represent node content will be made of rows that represent a single record.  <b>Note that the table normalizes the <item> structure in the CMDBf query response to flatten the CMDBf graph structure</b>

Revision as of 02:06, 8 January 2008

Back to Data Reporting Design

Change History

Name: Date: Revised Sections:
Sheldon Lee-Loy 01/07/2008
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Design
Code
Test
Documentation
Build and infrastructure
Code review, etc.*
TOTAL

'* - includes other committer work (e.g. check-in, contribution tracking)

'** - documentation may span multiple release. Note an additional enhancement is associated with a programmer's guide (ER 210134)

Purpose

A simple generic graph response view is needed catered towards users that are not familiar with CMDBf schemas. This will allow end users to understand and analyze the data easier instead of trying to navigate an XML structure. This view will be used as a default view for the COSMOS UI. This view should be able to render the contents of any graph response in a generic way. There should be extension points to customize the specific contents of the graph response.

Requirement

A table is a likely generic view since users at a glance can determine the number of records in the graph response. A table can scale the cmdbf query response better than a tree since the graph response will most likely be root level heavy (i.e. the tree will contain a large number of root notes rather than many leaf nodes).

As a stretch goal a tool bar should be provided that provides filtering and searching capability. Searching capability may be complicated. Filtering capability can be the definition of a cmdbf query.

Design

Let us first consider the structure of the CMDBf graph response.

TO DO:add graph response pseudo schema from CMDBf 1.0 spec

As stated in the CMDBf 1.0 specification document the graph response is made up of <nodes> and <edges> elements. Each of these elements have an associated 'templateId' attribute that corresponds to the 'templateId' attribute used to construct the CMDBf query.

Creating a tab layout will improve the visualization of the node and edge elements. A tab can be constructed for each node or element. The title of the tab will correspond to the templateId. This will logically separate the edge and node contents. Color coding or icons can be used to distinguish between a node or edge.

Each tab will contain a table that will show the contents of the node or edge. There will be two version of the the table. There will be a detail table and simple table. The simple table will show a list of record meta data. Each row can expand to show the contents of the record. The detail table will show all the information capture in the CMDBf response structure.

Simple Table Mockup

SimpleCollapse.png

Simple view with rows collapsed

SimpleExpand.png Simple view with rows expanded

DetailCollapse.png

Detail view with rows collapsed

DetailExpand1.png Detail view with item rows expanded

DetailExpand2.png Detail view with record rows expanded

Tables that represent node content will be made of rows that represent a single record. Note that the table normalizes the <item> structure in the CMDBf query response to flatten the CMDBf graph structure

Back to the top