New version up in my sandbox

New modules are up. Lots of changes to cre. Including new table name and new table format. It is setup now to be able to recommend any content(user, comments, developer defined, nodes).

And I would also like to pose a question for discussion....

When recommending some piece of content (whether a node, comment, user etc...) does the alogrithm only recommend based on content that is the same type? so when recommending a node, only use similarity matrix referencing content that is both the same type. Thats not making much sense typing it out but here is an example.

Johny is a user. The site is recommending both nodes and users. The block for 'Johny's recommended users' should be populated based only similarities between user and user votes or similarities between BOTH user to user and user to node. Should this be up to user level module (node_recommendation)?

So the new cre_similarity_matrix (new name btw. Like it tons better) would have two additional fields content_type1, and content_type2. Or if we do not want to do similarities between both user and user and user to node, then it would have one additional field, content_type, that would hold the content_type of both content_id1 and content_id2.

Here is the new table structure to help clear up this cryptic message....
db_query("CREATE TABLE {cre_similarity_matrix}(
content_id1 int(10) NOT NULL DEFAULT 0,
content_id2 int(10) NOT NULL DEFAULT 0,
content_type1 varchar(20) default NULL,
content_type2 varchar(20) default NULL,
count int(10) NOT NULL DEFAULT 0,
sum int(10) NOT NULL DEFAULT 0,
PRIMARY KEY (content_id1, content_id2)
) /*!40100 DEFAULT CHARACTER SET utf8 */;");