Skip to content

Commit e3d4f30

Browse files
committed
added documentation and test data
1 parent 5fbe929 commit e3d4f30

File tree

5 files changed

+102747
-0
lines changed

5 files changed

+102747
-0
lines changed
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
===
2+
Recommender
3+
===
4+
5+
The Recommender Operator utilizes advanced algorithms to provide personalized recommendations based on user behavior and preferences. This operator streamlines the data science workflow by automating the process of selecting the best recommendation algorithms, tuning hyperparameters, and extracting relevant features, ensuring that users receive the most relevant and effective suggestions for their needs.
6+
7+
Overview
8+
--------
9+
10+
The Recommender Operator is a powerful tool designed to facilitate the creation and deployment of recommendation systems. This operator utilizes three essential input files: `items`, `users`, and `interaction`, along with specific configuration parameters to generate personalized recommendations.
11+
12+
**Input Files**
13+
14+
1. **Items File**: Contains information about the items that can be recommended. Each entry in this file represents an individual item and includes attributes that describe the item.
15+
16+
2. **Users File**: Contains information about the users for whom recommendations will be generated. Each entry in this file represents an individual user and includes attributes that describe the user.
17+
18+
3. **Interaction File**: Contains historical interaction data between users and items. Each entry in this file represents an interaction (e.g., a user viewing, purchasing, or rating an item) and includes relevant details about the interaction.
19+
20+
**Configuration Parameters**
21+
22+
The Recommender Operator requires the following parameters to trigger the recommendation job:
23+
24+
- **top_k**: Specifies the number of top recommendations to be generated for each user.
25+
- **user_column**: Identifies the column in the users file that uniquely represents each user.
26+
- **item_column**: Identifies the column in the items file that uniquely represents each item.
27+
- **interaction_column**: Identifies the column in the interaction file that details the interactions between users and items.
28+
29+
**Functionality**
30+
31+
Upon execution, the Recommender Operator processes the provided input files and configuration parameters to generate a list of top-k recommended items for each user. It leverages sophisticated algorithms that analyze the historical interaction data to understand user preferences and predict the items they are most likely to engage with in the future.
32+
33+
**Use Cases**
34+
35+
This operator is ideal for a variety of applications, including:
36+
37+
- **E-commerce**: Recommending products to users based on their browsing and purchase history.
38+
- **Streaming Services**: Suggesting movies, TV shows, or music based on user viewing or listening habits.
39+
- **Content Platforms**: Proposing articles, blogs, or news stories tailored to user interests.
40+
41+
**Recommender Documentation**
42+
43+
This documentation will delve into these concepts comprehensively, showcasing how to utilize the versatility and adaptability of the recommender operator within the Python library module to build recommendation systems.
44+
45+
.. versionadded:: 2.11.14
46+
47+
.. toctree::
48+
:maxdepth: 1
49+
50+
./quickstart
Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
===========
2+
Quick Start
3+
===========
4+
5+
Install
6+
--------
7+
8+
Install ads using pip (shown below) or OCI Conda Packs
9+
10+
.. code-block:: bash
11+
12+
python3 -m pip install "oracle_ads"
13+
14+
Initialize
15+
----------
16+
17+
Initialize your recommender job through the ads cli command:
18+
19+
.. code-block:: bash
20+
21+
ads operator init -t recommender
22+
23+
24+
Input Data
25+
-----------
26+
27+
Within the ``recommender`` folder created above there will be a ``recommender.yaml`` file. This file should be updated to contain the details about your data and recommender.
28+
29+
.. code-block:: bash
30+
31+
cd recommender
32+
vi recommender.yaml
33+
34+
.. code-block:: yaml
35+
36+
kind: operator
37+
type: recommendation
38+
version: v1
39+
spec:
40+
user_data:
41+
url: users.csv
42+
item_data:
43+
url: items.csv
44+
interactions_data:
45+
url: interactions.csv
46+
top_k: 4
47+
user_column: user_id
48+
item_column: movie_id
49+
interaction_column: rating
50+
51+
52+
Run
53+
---
54+
55+
Now run the recommender job locally:
56+
57+
.. code-block:: bash
58+
59+
ads operator run -f recommender.yaml
60+
61+
62+
Results
63+
-------
64+
65+
If not specified in the YAML, all results will be placed in a new folder called ``results``. Performance is summarized in the ``report.html`` file.
66+
67+
.. code-block:: bash
68+
69+
open results/report.html

0 commit comments

Comments
 (0)