"dataset_infos.json" missing for chr_en and mc4
MEMBER
Hi ! Thanks for reporting :) 
We can easily add the metadata for `chr_en` IMO, but for mC4 it will take more time, since it requires to count the number of examples in each language
2021-11-22T09:19:00Z
https://github.com/huggingface/datasets/issues/3308#issuecomment-975315348
https://api.github.com/repos/huggingface/datasets/issues/3308
IC_kwDODunzps46IiGU
https://api.github.com/repos/huggingface/datasets/issues/comments/975315348/reactions
2021-11-22T09:19:00Z
https://api.github.com/repos/huggingface/datasets/issues/comments/975315348
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
NONE
No problem. I am trying to do some analysis on the metadata of all available datasets. Is reading `metadata_infos.json` for each dataset the correct way to go? 

I noticed that the same information is also available as special variables inside .py file of each dataset. So, I was wondering if `metadata_infos.json` has been deprecated?

![image](https://user-images.githubusercontent.com/8587189/142914413-a95a1abf-6f3e-4fbe-96e5-16d3ca39c831.png)

2021-11-22T18:20:50Z
https://github.com/huggingface/datasets/issues/3308#issuecomment-975798079
https://api.github.com/repos/huggingface/datasets/issues/3308
IC_kwDODunzps46KX8_
https://api.github.com/repos/huggingface/datasets/issues/comments/975798079/reactions
2021-11-22T18:20:50Z
https://api.github.com/repos/huggingface/datasets/issues/comments/975798079
https://avatars.githubusercontent.com/u/8587189?v=4
https://api.github.com/users/amitness/events{/privacy}
https://api.github.com/users/amitness/followers
https://api.github.com/users/amitness/following{/other_user}
https://api.github.com/users/amitness/gists{/gist_id}
https://github.com/amitness
amitness
MDQ6VXNlcjg1ODcxODk=
https://api.github.com/users/amitness/orgs
https://api.github.com/users/amitness/received_events
https://api.github.com/users/amitness/repos
https://api.github.com/users/amitness/starred{/owner}{/repo}
https://api.github.com/users/amitness/subscriptions
User
https://api.github.com/users/amitness
public
MEMBER
The `dataset_infos.json` files have more information and are made to be used to analyze the datasets without having to run/parse the python scripts. Moreover some datasets on the Hugging face don't even have a python script, and for those ones we'll make tools to generate the JSON file automatically :)
2021-11-24T16:36:52Z
https://github.com/huggingface/datasets/issues/3308#issuecomment-978042719
https://api.github.com/repos/huggingface/datasets/issues/3308
IC_kwDODunzps46S79f
https://api.github.com/repos/huggingface/datasets/issues/comments/978042719/reactions
2021-11-24T16:36:52Z
https://api.github.com/repos/huggingface/datasets/issues/comments/978042719
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
## Describe the bug
In the repository, every dataset has its metadata in a file called`dataset_infos.json`. But, this file is missing for two datasets: `chr_en` and `mc4`.

## Steps to reproduce the bug
Check [chr_en](https://github.com/huggingface/datasets/tree/master/datasets/chr_en) and [mc4](https://github.com/huggingface/datasets/tree/master/datasets/mc4)