# Huggingface datasets card not work correctly

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-datasets-card-not-work-correctly%2F174072%3E%5C
**Category:** 🤗Datasets\
**Created:** [March 8, 2026, 7:42am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-datasets-card-not-work-correctly%2F174072 "2026-03-08T07:42:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anilosan15](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/anilosan15/32/58453_2.png) [@Anilosan15](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAnilosan15)%5C
**Post date:** [March 8, 2026, 7:42am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-datasets-card-not-work-correctly%2F174072%2F1 "2026-03-08T07:42:43Z")

</div>

Hi everyone, I’m trying to support the community by sharing datasets. However, for my newly published dataset, the download counts are not showing.

In my previous dataset, things like libraries and modalities appeared automatically, and Data Studio access was shown as available. But in the new dataset, these features are missing and I can’t seem to select them either.

It also feels like the download count may not be getting tracked at all. Is this normal? What should I do?

This was the case with my previous dataset:

[Anilosan15/Turkish\_TTS\_Data · Datasets at Hugging Face](https://huggingface.co/datasets/Anilosan15/Turkish_TTS_Data)

 ![{E6AE7391-0ACA-4F2E-9802-556CAEBF9401}](https://us1.discourse-cdn.com/hellohellohello/original/3X/e/0/e0d8429e48cad881b38d275fbca105b6bc56316b.png)

But with my newly published dataset, there is no modalities or libraries …. :

[Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data)

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 9, 2026, 7:20am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhuggingface-datasets-card-not-work-correctly%2F174072%2F2 "2026-03-09T07:20:51Z")

</div>

For now, a quick diagnosis:

* * *

## What I think is happening in your case

Your new dataset is **not failing in the core way that would actually break usability**. Right now, its page shows a working **Dataset Viewer** , an **“Expand in Data Studio”** link, preview rows with the columns `audio`, `text`, `source`, `sample_rate`, and `speaker`, and a visible **“Downloads last month”** count of **10**. That means the important backend pieces are already working: the Hub can read the repo, understand the schema, and power the viewer/Data Studio layer. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))

What is missing on the new page is the **top header metadata surface** : no `Modalities`, no `Formats`, no `Libraries`, and no separate top tab labeled `Data Studio`. Your older dataset page does show all of those: `Modalities: Audio, Text`, `Formats: parquet`, `Libraries: Datasets, Dask, Polars`, plus a top-level `Data Studio` tab. So the two repos are being rendered differently at the page-header level even though both are dataset-viewer-compatible. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Turkish_TTS_Data "Anilosan15/Turkish\_TTS\_Data · Datasets at Hugging Face"))

## Why I do **not** think the dataset itself is broken

Both repositories are built around the same basic storage pattern: a `data/` directory containing Parquet shards named `train-...parquet`. Your new repo has six shards (`train-00000-of-00006.parquet` through `train-00005-of-00006.parquet`), and the older repo has forty-one shards. Since both use Parquet shards under `data/`, the missing badges on the new page are **not well explained by using the wrong file format or the wrong top-level layout**. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data/tree/main/data "Anilosan15/Synthetic\_Turkish\_TTS\_Data at main"))

Hugging Face’s own docs say that a dataset with a supported structure and supported file formats automatically gets a **Dataset Viewer** , and that the viewer backend auto-converts Hub datasets to **Parquet** for exploration. Your new page already passes that bar. In other words, the fundamental data ingestion pipeline appears healthy. ([Hugging Face](https://huggingface.co/docs/hub/datasets-audio "Audio Dataset"))

## The real split: viewer/backend vs. metadata/header

Hugging Face separates two things:

1. **Dataset Viewer / Data Studio / schema preview** , which come from the viewer backend and recognizable dataset structure.
2. **Dataset card metadata and header badges** , which come from the `README.md` card and especially its YAML metadata block at the top. ([Hugging Face](https://huggingface.co/docs/hub/datasets-cards "Dataset Cards"))

That distinction matters a lot here. Your new repo already has the backend-driven features that matter most to users: preview, rows, columns, Parquet, and Data Studio access through the viewer. The missing pieces are mostly the **card/header decorations and tags**. That points much more strongly to a **metadata inference / indexing / rendering inconsistency** than to a damaged dataset. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))

## The most important clue in your README

Your new `README.md` already contains structured metadata such as `dataset_info`, feature types, split info, `configs`, `task_categories`, `language`, and a `license` field. But the `license` field in the YAML is currently just **`cc`** , while the human-readable body below says the dataset is released under **CC BY 4.0**. On the page, the header also shows only the generic **`cc`** badge. Hugging Face’s license list distinguishes the broad family identifier `cc` from the specific identifier `cc-by-4.0`. So your repo is currently telling the Hub “generic Creative Commons” in metadata while telling readers “CC BY 4.0” in prose. That mismatch is a concrete sign that the metadata layer is not as specific as it should be. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data/blob/main/README.md "README.md · Anilosan15/Synthetic\_Turkish\_TTS\_Data at main"))

