A node in DRM may be used to represent a cost center, a department, a product category, or any segment value in your chart of account.
It is the way how DRM stores information. It does not have the concept of entity or table. Data are stored as nodes.
A node can have many user-defined properties that stores information about the node.
It is the way how DRM stores attributes.
A node can be added to one or more hierarchies. A node can also be an orphan node that is not added to any hierarchy.
A node is created within a DRM version. A “version” is the container of nodes. It is important to understand the DRM version concept.
DRM uses these terminologies to describe node relationships:
I feel that they are useful”
- Leaf – A node that does not have children
- Limb – A node that can have children. Note that it does not have to have any child.
- Parent – It is referring to the node that is directly above another node
- Child – It is referring to the node that is directly below another node
- Ancestor – All nodes between a node and the top of the hierarchy (including the parent, the parent of the parent, and so on). Note that this is not a single node and a parent of a given node is part of the ancestor.
- Descendant – A node below a specified node (including children and children of children). Note that the difference between a descendant and a child is that a child is directly below the parent node.
- Sibling – All nodes that share a parent node in a hierarchy.
- Orphan – A node not assigned to a hierarchy
The above are general terms can be used to describe nodes in various systems that supports hierarchy.
These are DRM specific concepts:
- Global Node – A node within a version.
- Local Node – A node within a hierarchy.