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

Step 2. Define the hierarchy model

Step 2. Define the hierarchy model

Define the top level node and then add child nodes to the hierarchy model. You can add flat and hierarchical code lists as nodes to different levels of the hierarchy model. For example, you might define the Enterprise Regions code list as the top level node. Then you create a relationship from the Enterprise Regions code list to the Enterprise Country Codes code list.
The following video shows you how to define the hierarchy model:
Define hierarchy model by adding code lists and defining relationships between the code lists.
  1. In the
    Properties
    panel, select a code list as the top level node for the hierarchy model.
    The undefined node name is replaced with the code list you selected.
  2. In the Hierarchy Designer, hover over the node and click
    Add Child
    .
    A child node appears in the Hierarchy Designer.
  3. In the
    Node
    field, select a code list to create a relationship.
    The following image shows a relationship from the top level node to the child node:
    The undefined node name is replaced with the code list you selected.
  4. Optionally, add additional child nodes.
  5. Click
    Save
    .

0 COMMENTS

We’d like to hear from you!