By contrast, your old dataset’s page shows rich badges even though its README preview is effectively empty apart from auto-generated metadata. That tells me the older page likely benefited from **auto-inference or prior indexing behavior** that the new page has not reproduced in the same way. In plain terms: the older repo got lucky or got indexed more favorably; the newer one did not. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Turkish_TTS_Data "Anilosan15/Turkish\_TTS\_Data · Datasets at Hugging Face"))

## About the missing Modalities and Libraries

Hugging Face documents that:

- modality is **auto-detected** from the files, but you can **force it** by adding tags such as `audio` and `text` to the YAML metadata;
- the dataset page automatically shows compatible libraries, but you can also **manually associate libraries** by tagging the dataset with values such as `datasets`, `dask`, `pandas`, or `webdataset`. ([Hugging Face](https://huggingface.co/docs/hub/datasets-cards "Dataset Cards"))

That is almost exactly your situation. The page clearly understands your columns well enough to show `audio` and `text` in the viewer, but it is **not surfacing those as top-level header badges**. Since HF explicitly documents manual tags as the fallback, the safest conclusion is: **automatic inference did not fully populate the page header for this repo**. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))

## About Data Studio

This part is easy to misread. Hugging Face says **Data Studio is enabled by default for all public datasets**. Your new page does not show a separate top `Data Studio` tab the way the older page does, but it **does** show `Expand in Data Studio` inside the viewer area. So for your repo, the correct reading is not “Data Studio is unavailable”; it is “Data Studio is available, but the page is presenting it differently.” ([Hugging Face](https://huggingface.co/docs/hub/datasets-adding "Uploading datasets"))

## About download counts

This part is partly normal, partly confusing.

Hugging Face’s current rule is that **all files downloaded by the same user/IP within a 5-minute window in one repository count as a single dataset download**. That is done specifically so one user downloading many files or splits does not inflate the counter. So if you uploaded six Parquet shards, a person fetching several of them in one session still may count as only **one** dataset download. ([Hugging Face](https://huggingface.co/docs/hub/datasets-download-stats "Datasets Download Stats"))

That means a low number does **not** automatically mean tracking is broken. And in your repo’s current state, the count is not missing anyway: the page shows **10 downloads last month**. So the strongest answer is: **download tracking appears to be active right now**. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))

At the same time, public forum posts do show that Hugging Face has had periods where dataset download statistics appeared stuck or delayed for some users. There are reports from June 2024, June–July 2025, and March 2026 describing counters not updating for days. Those reports do not prove your repo has a bug, but they do show that **stats glitches on the Hub are a real thing** , so it is reasonable that this made you suspicious. ([Hugging Face Forums](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fmonthly-total-downloads-not-updated%2F92783 "Monthly / Total downloads not updated - Hub - Hugging Face Forums"))

## My actual diagnosis

For **your** repository, I would describe it this way:

- **Core dataset publishing:** working. Viewer works, Parquet is recognized, schema is recognized, Data Studio is reachable, and downloads are being counted. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))
- **Header metadata / discoverability badges:** inconsistent. The page is not surfacing modalities, format, libraries, or the dedicated Data Studio tab the way the older repo does. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Turkish_TTS_Data "Anilosan15/Turkish\_TTS\_Data · Datasets at Hugging Face"))
- **Most likely cause:** incomplete or inconsistent **Hub-side metadata inference / indexing** , made worse by your metadata being partially generic (`license: cc`) and not explicitly tagging modality/library. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data/blob/main/README.md "README.md · Anilosan15/Synthetic\_Turkish\_TTS\_Data at main"))

