Attribute definitions in the search space creation XML file

The general rule for adding these to a search space via the XML file used with the PACreateSearchSpaceBatchCmd scheduler command is as follows:

• For a base search space, the <columnName> is the English version of the value in the NAME column in the ATTRIBUTE table. The name must adhere to all rules imposed by the database for column names. In particular, the <columnName> cannot contain spaces. The <attrName> is the value from the NAME column for the language identified. This value is case sensitive.
• For a separate search space, the <columnName> is the English version of the value in the NAME column, with F_ prepended to it, for example, F_Size for Size. The name must adhere to all rules imposed by the database for column names. In particular, the <columnName> cannot contain spaces. The <attrName> is the value in the NAME column for the language identified. This value is case sensitive.

Product Advisor also supports a selection of attributes from other tables, such as CATENTRY and CATENTDESC, in addition to prices. The general rule for adding these to a search space via the XML file used with the PACreateSearchSpaceBatchCmd scheduler command is as follows:

• For a base search space, the <columnName> and <attrName> should be the column name from the base table. For example, use shortdescription for the SHORTDESCRIPTION column in CATENTDESC. This value is not case sensitive.
• For a separate search space, the <columnName> value can be found in the table below. The <attrName> is the column name from the base table. This value is not case sensitive.

The table below illustrates the selection of attributes supported beyond those in the ATTRIBUTE table. The italicized rows are mandatory when using the PACreateSearchSpaceBatchCmd scheduler command. Otherwise, the metaphors will not operate properly. This is true even if the attributes are not exposed to customers.