# youte: A command-line tool to retrieve and tidy YouTube metadata and comments from YouTube Data API
[](https://pypi.org/project/youte/)
[](https://doi.org/10.25912/RDF_1684202566368)
[](https://pepy.tech/project/youte)
[](LICENCE)
Big thanks to [@Lingomat](https://github.com/Lingomat) (Mat Bettinson) for code review and suggestions.
## Installation
```bash
python -m pip install youte
```
## YouTube API key
To get data from YouTube API, you will need a YouTube API key. Follow YouTube [instructions](https://developers.google.com/youtube/v3/getting-started) to obtain a YouTube API key if you do not already have one.
## Configure API key (recommended)
You can save your API key in the youte config file for reuse. To do so, run:
```bash
youte config add-key
```
The interactive prompt will ask you to input your API key and name it. The name is used to identify the key, and can be anything you choose.
The prompt will also ask if you want to set the given key as default.
When running queries, if no API key or name is specified, `youte` will automatically use the default key.
### Manually set a key as default
If you want to manually set an existing key as a default, run:
```bash
youte config set-default <name-of-existing-key>
```
Note that what is passed to this command is the _name_ of the API key, not the API key itself. It follows that the API key has to be first added to the config file using `youte config add-key`. If you use a name that has not been added to the config file, an error will be raised.
#### See the list of all keys
To see the list of all keys, run:
```bash
youte config list-keys
```
The default key, if there is one, will have an asterisk next to it.
#### Remove a key
To remove a stored key, run:
```bash
youte config remove <name-of-key>
```
#### About the config file
youte's config file is stored in a central place whose exact location depends on the running operating system:
- Linux/Unix: ~/.config/youte/
- Mac OS X: ~/Library/Application Support/youte/
- Windows: C:\Users\\\<user>\\AppData\Roaming\youte
## search
Searching can be as simple as:
```bash
youte search <search-terms> --key <API-key> --outfile <name-of-file.json>
# OR
youte search <search-terms> --key <API-key> -o <name-of-file.json>
```
If you have a default key set up using `youte config`, then there is no need to specify an API key using `--key`.
This will return the maximum number of results pages (around 12-13) matching the search terms and store them in a JSON file. Unlike version 1.3, youte 2.0 does not print results to the terminal. Instead, `--outfile` is now a required option. <search-terms> and `--outfile` must be specified.
In the search terms, you can also use the Boolean NOT (-) and OR (|) operators to exclude videos or to find videos that match one of several search terms. If the terms contain spaces, the entire search term value has to be wrapped in quotes.
Use the flag `--pretty` to pretty format the JSON output.
```bash
youte search <search-terms> --key <API-key> --outfile <name-of-file> --pretty
```
### Limit pages returned
Searching is very expensive in terms of API usage - a single results page uses up 100 points - 1% of your standard daily quota. Therefore, you can limit the maximum number of result pages returned, so that a search doesn't go on and exhaust your API quota.
```bash
youte search <search-terms> --max-pages 5
# OR
youte search <search-terms> -m 5
```
### Tidy data
Raw JSONs from YouTube API contain request metadata and nested fields. You can tidy these data into a CSV or a flat JSON using `--tidy-to`. The default format that youte will tidy raw JSON into will be CSV.
```bash
youte search <search-terms> --tidy-to <file.csv>
```
You can specify the encoding for the CSV. By default, `youte` uses `utf-8-sig` for compatibility with Excel readers. To change this, use the `--encoding` argument.
```bash
youte search <search-terms> --tidy-to <file.csv> --encoding "utf-8"
```
Specify `--format json` if you want to tidy raw data into an array of flat JSON objects.
```bash
youte search <search-terms> --tidy-to <file-name.json> --format json
```
`--tidy-to` option is available for all `youte` commands that retrieve data, and works the same way.
### Advanced search
There are multiple filters to refine your search. A full list of these are provided below:
``` {.bash .no-copy}
Options:
--type TEXT Type of resource to search for [default:
video]
--order [date|rating|relevance|title|videoCount|viewCount]
Sort results [default: date]
--safe-search [none|moderate|strict]
Include or exclude restricted content
[default: none]
--lang TEXT Return results most relevant to a language
(ISO 639-1 two-letter code)
--region TEXT Return videos viewable in the specified
country (ISO 3166-1 alpha-2 code) [default:
US]
--video-duration [any|long|medium|short]
Include videos of a certain duration
--channel-type [any|show] Restrict search to a particular type of
channel
--video-type [any|episode|movie]
Search a particular type of videos
--caption [any|closedCaption|none]
Filter videos based on if they have captions
--definition, --video-definition [any|high|standard]
Include videos by definition
--dimension, --video-dimension [any|2d|3d]
Search 2D or 3D videos
--embeddable, --video-embeddable [any|true]
Search only embeddable videos
--license, --video-license [any|creativeCommon|youtube]
Include videos with a certain license
--location FLOAT... Lat and long coordinates to restrict search
to. --radius must be specified
--radius TEXT Define the geographic area to restrict
search. Must be a number with a unit
```
#### Restrict by date range
The `--from` and `--to` options allow you to restrict your search to a specific period. The input values have to be in ISO format (YYYY-MM-DD). Currently, all dates and times in youte are in UTC.
#### Restrict by type
The `--type` option specifies the type of results returned, which by default is videos. The accepted values are `channel`, `playlist`, `video`, or a combination of these three. If more than one type is specified, separate each by a comma.
```shell
youte search <search-terms> --limit 5 --type playlist,video
```
#### Restrict by language and region
The `--lang` returns results most relevant to a language. Not all results will be in the specified language: results in other languages will still be returned if they are highly relevant to the search query term. To specify the language, use [ISO 639-1 two letter code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), except that you should use the values `zh-Hans` for simplified Chinese and `zh-Hant` for traditional Chinese.
The `--region` returns results viewable in a region. To specify the region, use [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). Note that this option does *not* filter videos uploaded in that region, but rather videos that can be _viewed_ in that region.
The `--location` and `--radius` options define a circular geographic area to filter videos that specify, in their metadata, a location within this area. This is *not* a robust and reliable way to geolocate YouTube videos, and hence should be used with care.
- `--location` takes in 2 values - the latitude/longitude coordinates that represent the centre of the area
- `--radius` specifies the maximum distance that the location associated with a video can be from that point for the video to still be included in the search results. It must be a number followed by a unit. Valid units are `m`, `km`, `ft`, and `mi`. For example, `1500m`, `5km`, `10000ft`, and `0.75mi`.
Both `--location` and `--radius` have to be specified if they are to be used, otherwise an API error will be thrown.
### Sort results
The `--order` option specifies how results will be sorted. The following values are accepted:
- `date`: Resources are sorted in reverse chronological order based on the date they were created (default value).
- `rating`: Resources are sorted from highest to lowest rating.
- `relevance`: Resources are sorted based on their relevance to the search query.
- `title` – Resources are sorted alphabetically by title.
- `videoCount` – Channels are sorted in descending order of their number of uploaded videos.
- `viewCount` – Resources are sorted from highest to lowest number of views. For live broadcasts, videos are sorted by number of concurrent viewers while the broadcasts are ongoing.
## videos
`youte videos` takes in one or multiple video IDs and retrieve all public metadata for those videos. This complements results returned from `youte search`, as they contain only limited information.
```shell
youte hydrate <resource-id>.... --outfile <file.json>
```
You can put as many IDs as you need, separating each with a space.
Like search, you can also tidy the data to a CSV using the `--tidy-to` option.
```shell
youte hydrate <resource-id>... --outfile <file.json> --tidy-to <file-name.csv>
```
### Use IDs from text file
You can hydrate a list of video ids stored in a text file by using `--file-path` or `-f`. The text file should contain a line-separated list of video ids, with no header.
```shell
youte hydrate -f <id-file.csv>
```
This option is often used in combination with `youte dehydrate`, which retrieves the ids from raw JSON returned by `youte search` and stores them in a text file.
## channels
`youte channels` works the same as `youte videos`, except it retrieves channel metadata from channel ids.
You can either hydrate channels by channel IDs, or *handles*, i.e. @stanfordgsb. To pass handles, use the option `--handles` followed by a comma separated list of handles, each prefererably prepended by `@`. For example:
```shell
youte channels --handles @stanfordgsb,@TED,@TEDEd -o <file.json>
```
To use a file containing handles, pass `--handle-file`.
You can hydrate both channel IDs and handles in one command:
```shell
youte channels -f <id-file.csv> --handles @stanfordgsb,@TED,@TEDEd -o <file.json>
```
This will hydrate both the channel IDs in the file and the handles specified in the terminal.
## comments
`youte comments` retrieves top-level comments (comment threads) on one or multiple videos or channels. It takes in a list of ids and a flag indicating which type these ids are (i.e. videos or channels).
To retrieve comments on videos, specify the video ids and pass the `--by-video-id` or `-v` flag.
```shell
youte comments <id>... --by-video-id --outfile <file.json>
#OR
youte comments <id>... -v --outfile <file.json>
```
To retrieve comments on channels, specify channel ids and pass the `--by-channel-id` or `-c` flag.
```bash
youte comments <id>... --by-channel-id --outfile <file.json>
OR
youte comments <id>... -c --outfile <file.json>
```
If neither of the flags are specified, `youte comments` will assume the ids are thread ids and retrieve the full metadata for those threads.
You can search within the threads and filter threads that match the search terms, by using the `--query` or `-q` option.
```bash
youte comments <ids>... -v --outfile <file.json> -q "search term"
```
## replies
While `youte comments` only retrieve top-level comment threads, if those threads have replies, they can be retrieved using `youte replies`. `youte replies` takes a list of thread ids and return the replies to those threads.
```shell
youte replies <ids>... --outfile <file.json>
```
## chart
`youte chart` retrieves the most popular videos in a region, specified by [ISO 3166-1 alpha-2 country codes](https://www.iso.org/obp/ui/#search). If no argument or option is given, it retrieves the most popular videos in the United States.
For example:
```shell
youte chart <region-code> -o <file.json>
```
## full-archive
A new feature added in `youte` 2.1.0 is the ability to run a full archive workflow in one command. `youte full-archive` runs `youte search`, then retrieving video and channel metadata for the search results, as well as getting comments and replies for those videos as well. All data are then tidied and stored in multiple tables in an SQLite database.
```shell
youte full-archive <query> [options] -o <name-of-database-file>
```
The search options are identical to `youte search`. Name of the file given to `-o` has to have SQLite extension (i.e. `.db` or `.sqlite`).
Below are the list of tables and the corresponding YouTube resource that they contain:
- `search_result`: search results from `youte search`
- `video`: videos
- `channel`: channels
- `commment`: comment threads and replies
Warning: since `full-archive` will potentially run a large number of queries, it's important to ensure you have enough API quota. You can select which resources to retrieve by using the `--select` option. `--select` takes one or a comma-separated list of YouTube resource types, namely `video`, `channel`, `thread`, and `reply`. Note that if you select `reply`, `thread` also has to be selected. This is because comment thread replies are retrieved using thread IDs, thus collecting comment threads is a must before getting replies. Because of that, if you want to archive the replies, both 'thread' and 'reply' will have to be specified.
## dehydrate
`dehydrate` extracts the IDs from a JSON file returned from YouTube API.
```shell
youte dehydrate <file-name.json>
```
```{.shell .no-copy}
Options:
-o, --output FILENAME Output text file to store IDs in
```
## related-to (deprecated)
*Note.* **From August 7, 2023, this endpoint was deprecated by YouTube. This command is no longer usable.**
`youte related-to` retrieves a list of videos related to a video.
```shell
youte related-to <video-ids>... -o <file.json>
```
You can pass one or many video IDs. If multiple video IDs are inputted, youte will iterate through those video IDs, retrieving all related videos to each video separately. The end result contains both the related videos and the id of the video that they are related to.
Other options include:
```{.bash .no-copy}
--safe-search [none|moderate|strict]
Include or exclude restricted content
[default: none]
--region TEXT Specify region the videos can be viewed in
(ISO 3166-1 alpha-2 country code)
--lang TEXT Return results most relevant to a language
(ISO 639-1 two-letter code)
```
## YouTube API Quota system and youte handling of quota
Most often, there is a limit to how many requests you can make to YouTube API per day. YouTube Data API uses a quota system, whereby each request costs a number of units depending on the endpoint the request is made to.
For example:
- search endpoint costs 100 units per request
- video, channel, commentThread, and comment endpoints each costs 1 unit per request
Free accounts get an API quota cap of 10,000 units per project per day, which resets at midnight Pacific Time.
At present, you can only check your quota usage on the [Quotas](https://console.developers.google.com/iam-admin/quotas) page in the API Console. It is not possible to monitor quota usage via metadata returned in the API response. `youte` does not monitor quota usage.
Raw data
{
"_id": null,
"home_page": "https://github.com/QUT-Digital-Observatory/youte",
"name": "youte",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": null,
"author": "Digital Observatory",
"author_email": "digitalobservatory@qut.edu.au",
"download_url": "https://files.pythonhosted.org/packages/0c/bc/10931266c6408038d09dd3e95af61869ee886ca0aaa52a8be8b79b303d2e/youte-2.6.1.tar.gz",
"platform": null,
"description": "# youte: A command-line tool to retrieve and tidy YouTube metadata and comments from YouTube Data API\n\n[](https://pypi.org/project/youte/)\n[](https://doi.org/10.25912/RDF_1684202566368)\n[](https://pepy.tech/project/youte)\n[](LICENCE)\n\n\n\n\n\nBig thanks to [@Lingomat](https://github.com/Lingomat) (Mat Bettinson) for code review and suggestions.\n\n## Installation\n\n```bash\npython -m pip install youte\n``` \n\n## YouTube API key \n\nTo get data from YouTube API, you will need a YouTube API key. Follow YouTube [instructions](https://developers.google.com/youtube/v3/getting-started) to obtain a YouTube API key if you do not already have one.\n\n## Configure API key (recommended)\n\nYou can save your API key in the youte config file for reuse. To do so, run:\n\n```bash \nyoute config add-key\n``` \n\nThe interactive prompt will ask you to input your API key and name it. The name is used to identify the key, and can be anything you choose.\n\nThe prompt will also ask if you want to set the given key as default.\n\nWhen running queries, if no API key or name is specified, `youte` will automatically use the default key.\n\n### Manually set a key as default \n\nIf you want to manually set an existing key as a default, run: \n\n```bash \nyoute config set-default <name-of-existing-key>\n```\n\nNote that what is passed to this command is the _name_ of the API key, not the API key itself. It follows that the API key has to be first added to the config file using `youte config add-key`. If you use a name that has not been added to the config file, an error will be raised.\n\n#### See the list of all keys \n\nTo see the list of all keys, run: \n\n```bash \nyoute config list-keys\n``` \n\nThe default key, if there is one, will have an asterisk next to it.\n\n#### Remove a key\n\nTo remove a stored key, run:\n\n```bash\nyoute config remove <name-of-key>\n```\n\n#### About the config file \n\nyoute's config file is stored in a central place whose exact location depends on the running operating system: \n\n- Linux/Unix: ~/.config/youte/ \n- Mac OS X: ~/Library/Application Support/youte/\n- Windows: C:\\Users\\\\\\<user>\\\\AppData\\Roaming\\youte\n\n## search\n\nSearching can be as simple as:\n\n```bash\nyoute search <search-terms> --key <API-key> --outfile <name-of-file.json>\n# OR\nyoute search <search-terms> --key <API-key> -o <name-of-file.json>\n```\n\nIf you have a default key set up using `youte config`, then there is no need to specify an API key using `--key`.\n\nThis will return the maximum number of results pages (around 12-13) matching the search terms and store them in a JSON file. Unlike version 1.3, youte 2.0 does not print results to the terminal. Instead, `--outfile` is now a required option. <search-terms> and `--outfile` must be specified. \n\nIn the search terms, you can also use the Boolean NOT (-) and OR (|) operators to exclude videos or to find videos that match one of several search terms. If the terms contain spaces, the entire search term value has to be wrapped in quotes.\n\nUse the flag `--pretty` to pretty format the JSON output.\n\n```bash\nyoute search <search-terms> --key <API-key> --outfile <name-of-file> --pretty\n```\n\n### Limit pages returned\n\nSearching is very expensive in terms of API usage - a single results page uses up 100 points - 1% of your standard daily quota. Therefore, you can limit the maximum number of result pages returned, so that a search doesn't go on and exhaust your API quota.\n\n```bash\nyoute search <search-terms> --max-pages 5\n# OR\nyoute search <search-terms> -m 5\n```\n\n### Tidy data\n\nRaw JSONs from YouTube API contain request metadata and nested fields. You can tidy these data into a CSV or a flat JSON using `--tidy-to`. The default format that youte will tidy raw JSON into will be CSV.\n\n```bash\nyoute search <search-terms> --tidy-to <file.csv>\n```\n\nYou can specify the encoding for the CSV. By default, `youte` uses `utf-8-sig` for compatibility with Excel readers. To change this, use the `--encoding` argument.\n\n```bash\nyoute search <search-terms> --tidy-to <file.csv> --encoding \"utf-8\"\n```\n\nSpecify `--format json` if you want to tidy raw data into an array of flat JSON objects.\n\n```bash\nyoute search <search-terms> --tidy-to <file-name.json> --format json\n```\n\n`--tidy-to` option is available for all `youte` commands that retrieve data, and works the same way.\n\n### Advanced search\n\nThere are multiple filters to refine your search. A full list of these are provided below:\n\n``` {.bash .no-copy}\nOptions:\n --type TEXT Type of resource to search for [default:\n video]\n --order [date|rating|relevance|title|videoCount|viewCount]\n Sort results [default: date]\n --safe-search [none|moderate|strict]\n Include or exclude restricted content\n [default: none]\n --lang TEXT Return results most relevant to a language\n (ISO 639-1 two-letter code)\n --region TEXT Return videos viewable in the specified\n country (ISO 3166-1 alpha-2 code) [default:\n US]\n --video-duration [any|long|medium|short]\n Include videos of a certain duration\n --channel-type [any|show] Restrict search to a particular type of\n channel\n --video-type [any|episode|movie]\n Search a particular type of videos\n --caption [any|closedCaption|none]\n Filter videos based on if they have captions\n --definition, --video-definition [any|high|standard]\n Include videos by definition\n --dimension, --video-dimension [any|2d|3d]\n Search 2D or 3D videos\n --embeddable, --video-embeddable [any|true]\n Search only embeddable videos\n --license, --video-license [any|creativeCommon|youtube]\n Include videos with a certain license\n --location FLOAT... Lat and long coordinates to restrict search\n to. --radius must be specified\n --radius TEXT Define the geographic area to restrict\n search. Must be a number with a unit\n```\n\n#### Restrict by date range\n\nThe `--from` and `--to` options allow you to restrict your search to a specific period. The input values have to be in ISO format (YYYY-MM-DD). Currently, all dates and times in youte are in UTC.\n\n#### Restrict by type\n\nThe `--type` option specifies the type of results returned, which by default is videos. The accepted values are `channel`, `playlist`, `video`, or a combination of these three. If more than one type is specified, separate each by a comma.\n\n```shell\nyoute search <search-terms> --limit 5 --type playlist,video\n```\n\n#### Restrict by language and region\n\nThe `--lang` returns results most relevant to a language. Not all results will be in the specified language: results in other languages will still be returned if they are highly relevant to the search query term. To specify the language, use [ISO 639-1 two letter code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), except that you should use the values `zh-Hans` for simplified Chinese and `zh-Hant` for traditional Chinese.\n\nThe `--region` returns results viewable in a region. To specify the region, use [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2). Note that this option does *not* filter videos uploaded in that region, but rather videos that can be _viewed_ in that region.\n\nThe `--location` and `--radius` options define a circular geographic area to filter videos that specify, in their metadata, a location within this area. This is *not* a robust and reliable way to geolocate YouTube videos, and hence should be used with care.\n\n- `--location` takes in 2 values - the latitude/longitude coordinates that represent the centre of the area\n- `--radius` specifies the maximum distance that the location associated with a video can be from that point for the video to still be included in the search results. It must be a number followed by a unit. Valid units are `m`, `km`, `ft`, and `mi`. For example, `1500m`, `5km`, `10000ft`, and `0.75mi`.\n\nBoth `--location` and `--radius` have to be specified if they are to be used, otherwise an API error will be thrown.\n\n### Sort results\n\nThe `--order` option specifies how results will be sorted. The following values are accepted:\n\n- `date`: Resources are sorted in reverse chronological order based on the date they were created (default value).\n- `rating`: Resources are sorted from highest to lowest rating.\n- `relevance`: Resources are sorted based on their relevance to the search query.\n- `title` \u2013 Resources are sorted alphabetically by title.\n- `videoCount` \u2013 Channels are sorted in descending order of their number of uploaded videos.\n- `viewCount` \u2013 Resources are sorted from highest to lowest number of views. For live broadcasts, videos are sorted by number of concurrent viewers while the broadcasts are ongoing.\n\n## videos\n\n`youte videos` takes in one or multiple video IDs and retrieve all public metadata for those videos. This complements results returned from `youte search`, as they contain only limited information.\n\n```shell\nyoute hydrate <resource-id>.... --outfile <file.json>\n```\n\nYou can put as many IDs as you need, separating each with a space.\n\nLike search, you can also tidy the data to a CSV using the `--tidy-to` option.\n\n```shell\nyoute hydrate <resource-id>... --outfile <file.json> --tidy-to <file-name.csv>\n```\n\n### Use IDs from text file\n\nYou can hydrate a list of video ids stored in a text file by using `--file-path` or `-f`. The text file should contain a line-separated list of video ids, with no header.\n\n```shell\nyoute hydrate -f <id-file.csv>\n```\n\nThis option is often used in combination with `youte dehydrate`, which retrieves the ids from raw JSON returned by `youte search` and stores them in a text file.\n\n## channels\n\n`youte channels` works the same as `youte videos`, except it retrieves channel metadata from channel ids.\n\nYou can either hydrate channels by channel IDs, or *handles*, i.e. @stanfordgsb. To pass handles, use the option `--handles` followed by a comma separated list of handles, each prefererably prepended by `@`. For example:\n\n```shell\nyoute channels --handles @stanfordgsb,@TED,@TEDEd -o <file.json>\n```\n\nTo use a file containing handles, pass `--handle-file`.\n\nYou can hydrate both channel IDs and handles in one command:\n\n```shell\nyoute channels -f <id-file.csv> --handles @stanfordgsb,@TED,@TEDEd -o <file.json>\n```\n\nThis will hydrate both the channel IDs in the file and the handles specified in the terminal.\n\n## comments\n\n`youte comments` retrieves top-level comments (comment threads) on one or multiple videos or channels. It takes in a list of ids and a flag indicating which type these ids are (i.e. videos or channels).\n\nTo retrieve comments on videos, specify the video ids and pass the `--by-video-id` or `-v` flag.\n\n```shell\nyoute comments <id>... --by-video-id --outfile <file.json>\n#OR\nyoute comments <id>... -v --outfile <file.json>\n```\n\nTo retrieve comments on channels, specify channel ids and pass the `--by-channel-id` or `-c` flag.\n\n```bash\nyoute comments <id>... --by-channel-id --outfile <file.json>\nOR\nyoute comments <id>... -c --outfile <file.json>\n```\n\nIf neither of the flags are specified, `youte comments` will assume the ids are thread ids and retrieve the full metadata for those threads.\n\nYou can search within the threads and filter threads that match the search terms, by using the `--query` or `-q` option.\n\n```bash\nyoute comments <ids>... -v --outfile <file.json> -q \"search term\"\n```\n\n## replies\n\nWhile `youte comments` only retrieve top-level comment threads, if those threads have replies, they can be retrieved using `youte replies`. `youte replies` takes a list of thread ids and return the replies to those threads.\n\n```shell\nyoute replies <ids>... --outfile <file.json>\n```\n\n## chart\n\n`youte chart` retrieves the most popular videos in a region, specified by [ISO 3166-1 alpha-2 country codes](https://www.iso.org/obp/ui/#search). If no argument or option is given, it retrieves the most popular videos in the United States.\n\nFor example:\n\n```shell\nyoute chart <region-code> -o <file.json>\n```\n\n## full-archive\n\nA new feature added in `youte` 2.1.0 is the ability to run a full archive workflow in one command. `youte full-archive` runs `youte search`, then retrieving video and channel metadata for the search results, as well as getting comments and replies for those videos as well. All data are then tidied and stored in multiple tables in an SQLite database. \n\n```shell\nyoute full-archive <query> [options] -o <name-of-database-file>\n```\n\nThe search options are identical to `youte search`. Name of the file given to `-o` has to have SQLite extension (i.e. `.db` or `.sqlite`).\n\nBelow are the list of tables and the corresponding YouTube resource that they contain:\n\n- `search_result`: search results from `youte search`\n- `video`: videos\n- `channel`: channels\n- `commment`: comment threads and replies\n\nWarning: since `full-archive` will potentially run a large number of queries, it's important to ensure you have enough API quota. You can select which resources to retrieve by using the `--select` option. `--select` takes one or a comma-separated list of YouTube resource types, namely `video`, `channel`, `thread`, and `reply`. Note that if you select `reply`, `thread` also has to be selected. This is because comment thread replies are retrieved using thread IDs, thus collecting comment threads is a must before getting replies. Because of that, if you want to archive the replies, both 'thread' and 'reply' will have to be specified.\n\n## dehydrate\n\n`dehydrate` extracts the IDs from a JSON file returned from YouTube API.\n\n```shell\nyoute dehydrate <file-name.json>\n```\n\n```{.shell .no-copy}\nOptions:\n -o, --output FILENAME Output text file to store IDs in\n```\n\n## related-to (deprecated)\n\n*Note.* **From August 7, 2023, this endpoint was deprecated by YouTube. This command is no longer usable.**\n\n`youte related-to` retrieves a list of videos related to a video.\n\n```shell\nyoute related-to <video-ids>... -o <file.json>\n```\n\nYou can pass one or many video IDs. If multiple video IDs are inputted, youte will iterate through those video IDs, retrieving all related videos to each video separately. The end result contains both the related videos and the id of the video that they are related to.\n\nOther options include:\n\n```{.bash .no-copy}\n --safe-search [none|moderate|strict]\n Include or exclude restricted content\n [default: none]\n --region TEXT Specify region the videos can be viewed in\n (ISO 3166-1 alpha-2 country code)\n --lang TEXT Return results most relevant to a language\n (ISO 639-1 two-letter code)\n```\n\n## YouTube API Quota system and youte handling of quota \n\nMost often, there is a limit to how many requests you can make to YouTube API per day. YouTube Data API uses a quota system, whereby each request costs a number of units depending on the endpoint the request is made to.\n\nFor example: \n\n- search endpoint costs 100 units per request \n- video, channel, commentThread, and comment endpoints each costs 1 unit per request \n\nFree accounts get an API quota cap of 10,000 units per project per day, which resets at midnight Pacific Time.\n\nAt present, you can only check your quota usage on the [Quotas](https://console.developers.google.com/iam-admin/quotas) page in the API Console. It is not possible to monitor quota usage via metadata returned in the API response. `youte` does not monitor quota usage.\n",
"bugtrack_url": null,
"license": null,
"summary": "Command-line tool to collect video metadata and comments from Youtube API",
"version": "2.6.1",
"project_urls": {
"Bug Tracker": "https://github.com/QUT-Digital-Observatory/youte/issues",
"Homepage": "https://github.com/QUT-Digital-Observatory/youte"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "d89c3ae244ec11df1585630d1af74197b99128aed628a3c3e2d6ef8963bae6ee",
"md5": "71c6e1b76414b998c7b4b43b417d6740",
"sha256": "e3377aa0539fe78d20d34dab5e3874e16d1caf84b9d2cd72648629a949a9e3ec"
},
"downloads": -1,
"filename": "youte-2.6.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "71c6e1b76414b998c7b4b43b417d6740",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 33731,
"upload_time": "2024-08-27T05:56:58",
"upload_time_iso_8601": "2024-08-27T05:56:58.272516Z",
"url": "https://files.pythonhosted.org/packages/d8/9c/3ae244ec11df1585630d1af74197b99128aed628a3c3e2d6ef8963bae6ee/youte-2.6.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "0cbc10931266c6408038d09dd3e95af61869ee886ca0aaa52a8be8b79b303d2e",
"md5": "b6a7fd432d1c2393fe8565018e0321f0",
"sha256": "aea501ab32d11d214a44cad99ea8bb0747274fc5c7d5da603cdfd206451bb1e0"
},
"downloads": -1,
"filename": "youte-2.6.1.tar.gz",
"has_sig": false,
"md5_digest": "b6a7fd432d1c2393fe8565018e0321f0",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 1160013,
"upload_time": "2024-08-27T05:57:02",
"upload_time_iso_8601": "2024-08-27T05:57:02.761395Z",
"url": "https://files.pythonhosted.org/packages/0c/bc/10931266c6408038d09dd3e95af61869ee886ca0aaa52a8be8b79b303d2e/youte-2.6.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-08-27 05:57:02",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "QUT-Digital-Observatory",
"github_project": "youte",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "youte"
}
JSON
