Open seanmacavaney opened 2 years ago
As the structure of this collection will be very similar to HC4, should we just reuse HC4Doc
defined in ./datasets/hc4.py
?
Yup, you can give the format a name and move them under ir_datasets/formats/
@seanmacavaney
For the directory and namespace structure, do you think neuclir/22
would be better (both neuclir
and neuclir/22
are dummy levels)? This could accommodate future datasets/topics to be under neuclir namespace without.
I am revisiting this and hopefully adding NeuCLIR 22 topics and queries as well.
Dataset Information:
"The main task for the proposed track is ad-hoc cross-language retrieval. Documents will be drawn from Common Crawl newswire, and will be written in Chinese, Russian, and Persian. Topics will be in English, and will be expressed in traditional TREC title/description/narrative form. Retrieved documents will be graded as highly relevant, somewhat relevant, and not relevant; we expect to use several metrics to evaluate runs, including nDCG@100 and ERR."
Links to Resources:
Dataset ID(s) & supported entities:
Checklist
Mark each task once completed. All should be checked prior to merging a new dataset.
ir_datasets/datasets/[topid].py
)tests/integration/[topid].py
)ir_datasets generate_metadata
command, should appear inir_datasets/etc/metadata.json
)ir_datasets/etc/[topid].yaml
)ir_datasets/etc/downloads.json
).github/workflows/verify_downloads.yml
). Only one needed pertopid
.downloads.json
.Additional comments/concerns/ideas/etc.
cc: @eugene-yang