Management Center: Options for managing attributes

Options for managing attributes
The attribute dictionary in Management Center provides a flexible, alternative method for managing attributes within a store catalog. Before starting to use the attribute dictionary in Management Center, review the available options for managing attributes.
Note: IBM recommends to use Option 1. If the site currently uses Option 2 or Option 3 and has the bandwidth available, we are recommended to migrate to use Option 1.

Option 1: Use the attribute dictionary in Management Center to manage attributes for catalog entries
The attribute dictionary in Management Center contains all of the features to perform the following tasks:

Assign or remove attributes for catalog entries.
Share attributes and attribute values across multiple catalog entries.
Create, assign, or remove values for predefined value attributes.
Create, update, and delete shared attributes and attribute values in a single location; cascade new attribute values through all catalog entries that use the shared attributes.
Assign multiple values to descriptive attributes for a catalog entry.
Support for managing storefront facets
Use attribute folders to group and organize attributes.
Use attributes as merchandising attributes for use in the Marketing tool.
Advantages of Option 1:

We can assign and save attributes that are contained within the attribute dictionary to catalog entries.
We can use attributes and attribute values that are contained within the attribute dictionary when we are generating SKUs.
We can create catalog filters by using attributes with predefined values that are contained within the attribute dictionary. We can use these attributes as filter conditions.
A Searchable flag used by WebSphere Commerce search is provided to indicate whether to index an attribute.
Easier identification of distinguishing attributes and shared attributes in similar products improves product comparisons.
Reduces maintenance costs for managing product attributes, helping to prevent incorrect attribute names and values from being associated with a product.
Reduces overall database footprint in attribute tables by reusing attribute data.
We can assign multiple values to descriptive attributes for a catalog entry.
Support for managing storefront facets
We can use attribute folders to simplify organizing and browsing for attributes in the attribute dictionary.
We can use attributes in merchandising. We can use these merchandising attributes in search filters for catalog entry recommendations in marketing activities to help Marketing Managers improve targeting shoppers with relevant recommendations. We can also use these merchandising attributes in search filters to create search rules that add or replace search criteria. We can use merchandising attributes in search filters for finding catalog entries to assign to sale categories and rule-based sales categories.
We can assign multiple descriptive attributes to multiple catalog entries at a time.
We can view the References tab for an attribute to view the catalog entries assigned the attribute.

Considerations for Option 1:
Consideration Action
We cannot add defining attributes that are contained within the attribute dictionary to a catalog entry that already has defining attributes that are not contained within the attribute dictionary. Delete defining attributes that are not contained within the attribute dictionary from the catalog entry. We can then add defining attributes that are contained within the attribute dictionary to the catalog entry.
We cannot add non-attribute dictionary attributes to catalog entries that do not have any attributes. We can only add non-attribute dictionary attributes to a catalog entry if that catalog entry already has at least one non-attribute dictionary attribute. If you remove all non-attribute dictionary attributes from a catalog entry, we must use attribute dictionary attributes for that catalog entry. Assign attributes that are contained within the attribute dictionary to catalog entries.
We must use attributes from the attribute dictionary when you create new products. Create an assigned value attribute and add it to a specific product. Then, supply a unique assigned value for the attribute.
We cannot view, manage, or use attributes that are contained within the attribute dictionary in WebSphere Commerce Accelerator. Use Management Center to view, manage, and use attributes that are contained within the attribute dictionary.
We can assign multiple values for a descriptive attribute for a catalog entry and display the multiple values on the storefront. Add multiple descriptive attribute values without replacing existing values.
Note: If the site is configured to support multiple value attributes, when loading values for a descriptive attribute with the Catalog Upload feature, we are loading multiple values. The loaded values are added to existing attribute values. The loaded values do not replace existing values. To replace existing values with the newly loaded values:

Include the existing value to replace in the input file that we are loading and set the existing value to be deleted.
Have an administrator configure your load process to separate the load processes for loading attribute value information. With this configuration, we can load information about multiple value attributes in one input file and load information for single value attributes in a different file. This configuration ensures that when loading a value for a single value attribute, the existing value is replaced with the new value.

Manage storefront facets by marking attributes for use in faceted navigation Select attributes as for use in faceted navigation so that products with similar attributes are grouped. For example, products that are grouped by brand or price, or by other selectable facets from the storefront left sidebar.
The attribute and value descriptions must be available in the store default language. If you change the store default language, we must ensure that the attribute and value descriptions be available in that new default language.
Tip: If you plan to use only the attribute dictionary in Management Center to manage attributes, we can hide all attributes that are not contained within the attribute dictionary.

Option 2: Continue to manage attributes individually for catalog entries
If the store does not contain attributes that are shared across multiple catalog entries, we are not required to use the attribute dictionary in Management Center. We can continue to manage attributes in Management Center specific to a single catalog entry.Advantages of Option 2:

