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

Managing hierarchies

Managing hierarchies

You can create hierarchies to show hierarchical relationships between code values in multiple code lists. A hierarchy consists of two components: the hierarchy model and the hierarchy tree. In the hierarchy model, you define the top-level code list and add relationships to other code lists. Then based on the hierarchy model, you can create the hierarchy tree and define relationships between the code values in the code lists.
For example, you might create a location hierarchy. First, you define the hierarchy model. You define the Region code list as the top-level code list. Then you create a parent-child relationship from the Region code list to the Enterprise Country Codes code list. Based on this hierarchy model, in the hierarchy, you create a hierarchy relationship from the North America code value to the United States code value. You create a hierarchy relationship from the North America code value to the Canada code value.
To create and manage hierarchies, perform the following actions:
  1. In
    Reference 360
    , create the hierarchy asset and define the hierarchy model. For more information, see Creating hierarchy models.
  2. Use the List hierarchies REST API to retrieve all hierarchies.
  3. Use the List hierarchy model relationships REST API to retrieve the relationships in a hierarchy model.
  4. Use the Import hierarchy relationships REST API to import relationships in a hierarchy tree.

0 COMMENTS

We’d like to hear from you!