Update README.md

README.md

@@ -1,217 +1,70 @@
 ---
 tags:
-  - embeddings
-  - vector-database
-  - information-retrieval
   - stackoverflow
+  - qdrant
+  - embeddings
+  - retrieval
   - question-answering
-  - semantic-search
-pretty_name: StackOverflow Vector Dataset
+task_categories:
+  - feature-extraction
+  - question-answering
+language:
+  - en
+pretty_name: StackOverflow Vector Snapshot Dataset
 license: cc-by-sa-4.0
 ---
 
-# Dataset Summary
+# Dataset Card for StackOverflow Vector Snapshot Dataset
 
-This dataset contains the vector-retrieval component of Stack2Graph, a retrieval-oriented representation of Stack Overflow content introduced in the paper *Stack2Graph: A Structured Knowledge Representation of Stack Overflow Data for Retrieval-based Question Answering*.
+## Summary
 
-The vector dataset is derived from Stack Overflow questions that match a supported programming-language tag set. It is designed for dense and sparse retrieval workflows and can be exported either from the local preprocessing caches, directly during embedding, or from an existing Qdrant vector index.
+This dataset contains the vector-database component of Stack2Graph as restorable Qdrant snapshots.
 
-As described in the paper, Stack2Graph combines a knowledge graph with a vector database. This Hugging Face dataset card covers only the vector-dataset artifact. The complementary knowledge-graph artifact is documented separately.
+The artifacts are intended for direct restore into Qdrant rather than row-wise reuse as a plain text or parquet dataset.
 
-# Repository Layout
+The repository covers the vector side of Stack2Graph only, not the accompanying knowledge graph artifact.
 
-The uploaded repository stores compressed archive batches for the vector dataset under the `vector_dataset` directory.
+## Repository Layout
 
 ```text
-README.md
-vector_dataset/
+qdrant_snapshots/
+  collections_manifest.json
   archive_manifest.json
-  part_0.tar.gz
-  part_1.tar.gz
-  part_2.tar.gz
+  stackoverflow_python_vector.tar.xz
+  stackoverflow_java_vector.tar.xz
+  stackoverflow_javascript_vector.snapshot.xz.part_000
   ...
 ```
 
-Each archive contains a subset of the exported Parquet shards and may also include the `dataset_manifest.json` file produced by the exporter.
-
-The `archive_manifest.json` file records:
-
-- the archive batch size
-- the number of archive files
-- the exact export files included in each archive
-- a source manifest used to detect whether staged archives still match the current vector export
-
-# Export Layout
-
-The underlying vector export is organized by category and programming language.
-
-When parent-child indexing is enabled, the exported layout follows this pattern:
-
-```text
-question_metadata/<language>/part-*.parquet
-chunk_records/<language>/part-*.parquet
-dataset_manifest.json
-```
-
-When parent-child indexing is disabled, the export instead uses:
-
-```text
-question_records/<language>/part-*.parquet
-dataset_manifest.json
-```
-
-# Record Types
-
-## `question_metadata`
-
-Question metadata shards contain one row per retained question and provide the canonical textual payload used to interpret dense and sparse vector rows.
-
-Columns:
-
-- `question_id`
-- `language`
-- `question_title`
-- `question_full_text`
-- `dense_text`
-- `tags`
-
-## `question_records`
-
-Question record shards contain one row per retained question when parent-child indexing is disabled.
-
-Columns:
-
-- `question_id`
-- `language`
-- `question_title`
-- `question_full_text`
-- `dense_text`
-- `tags`
-- `dense_vector`
-- `sparse_indices`
-- `sparse_values`
-- `export_source`
-
-## `chunk_records`
-
-Chunk record shards contain one row per child chunk when parent-child indexing is enabled.
-
-Columns:
-
-- `chunk_id`
-- `question_id`
-- `language`
-- `chunk_index`
-- `chunk_text`
-- `sparse_text`
-- `dense_vector`
-- `sparse_indices`
-- `sparse_values`
-- `export_source`
-
-# Embedding and Sparse Features
-
-The current pipeline combines:
-
-- dense embeddings from `nomic-ai/nomic-embed-code`
-- sparse lexical features derived from `BAAI/bge-m3`
-
-Dense vectors are stored in the `dense_vector` column when they are available in the export source.
-
-Sparse vectors are stored in split form:
-
-- `sparse_indices`
-- `sparse_values`
-
-This split representation is designed to be Parquet-friendly and easy to reconstruct into sparse retrieval structures in downstream systems.
-
-# Export Provenance
-
-The `export_source` column indicates where a given vector row came from:
-
-- `embed`: written directly during the embedding run
-- `qdrant`: exported from an existing Qdrant collection
-- `cache`: exported from local preprocessing caches
-
-Important note:
-
-- exports from `embed` and `qdrant` include dense vectors
-- exports from `cache` may omit dense vectors and therefore set `dense_vector` to `null`
-
-# Parent-Child Indexing
-
-The default vector pipeline uses parent-child indexing.
-
-In this mode:
-
-- each question remains available as `question_metadata`
-- each question body is additionally split into overlapping child chunks
-- chunk records are the main retrieval rows for vector search
-- `question_id` links each chunk back to its parent question
-
-The current default chunking parameters in the repository are:
-
-- child chunk tokens: `384`
-- child chunk stride: `256`
-
-These values are configurable at export time through the repository pipeline.
-
-# Supported Language Tags
-
-The current pipeline retains questions when at least one tag matches this set:
-
-- `java`, `c`, `c++`, `python`, `c#`, `javascript`, `assembly`, `php`, `perl`, `ruby`, `vb.net`, `swift`, `r`, `objective-c`, `go`, `sql`, `matlab`, `typescript`, `scala`, `kotlin`, `rust`, `lua`, `haskell`, `cobol`, `fortran`, `lisp`, `erlang`, `elixir`, `f#`, `dart`, `shell`, `bash`, `powershell`, `css`, `html`, `.net`, `julia`, `prolog`, `abap`
-
-The `language` field in export rows is the normalized language bucket used by the repository pipeline.
-
-# Construction Pipeline
+Each language is stored as exactly one restore unit:
 
