Skip to content

[Docs Enhancement] Why do I need a Schema for Weaviate's Recommender Service? #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cdpierse merged 1 commit into from
Sep 23, 2024
Merged

[Docs Enhancement] Why do I need a Schema for Weaviate's Recommender Service? #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/2_create_schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,13 @@
## Overview
This guide explains how to create and configure the schema for your recommender system using the `WeaviateRecommendClient`.

## Why do I need a Schema for the Recommender Service?

The Recommender Service Schema lets you achieve two key features:

1. Set Interaction Weights: The Recommender Schema enables weighting interactions such as "Add_To_Cart" more so than "Viewed_Item". This further lets you set negative weights for interactions such as "Dislike".
2. Table Representation Learning (Advanced): Weaviate's Recommender Service leverages `BOOLEAN`, `INT`, `FLOAT`, and `TEXT`-encoded categories to compute vector representations.

## Prerequisites
- Established connection to the Recommender Service (see `1_connection.md`)
- Understanding of your data model and recommendation requirements
Expand Down