Step 1: Gather Data
Stay organized with collections
Save and categorize content based on your preferences.
Gathering data is the most important step in solving any supervised machine
learning problem. Your text classifier can only be as good as the dataset it is
built from.
If you don’t have a specific problem you want to solve and are just interested
in exploring text classification in general, there are plenty of open source
datasets available. You can find links to some of them in our GitHub
repo.
On the other hand, if you are tackling a specific problem,
you will need to collect the necessary data. Many organizations provide public
APIs for accessing their data—for example, the
X API or the
NY Times API. You may be able to leverage
these APIs for the problem you are trying to solve.
Here are some important things to remember when collecting data:
- If you are using a public API, understand the limitations of the API before
using them. For example, some APIs set a limit on the rate at which you can make
queries.
- The more training examples (referred to as samples in the rest of this guide)
you have, the better. This will help your model
generalize better.
- Make sure the number of samples for every class or topic is not overly
imbalanced. That is,
you should have comparable number of samples in each class.
- Make sure that your samples adequately cover the space of possible inputs,
not only the common cases.
Throughout this guide, we will use the Internet Movie Database (IMDb) movie
reviews dataset to illustrate
the workflow. This dataset contains movie reviews posted by people on the IMDb
website, as well as the corresponding labels (“positive” or “negative”)
indicating whether the reviewer liked the movie or not. This is a classic
example of a sentiment analysis problem.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-25 UTC.
[null,null,["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eHigh-quality data is crucial for building effective supervised machine learning text classifiers, with more training samples generally leading to better performance.\u003c/p\u003e\n"],["\u003cp\u003ePublic APIs and open-source datasets can be leveraged for data collection, but it's important to understand API limitations and ensure data balance across classes.\u003c/p\u003e\n"],["\u003cp\u003eAdequate data representation across all possible input variations is necessary, and the IMDb movie reviews dataset will be used to demonstrate text classification workflow for sentiment analysis.\u003c/p\u003e\n"],["\u003cp\u003eWhen collecting data, aim for a balanced dataset with a sufficient number of samples for each class to avoid imbalanced datasets and promote better model generalization.\u003c/p\u003e\n"]]],[],null,["# Step 1: Gather Data\n\nGathering data is the most important step in solving any supervised machine\nlearning problem. Your text classifier can only be as good as the dataset it is\nbuilt from.\n\nIf you don't have a specific problem you want to solve and are just interested\nin exploring text classification in general, there are plenty of open source\ndatasets available. You can find links to some of them in our [GitHub\nrepo](https://github.com/google/eng-edu/blob/master/ml/guides/text_classification/load_data.py).\nOn the other hand, if you are tackling a specific problem,\nyou will need to collect the necessary data. Many organizations provide public\nAPIs for accessing their data---for example, the\n[X API](https://developer.x.com/docs) or the\n[NY Times API](http://developer.nytimes.com/). You may be able to leverage\nthese APIs for the problem you are trying to solve.\n\nHere are some important things to remember when collecting data:\n\n- If you are using a public API, understand the *limitations* of the API before using them. For example, some APIs set a limit on the rate at which you can make queries.\n- The more training examples (referred to as *samples* in the rest of this guide) you have, the better. This will help your model [generalize](/machine-learning/glossary#generalization) better.\n- Make sure the number of samples for every *class* or topic is not overly [imbalanced](/machine-learning/glossary#class_imbalanced_data_set). That is, you should have comparable number of samples in each class.\n- Make sure that your samples adequately cover the *space of possible inputs*, not only the common cases.\n\nThroughout this guide, we will use the [Internet Movie Database (IMDb) movie\nreviews dataset](http://ai.stanford.edu/%7Eamaas/data/sentiment/) to illustrate\nthe workflow. This dataset contains movie reviews posted by people on the IMDb\nwebsite, as well as the corresponding labels (\"positive\" or \"negative\")\nindicating whether the reviewer liked the movie or not. This is a classic\nexample of a sentiment analysis problem."]]