Home > Data Mining Algorithms > Anomaly Detection > Anomaly Detection Viewers a... > Association > Data for AR Models
Association Rules is normally used with transactional data, but it can also be applied to single-record case data (similar to other algorithms).
Association does not support text; see Text Mining in Oracle Data Mining.
Native transactional data consists of two columns:
Case ID, either categorical or numericalItem ID, either categorical or numerical
Transactional data may also include a third column
Item value, either categorical or numerical
A typical example of transactional data is market basket data. In market basket data, a case represents a basket that may contain many items. Each item is stored in a separate row, and many rows may be needed to represent a case. The Case ID values do not uniquely identify each row. Transactional data is also called multi-record case data.
You specify the following when you build an Association model:
Item ID is the name of the column that contains the items in a transaction.
Item Value is the name of a column that contains a value associated with each item in a transaction. The item value column may specify information such as the number of items (for example, three apples) or the type of the item (for example, macintosh apples).
The default value for Item Value is <Existence> (that is, is one or more item identified by Item ID is in the basket).
If you select specific value for Item Value, you may have to perform appropriate data preparation. The maximum number of distinct values of Item Value is 10. If the specific value for Item Value is greater than 128, bin the attribute specified in Item Value using a Transform node.
For more information, see the discussion of Market Basket data in the Oracle Data Mining Application Developer's Guide.