Buildstats

The buildstats utility updates database statistics. We can use buildstats for all of the Recommendation engines except for the Item Affinity Engine.

When you install the LikeMinds utilities, the installer sets buildstats to run once a day, at 3:30 a.m. This is because the best time to run buildstats is daily, at a time when the LikeMinds server receives relatively little use. The buildstats utility connects directly to the LikeMinds database and processes the transactional or ratings data that is constantly being written to the LikeMinds database. Because this utility does not consume many resources, it is typically installed on the same machine as the LikeMinds server. buildstats performs a number of data analysis functions on the information in the LikeMinds database and persistently writes out the results into the LikeMinds schema. However, the functionality of this and the number of functions to test differ depending on the type of LikeMinds engines in use. If both a Preference and ClickStream are in use, buildstats will, by default, analyze both the ratings and the transactional data.

For ratings data, buildstats writes to the following fields in the Lps_Item_Data table:

• num_rtg: Total number of ratings for the item.

• total_rtg: Sum of all ratings for the item.

• total_square_rtg: Sum of the squares of all ratings for the item.

• ratability: Priority for an item's presentation to users for rating. Ratability is non-negative value. Higher numbers indicate a higher priority for rating.

• score: Popularity or unpopularity of an item. If you prefer to have the own applications update this field, we can disable buildstats from writing to score.

For transactional data, buildstats writes to these fields in Lps_User_Trx:

• value: Data value associated with the transaction.

• adj_count: Adjusted count of transactions. If a new activity is recorded in the transaction table, this value increases. It may diminish over time.

Parent: Use the LikeMinds utilities