Designing a Catalog Hierarchy Model

The Catalog Hierarchy determines how catalog items are organized and displayed to users.

• The Catalog Hierarchy is made of different categories, shown below in blue, with some category levels assigned with commodity codes.

• Items, shown in yellow, will fall into categories with matching commodity codes.
• Note that the same item may fall under two different categories if those two categories have the same commodity code assignment.

The Catalog Hierarchy Editor is available under Core Administration ﹥ Catalog Manager, and allows you to view, add, delete, rename, and reassign commodities to hierarchy nodes.

• A category that has categories within it
• Folders have Leaves

• Category with no further subcategories

• Leaves have classification codes

You must rebuild the catalog index when making the following changes to the catalog hierarchy:

• Add a new folder or leaf

• Delete a folder or leaf

• Modify a folder or leaf (change the commodity code)

• Use Catalog Manager =﹥ Index Builder

• By default all categories in the catalog hierarchy are translated into supported languages.

• If you add a new folder or leaf to the hierarchy, you must manually translate the entry into a language of your choice.

• If the commodity code of an item does not match a value defined in the catalog hierarchy, the system will either -

  • Map the item to Uncategorized Items if the commodity code is defined in the system.
  • Use wildcarding to map the item to a parent value in the catalog hierarchy if one exists, even if the item’s commodity code value is not defined in the system.

• Example – Commodity code 44122004 will map to a leaf node in the hierarchy that has a value of 441220, 4412, 44, or Uncategorized Items.