So: **not a broken dataset, but an incomplete card/header rendering state**.

## What I would do

### 1. Make the metadata explicit instead of relying on auto-detection

Add or revise the YAML block at the top of `README.md` so it explicitly tells the Hub what you want shown.

Use something close to this:

```yaml
---
pretty_name: Synthetic Turkish TTS Data
language:
  - tr
license: cc-by-4.0
task_categories:
  - text-to-speech
  - automatic-speech-recognition
tags:
  - audio
  - text
  - datasets
  - dask
  - polars
  - pandas

dataset_info:
  features:
    - name: audio
      dtype: audio
    - name: text
      dtype: string
    - name: source
      dtype: string
    - name: sample_rate
      dtype: int64
    - name: speaker
      dtype: string
  splits:
    - name: train
      num_bytes: 2942869578
      num_examples: 13000
  download_size: 3303296950
  dataset_size: 2942869578

configs:
  - config_name: default
    data_files:
      - split: train
        path: data/train-*
---

```

Why this helps:

- `license: cc-by-4.0` matches what your card text already says, and it uses the **specific** official Hugging Face identifier instead of the generic `cc`. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data/blob/main/README.md "README.md · Anilosan15/Synthetic\_Turkish\_TTS\_Data at main"))
- `tags: [audio, text]` is the documented way to force the **modality**. ([Hugging Face](https://huggingface.co/docs/hub/datasets-cards "Dataset Cards"))
- `tags: [datasets, dask, polars, pandas]` is the documented way to force **library associations** when the page does not show them automatically. ([Hugging Face](https://huggingface.co/docs/hub/datasets-cards "Dataset Cards"))

### 2. Commit the README change and let the page re-index

Because the header badges are metadata-driven, a README metadata commit is the right trigger for the Hub to recalculate what should be shown. Your current repo history already shows recent README updates, so another small metadata cleanup commit is reasonable. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data/tree/main "Anilosan15/Synthetic\_Turkish\_TTS\_Data at main"))

### 3. Judge success by the right signals

After the commit, the signals that matter most are:

- header shows `Modalities: Audio, Text`;
- header shows one or more `Libraries`;
- license badge becomes `cc-by-4.0` rather than generic `cc`;
- viewer still works;
- `Expand in Data Studio` still works. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))

### 4. If the header still does not update, treat it as a Hub bug, not your fault

There are enough public examples of viewer/stat inconsistencies on the Hub that I would not keep rewriting your dataset structure forever if the explicit tags do not fix it. Once your metadata is explicit and the backend is still healthy, a persistent missing-badges problem is best treated as **a Hub-side UI/indexing issue**. Public reports about row counts, Data Studio visibility, and stats glitches show that this class of issue does happen. ([Hugging Face Forums](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fdataset-row-counts-missing-from-profile-view%2F171818 "Dataset Row Counts Missing from Profile View! - Beginners - Hugging Face Forums"))

## Bottom line

For your case, my answer is:

- **Is this normal?** Partly. It is not unusual for Hugging Face’s metadata/display layer to be less consistent than the actual dataset backend, and the docs explicitly allow manual YAML tags because auto-detection is not always enough. ([Hugging Face](https://huggingface.co/docs/hub/datasets-cards "Dataset Cards"))
- **Is your dataset broken?** No. The important backend features are already working. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))
- **Are downloads tracked?** Yes, at least currently. The page shows `10`, and HF’s counting rules also make counts look lower than many authors expect. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data "Anilosan15/Synthetic\_Turkish\_TTS\_Data · Datasets at Hugging Face"))
- **What should you do?** Make the README YAML fully explicit: set `license: cc-by-4.0`, add `audio` and `text` tags, add the library tags you want, then let the page re-index. If the header still stays incomplete after that, treat it as a Hugging Face page/indexing issue rather than a dataset-format issue on your side. ([Hugging Face](https://huggingface.co/datasets/Anilosan15/Synthetic_Turkish_TTS_Data/blob/main/README.md "README.md · Anilosan15/Synthetic\_Turkish\_TTS\_Data at main"))