We can create attributes and attribute values for individual catalog entries in Management Center.
You do not have to change how you currently manage attributes for catalog entries.
You do not need to perform any additional migration to use this attribute model.
We can efficiently manage catalogs that contain attributes that are not common across catalog entries.
Considerations for Option 2:

The advantages of using the attribute dictionary are not available to you for managing the catalog entry attributes. These advantages are listed as the advantages for using Option 1.
This method is efficient only for catalogs that contain less than 50 distinct attributes and attribute values assigned to products.
When we are managing attributes within individual catalog entries, changes made to an attribute affect only that specific attribute and the catalog entry that uses it. These changes are not applied to similar attributes for other catalog entries.

Option 3: Use the attribute dictionary in Management Center and manage attributes individually for catalog entries
To use the attribute dictionary in Management Center, but do not want to initially convert your entire catalog to use attributes that are contained within the attribute dictionary, we can manage attributes by using both the attribute dictionary and individual catalog entries.Advantages of Option 3:

You do not have to convert your entire catalog to use attributes that are contained within the attribute dictionary. Products retain their current attributes and attribute management methods. Because of this retaining of attributes and methods, we can migrate the catalog attributes into attributes that are contained within the attribute dictionary in stages.
Efficient for catalogs that have both catalog entries with attributes that are not common across catalog entries, and catalog entries that have attributes that are common across catalog entries.
We can keep your existing attribute data as is. We can use the attribute dictionary to share attributes and to take advantage of other attribute dictionary features, such as multiple values for descriptive attributes or support for managing storefront facets.

Considerations for Option 3:
Consideration Action
We cannot add new attributes within new catalog entries. Add attributes to new catalog entries from the attribute dictionary.
We cannot add new attributes for catalog entries that do not already have attributes. Add attributes from the attribute dictionary for catalog entries that do not already have attributes.
We cannot add defining attributes that are contained within the attribute dictionary to a catalog entry that already has defining attributes that are not contained within the attribute dictionary. Delete defining attributes that are not contained within the attribute dictionary from the catalog entry. We can then add defining attributes that are contained within the attribute dictionary to the catalog entry.

Related concepts
Catalog Upload

Related tasks
Manage attributes
Use the attribute dictionary
Use catalog entry attributes

Consideration	Action
We cannot add defining attributes that are contained within the attribute dictionary to a catalog entry that already has defining attributes that are not contained within the attribute dictionary.	Delete defining attributes that are not contained within the attribute dictionary from the catalog entry. We can then add defining attributes that are contained within the attribute dictionary to the catalog entry.
We cannot add non-attribute dictionary attributes to catalog entries that do not have any attributes. We can only add non-attribute dictionary attributes to a catalog entry if that catalog entry already has at least one non-attribute dictionary attribute. If you remove all non-attribute dictionary attributes from a catalog entry, we must use attribute dictionary attributes for that catalog entry.	Assign attributes that are contained within the attribute dictionary to catalog entries.
We must use attributes from the attribute dictionary when you create new products.	Create an assigned value attribute and add it to a specific product. Then, supply a unique assigned value for the attribute.
We cannot view, manage, or use attributes that are contained within the attribute dictionary in WebSphere Commerce Accelerator.	Use Management Center to view, manage, and use attributes that are contained within the attribute dictionary.
We can assign multiple values for a descriptive attribute for a catalog entry and display the multiple values on the storefront.	Add multiple descriptive attribute values without replacing existing values. Note: If the site is configured to support multiple value attributes, when loading values for a descriptive attribute with the Catalog Upload feature, we are loading multiple values. The loaded values are added to existing attribute values. The loaded values do not replace existing values. To replace existing values with the newly loaded values: Include the existing value to replace in the input file that we are loading and set the existing value to be deleted. Have an administrator configure your load process to separate the load processes for loading attribute value information. With this configuration, we can load information about multiple value attributes in one input file and load information for single value attributes in a different file. This configuration ensures that when loading a value for a single value attribute, the existing value is replaced with the new value.
Manage storefront facets by marking attributes for use in faceted navigation	Select attributes as for use in faceted navigation so that products with similar attributes are grouped. For example, products that are grouped by brand or price, or by other selectable facets from the storefront left sidebar.
The attribute and value descriptions must be available in the store default language.	If you change the store default language, we must ensure that the attribute and value descriptions be available in that new default language.

Consideration	Action
We cannot add new attributes within new catalog entries.	Add attributes to new catalog entries from the attribute dictionary.
We cannot add new attributes for catalog entries that do not already have attributes.	Add attributes from the attribute dictionary for catalog entries that do not already have attributes.
We cannot add defining attributes that are contained within the attribute dictionary to a catalog entry that already has defining attributes that are not contained within the attribute dictionary.	Delete defining attributes that are not contained within the attribute dictionary from the catalog entry. We can then add defining attributes that are contained within the attribute dictionary to the catalog entry.