Creating data model objects

You can create data model objects such as specs, sub specs, hierarchies, catalogs, and lookup tables with IBM® InfoSphere® Master Data Management Collaboration Server. With GDS, you can upload or run a script to load the data model object.

A catalog is used for storing information about items. A hierarchy helps in categorizing item information that is stored in the catalogs.

For example, for abc company we can create a catalog named abc electronics items, a hierarchy named abc hierarchy electronics items, and categories named audio items, video items, audio video items, multimedia items, imported items, exported items.

Specs help in defining the format in which you want the data to be stored, calculated, and managed in the catalogs within the PIM solution.

A sub spec is a reusable spec which can be used as part of either a primary or a secondary spec, for example, to group together a set of attributes that always occur together.

Lookup tables are useful for quick information retrieval and for storing small amounts of data.

Views provide a more efficient or task-specific view of items, create groups of attributes that are related to a specific data entry or data maintenance process. You can create multiple views of the same catalog, and create views that are shared by multiple users.

You need to create the data model objects in the following sequence:

1. Create a spec
2. Associate a spec
3. Create a hierarchy
4. Create a catalog
5. Create a view

You can also create attribute collections, item relationships, lookup tables, and define location attributes.

An attribute collection is a group of item or category attributes that is associated or behave the same way in a given context. Attribute collections are used for workflow step validation and catalog and hierarchy views.

Item-to-item relationships are relationships between items. For example, you might have a relationship between the items in a bundle that are sold together for promotional purposes. Item-to-other-entity relationships can be between an item and any other entity, such as a supplier, a customer, or a location.

Location attributes store data that is specific to particular locations. For example, an item that is available for sale in California might require Prop 65 warning information.