Huge Collections of Software Manuals and Knowledgebase

GreatManuals.com
Huge Collections of Software Manuals and Knowledgebase

 
Home Contact Us Request to publish your help manuals Request to remove your help manuals
Introduction
» Metamation
» Login Security
Main Metamation Screen
» Main Metamation Screen
» Navigation Area
» Alerts & Tasks
» My Documents
» My Nodes
» My Data
» Metrics
» Work Frame
» Header Bar
» Maximise/Minimise On Screen Lists
Document Storage & Processing
» Document Storage & Processing
» Defining Documents
» Checking Out Documents for Amendment
» Document Check In
» Document Watching
» Viewing Document History
» Document Approval
» Document Scanning
Data Table Processing & Content Viewing
» Data Table Processing & Content Viewing
» Data Grid Data Entry
» Data Table Sheet Layout
» Sub-grid Processing
Metamation Nodal
» Metamation Nodal
» Metamation Node Maintenance
» Nodal Structure Linking
» Child/Parent/Sibling Nodes
» Node Status Reporting/Requesting
Meta Table
» Meta Table
» New Data Table
» Table Column
» Excel
» MS Project
» ODBC
» Table Form Layout
Searching for Information
» Performing Advanced Searches
» Performing Quick/Specific Item Searches
» Search Results Displayed
Maintenance, Help & Support
» Grant Maintenance
» Using This Help
» Acess via Remote Web Workplace & Internet
» Metamation Support
» Touchstone Systems Limited
» Interfaces
 

Child/Parent/Sibling Nodes

Child Nodes

Storage Nodes are defined either by creating children in the properties of existing nodes (where nodes are selected from the My Nodes panel of the home page), from the graphical nodal display window , or from the new button against the My Nodes in the same home page.

Child nodes are new storage nodes which area created in a structure from a parent node. Unless specific access is set to remove access to the child node, any user who can access the parent node will be automatically access the child node created.

data recovery ipod undelete mobile sms data retrieval
windows vista restore data recovery freeware restore deleted folders
xd card data recovery notebook data recovery restore files

When data is added to the child node which has metrics defined, the child node metrics will automatically be rolled up into the parent level for analysis and reporting in the metrics display.

When a new child node is created either from within the GUI nodal display or another nodes properties window , a pop-up window will appear allowing a new child to be defined as follows:

Child

Within this pop-up window, the entries available are as follows:

Description: A short description to describe the node, project, document store etc
Node Type: The type of node (used for filtering) can be selected from the drop down list of active node types.
Owner: This is the owner of the node. When creating a new node, this is you, but you can specify somebody else from the drop down list of users to own the node. When you specify somebody else, they will be alerted that they now control the node.

Parent Nodes

Storage Nodes are defined either by creating children in the properties of existing nodes (where nodes are selected from the My Nodes panel of the home page), from the graphical nodal display window, or from the new button against the My Nodes in the same home page.

Parent nodes are storage nodes which have children. Accessing a parent node automatically allows access to children nodes including the children's documents and data. To remove child access, specific access must be set to remove access to the child node.

A parent node may also be a child itself to its own parents.

Sibling Nodes

Storage Nodes are defined either by creating children in the properties of existing nodes (where nodes are selected from the My Nodes panel of the home page), from the graphical nodal display window, or from the new button against the My Nodes in the same home page.

Siblings nodes are nodes which have been linked as siblings. Siblings allow documents and data to be shared. Any user who can access a node will automatically be able to access documents and data in sibling nodes. However, unlike child nodes, this shared access does not extend to the siblings children or other siblings.

Home | Contact Us | Request to publish your help manuals | Request to remove your help manuals