Hi. I am the maintainer of the Node recommendation module (http://drupal.org/project/noderecommendation). I created that module because i wasn't finding something close to what was needed. I did check on CRE back then but we needed something particular but somehow flexible. I am now up to the task of porting that module to D6, however, I am wondering if I can help on some of the developing going on with this and CRE module.

I will test the module and check how far the functionality is from what we need and what that module does and report back, but I am also wondering if you can, by looking at my module, compare them from your point of view and your thoughts about considering merging any functionality with this and, if that's at all possible.

The main tasks of that module is to provide an easy interface for the site's admin (final client, not a developer) a somehow easy interface to administer recommendation and control how those recommendations are displayed. While I would have been able to build some of those with Views, D5 wasn't that flexible on that front. I am recently slowly switching to D6 and I know a lot of improvements have been made.

What the module is doing, is the following:
- Expose a new tab to the user allowing them to select on a per node configuration basis what should fed the recommendation block. The user can chooses to use the terms from the node, or even manually select what term should be looked at. It can also have a manual selection of nodes for a particular node. On top of this, he can select what order should this nodes are displayed, and it plugs with Ubercart to sort the nodes (products) according to some certain conditions (high margin, high stock, slow sellers). It does work w/o ubercart as well without those options.
- Besides the per-node configuration there's also a per-category default configuration in which, for a group of terms, you can apply a default recommendation logic for any node under those terms. This default will apply only if the node has no recommendation set of its own. The default works the same as the per-node configuration, allowing to chose terms from node, particular terms or manual nodes.

Thanks,
a.=

Comments

Scott Reynolds’s picture

Scott Reynolds commented

So this in combination with CRE should achieve the following:
1.) provide a clean way to configure how and which types can be 'recommended'
2.) scale by off-loading calculation to the database

Right now, they are in an odd state. They sort-of work but not all of it is complete. Until i get the stuff set up for the beta release: http://drupal.org/project/issues/search/similarity?issue_tags=similarity...

These seem like the features to start examining.

Because, both CRE and similarity use Views, so much of this is achieved just through the Views Interface.