history_rec's Introduction
Browsing History Recommender ============================ Installation & Configuration ---------------------------- You need to install the Recommender API (7.x-6.x) module and Drupal Computing module before install this module. After installation, follow these steps to compute recommendations: 1. Go to admin/config/system/computing/recommender/history_rec to review the settings, and make changes if necessary. Note that the "Use accesslog table" option is only valid if you enable the "Statistics" module in Core. 2. Run Drupal Cron to feed data into recommender. 3. Go to admin/config/system/computing/list, and click "Browsing History Recommender" to add a computing command. 4. Compute recommendations using either of the following approaches: - Open a command line terminal and run "drush recommender-run". - Open a command line terminal and execute the Recommender Java agent. - Go to admin/config/system/computing/recommender and click "Run Recommender" (not recommended). 5. You can view the execution results at admin/config/system/computing/records. 6. Display recommendation results using the default Views. For more information about how the module works, please read the documentation of Recommender API. Technology Explanation ---------------------- This module uses Recommender API to compute recommendations, using the item-based collaborative filtering algorithm. The basic idea is that two items are related because users always browse them together, and items should be recommended to me because I have viewed other related items before. For more details about the algorithm, see the paper at http://portal.acm.org/citation.cfm?id=642471. Users browsing history data are saved either in Drupal's built-in "history" table, or in the "accesslog" table if you enable the "statistics" module in core. The "history" table tracks registered users browsing history on nodes in the past 30 days. The "accesslog" table tracks all users (including anonymous users) browsing history on any links on the site in the past X days. Regardless of which table you use, this module will dump data in its own table for the purpose of recommendation computation. The benefit of using "accesslog" table is that you can use browsing history data from anonymous users. Limitations ----------- This module is **not** able to: * Make recommendations for entity types other than "node". * Use "comments" as browsing history (the "boost comments" feature was in previous releases, but not yet added here).
history_rec's People
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.