Datasets:
[bot] Conversion to Parquet
The parquet-converter bot has created a version of this dataset in the Parquet format in the refs/convert/parquet branch.
What is Parquet?
Apache Parquet is a popular columnar storage format known for:
- reduced memory requirement,
- fast data retrieval and filtering,
- efficient storage.
This is what powers the dataset viewer on each dataset page and every dataset on the Hub can be accessed with the same code (you can use HF Datasets, ClickHouse, DuckDB, Pandas, PostgreSQL, or Polars, up to you).
You can learn more about the advantages associated with Parquet in the documentation.
How to access the Parquet version of the dataset?
You can access the Parquet version of the dataset by following this link: refs/convert/parquet
What if my dataset was already in Parquet?
When the dataset is already in Parquet format, the data are not converted and the files in refs/convert/parquet are links to the original files.
What should I do?
You don't need to do anything. The Parquet version of the dataset is available for you to use. Refer to the documentation for examples and code snippets on how to query the Parquet files with ClickHouse, DuckDB, Pandas or Polars.
If you have any questions or concerns, feel free to ask in the discussion below. You can also close the discussion if you don't have any questions.
Thanks for enabling the Parquet conversion and Dataset Viewer for this repository.
For this specific dataset, I’ve observed that the auto-generated Parquet / Viewer layer exposes a single text stream that mixes the contents of all text-based files (including LICENSE.txt, README.md, CHANGELOG.md, and the 16 HTML manifesto files), rather than presenting the 16 HTML manifesto documents as 16 separate, file-level records.
In practice, this means the Hugging Face Dataset Viewer (and any embed relying on it) is not suitable for document-accurate access to the multilingual manifesto itself. The canonical units of this artifact remain the individual HTML files in the “Files and versions” view, and I’ve updated the README / dataset card to explain this limitation explicitly for future users.
If there are any recommended patterns or planned improvements for representing multi-file textual artifacts (like a set of HTML documents) more faithfully in the Viewer / Parquet layer, I’d be very interested to align this dataset with those best practices. Otherwise, I’ll treat this conversion as a helpful technical preview for text experiments, but not as a structural representation of the underlying DIO/ODI manifold.
Thank you again for providing the Parquet conversion and Viewer infrastructure – even this limited preview layer is still appreciated.