tensorflow / tensorflow/recommenders

Feature preprocessing doc needs more info

Open
#207 4 comments 0 reactions 1 assignee View on GitHub

@maciejkula is already working on this.

Since Jan 17, 2021.

question
Dominant language
Python
Stars
2k
Forks
300
PR merge metrics
No merged PRs in 30d

Description

I think others may be looking for the same kinds of info as me.

Working through the featurization doc, questions arise (can't seem to find relevant info on SOF):

  1. If you have user/item events with associated numeric ratings (assigned explicitly or computed implicitly), how do you featurize the ratings? The examples focus on featurizing user ID's and item ID (e.g. the movie titles) but what about event ratings in addition to those two?
  2. Text feature processing. Are there any how-to's or recipes for how to deal with multiple languages? There doesn't seem to be anything about multi-lang in the keras TextVectorization doc. This SOF post talks about using NLTK or the like. It would be very helpful if TFRS had a writeup on how to do multi-lang text features.
  3. "Turning categorical features into embeddings" talks about translating raw tokens to embedding ids and uses the adapt method. The Retrieval tutorial does not use adapt. How important is it to convert, for example, string user ID's into integers? Is this step a must? "During model training, the value of that vector is adjusted to help the model predict its objective better." -- does this mean that without the conversion to integers, accuracy of predictions will be a lot worse? If this step is done, would I still be able to use the string user ID's when looking up predictions, or do I need to use the integers? How does one go back and forth between the two forms?
  4. When instrumenting features for a model, how can I indicate the relative importance of one feature vs. another? For instance, if I want genre to be treated as N times more important than for example the duration of the movie, how do I specify that? Or, do we leave it up to TF itself to learn what's more imporant?
  5. User geo-location featurization. I have the following types of geoloc data on events: geoname_id (a unique geoloc integer), country, administrative division (e.g. state), latitude and longitude. Does it make sense to featurize the location ID's or something less precise such as e.g. country+state(if any) ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.