Table of Contents

Search

  1. Preface
  2. Introducing Reference 360
  3. Getting started with Reference 360
  4. Manage system reference data
  5. Manage reference data sets
  6. Manage code lists
  7. Manage code values
  8. Manage crosswalks
  9. Import data
  10. Manage hierarchies
  11. Manage attributes
  12. Manage workflows
  13. Manage jobs
  14. Reference 360 REST API
  15. Glossary

Reference 360

Reference 360

Hierarchies

Hierarchies

After you create reference data sets, code lists, and code values, you can create hierarchies. A hierarchy shows how code values are related to one another. You can arrange code values above, below, or at the same level as other code values.
Code values in a hierarchy are top-level nodes or child nodes. Each hierarchy must contain at least one code value as the top-level node. Top-level nodes are code values at the highest level in a hierarchy and don't have any code values above them. Child nodes are arranged below other code values and can have other code values below them.
The hierarchy relationships that you can create depend on the hierarchy model. A hierarchy model consists of hierarchical relationships between code lists. You define a code list as the top-level code list and then define levels by adding code lists and relationships between the code lists. Then based on the hierarchy model, you can add code values as nodes in the hierarchy.
For example, your organization needs to track country codes by regions. You might create the following hierarchy model:
  1. Create the Locations hierarchy asset.
  2. Add the Regions code list as the top-level node.
  3. Create a relationship from the Regions code list to the Enterprise Country Codes code list.
The following image shows a sample hierarchy model:
The hierarchy model displays the Regions code list as the top-level node with a relationship to the Enterprise Country Codes code list.
With the hierarchy model defined, you might create the following hierarchy:
  1. Add the North America code value as the top-level code list.
  2. Add the USA code value as a child node of the North America code value.
  3. Add the Canada code value as a child node of the North America code value.
The following image shows a sample hierarchy:
The hierarchy displays the North America code value and South America code value as top-level nodes. The North America code value contains child code values, including Canada and USA.
The relationship between the code values in a hierarchy are termed as related code values.
For example, in the preceding sample hierarchy, the Regions code list contains two code values, such as North America and South America; and the Enterprise Country Codes code list contains two code values, such as Canada and USA. In the hierarchy model, the hierarchical relationship connects the two code lists, and the code values in the parent and child code lists are related to each other.
You must be assigned the Planner role to work with hierarchies. For more information, see Users, groups, and roles.

0 COMMENTS

We’d like to hear from you!