-The dataset is built from the Stack Overflow XML dump through the following stages:
+- a single `tar.xz` archive for regular-size snapshots
+- split `xz` parts for oversized snapshots
 
-1. XML data is ingested into SQL tables.
-2. Questions tagged with at least one supported programming-language tag are selected.
-3. Question text is cleaned and normalized.
-4. Sparse lexical features are generated.
-5. Optional parent-child chunk records are generated.
-6. Dense embeddings are computed and uploaded to Qdrant.
-7. The final vector dataset is exported as Parquet shards and packaged into `.tar.gz` archive batches for Hugging Face upload.
+## Content
 
-The main repository components involved are:
+The snapshots represent per-language Qdrant collections derived from Stack Overflow questions tagged with supported programming-language tags.
 
-- `vectorDatabase/getQuestions.py`
-- `vectorDatabase/preprocessing.py`
-- `vectorDatabase/embed.py`
-- `vectorDatabase/export_vector_dataset.py`
-- `vectorDatabase/upload_hf_vector_dataset.py`
+Each collection stores the vector index used by the Stack2Graph retrieval pipeline.
 
-# Intended Uses
+The current pipeline covers major programming-language tags such as Python, Java, JavaScript, C, C++, C#, Go, Rust, TypeScript, SQL, Shell, and additional languages used throughout the project.
 
-This dataset is intended for:
+## Intended Use
 
-- retrieval-augmented generation
-- semantic search over Stack Overflow questions
-- hybrid dense+sparse retrieval
-- chunk-level code and technical-text retrieval
-- evaluation of retrieval pipelines over programming-language-specific Stack Overflow subsets
+This dataset is meant to be downloaded and restored into a running Qdrant instance.
 
-# Limitations
+The repository manifest files describe which artifact files belong to which Qdrant collection.
 
-- The dataset only includes questions that match the repository's supported language-tag list.
-- A question may appear in multiple language buckets if it carries multiple supported language tags in earlier pipeline stages.
-- Dense vectors may be missing when the dataset is exported from local caches rather than from embedding output or Qdrant.
-- Chunk boundaries are heuristic and token-window-based, not semantic.
-- Sparse features are lexical approximations and should not be treated as full inverted-index statistics.
-- The export inherits the biases, moderation artifacts, language imbalance, and temporal drift of Stack Overflow content.
-- Textual content is derived from Stack Overflow posts and may contain markup artifacts, noisy formatting, or incomplete context.
+It is primarily intended for retrieval experiments and system reconstruction, not for direct training from the packaged artifacts.
 
-# Licensing
+## Source
 
-This dataset is distributed under the `CC-BY-SA-4.0` license.
+The snapshots are generated from Stack Overflow data after preprocessing, embedding, and Qdrant ingestion in the Stack2Graph pipeline.
 
-If you redistribute derived artifacts or use this dataset in downstream resources, you should preserve the attribution and share-alike requirements of `CC-BY-SA-4.0`.
+## License
 
-# Citation
+This dataset is distributed under `CC-BY-SA-4.0`.
 
-If you use this dataset, cite:
+## Citation
 
-TODO
+If you use this dataset, cite the Stack2Graph project and preserve the attribution requirements of `CC-BY-SA-4.0`.