Create a Hierarchy

To create a Hierarchy for a repository:

  1. Open the repository’s Hierarchy/Taxonomy Sidebar (see Open a Hierarchy or Taxonomy in the Hierarchy/Taxonomy Sidebar).

    Hierarchy/Taxonomy Sidebar

  2. Click the Add button on the Hierarchy/Taxonomy Sidebar’s Activity Bar.

    The Add Button on the Hierarchy/Taxonomy Sidebar's Activity Bar

  3. An Add Hierarchy editor will appear.

    Add Hierarchy Editor

  4. The Add/Edit Hierarchy window opens on the Details page. The configuration options are:
    • Name: (Required) The name of the Hierarchy.
    • Description: (Optional) A description of the Hierarchy.
    • Hierarchy Folder: (Required; cannot be changed once set.) A folder to store the Hierarchy. The folder must be already created before attempting to create a Hierarchy. If the Hierarchy folder is not specified, an error may be generated when you attempt to save the Hierarchy.
    • Properties Repository: (Optional) A repository to hold Hierarchy properties; can be used instead of managing properties in the Property page of the Edit Code Set window (the next page).
    • Path Code: The manner in which the Hierarchy node’s path is stored. For more information, see EnterWorks 10 Basics.
    • Path Format: Specifies the format of how the path is stored:
      • Delimited: Node names are separated by a period.
      • Fixed: Node names are known by their position in the path.
    • Source: (Required.) The source of the codes and descriptions:
      • Detail Editor: You will enter the node levels on the Add/Edit Hierarchy editor’s Levels page.
      • From an Existing Set: The codes will be copied from an existing Hierarchy or Code Set.
      • Import from a file: The codes will be imported from a file.
      • Auto-build from Selected Attributes: The Hierarchy will be automatically populated.
    • Include Owner: If selected, an additional column titled User will appear. A check in this column means that only the user defined as the owner of the code value will have edit permission to item data containing that value.
    • User: The user name of the owner. If Include Owner is checked, this field is required.
  5. Select Next to move to the Property page.

    Edit a Hierarchy's Properties

  6. Properties are optional. They are custom metadata fields that can be added to a Hierarchy. The configuration options for properties are:
    • Property Name: (Required) The name that will appear as the header of the property’s metadata column.
    • Datatype: (Required) The data type of the property’s value.
    • Default Value: (Optional) A default value for the property.
    • Code Set: (Optional) If the property values are drawn from a Code Set, select the name of the Code Set to be used.
    • Display Order: (Optional) Indicate the order the properties will be displayed.
  7. After any properties have been edited as desired, click the Next button to go to the Levels page.

    Edit a Hierarchy's Levels

  8. The levels defined here are what determines the “depth” of your Hierarchy tree. For instance, if you define three levels, your Hierarchy will have a parent level, child level, and grandchild level.
    • To add a level, click on the Level Name field and enter the name of the level. After you enter the Level Name, the button will appear to the right of the Filler Value.

      • Click the button to add your level to the Hierarchy definition and to open an editor for the next level.

    • To remove a level, click the button to the right of the Filler Value.
    • If the Hierarchy’s path is Fixed, the number of characters in the Level Name must be specified.
  9. When the Hierarchy configuration options have been edited as desired, click the Save button to save the Hierarchy, or click the Cancel button to exit without saving the Hierarchy.
  10. The display will revert to the Repository View’s Hierarchy/Taxonomy Sidebar. If a Hierarchy has been added, it should appear. If the new Hierarchy does not appear, clear the cache, (see Clear Data Cache ), and/or click the Refresh button.
  11. The new Hierarchy does not yet have nodes defined.
    • Selecting the new Hierachy will not change the display of records until nodes have been defined and records assigned to those nodes.
    • The new Hierarchy must be configured with at least one node before it can be managed in the Hierarchy Manager. For directions on configuring the new Hierarchy, see the EnterWorks 10 Administration Guide.
  12. After the Hierarchy has been created, saved, and configured, it can be accessed in the Hierarchy/Taxonomy Sidebar by selecting it from the Hierarchy/Taxonomy dropdown list. The new Hierarchy may be at the bottom of the list.

    The New Hierarchy

For instructions on adding nodes to a hierachy after it has been created and configured, see Add Hierarchy Node.