[Samoed]

Set citation keys to author_title_year format ref #5724 (comment)

[KennethEnevoldsen]

if we want to standardize should we add a test for it?
What happens in the case of conflicts?

[ayush1298]

The rename also needs to cover a few other files:

1. citation_allowlist.json: It's keyed by citation key, and only 1 key still matches. That's why citation-check-pr fails.
2. citation_cache.json: its entries are keyed by key|doi|arxiv|title|year, so every lookup misses and all entries were checked again.
3. README.md and docs/index.md: they still use muennighoff2022mteb / enevoldsen2025mmtebmassivemultilingualtext, while the dataset card template now uses the new keys. docs/references.bib also has an old key.

[ayush1298]

A few more things adding here as adding on each file was difficult:

1. scripts/tools/update_citation_keys.py:290: the a/b suffix follows title sort order, so a newly added paper can rename an existing key. A run on a subset of paths also misses collisions with other files. Could we keep existing keys, with new ones getting the next free suffix checked against the whole repo?
2. scripts/tools/update_citation_keys.py:181: clean() keeps trailing hyphens, which gives buhmann_domain-_2022 and potthast_touche20-argument-retrieval-for-controversial-_2022. Could it .strip("-")?
3. scripts/tools/update_citation_keys.py:166: TITLE_SPLIT also splits on the . in "Qwen2.5", which gives xu_qwen2_2025. Could it split only on . followed by a space?
4. scripts/tools/update_citation_keys.py:10: the usage path should be scripts/tools/.... The comment at L247 ("undo the common ones") describes something the function doesn't do.
5. tests/test_validate_metadata/test_citation_formatting.py: could we add a test that keys match ^[a-z0-9-]+_[a-z0-9-]+_\d{4}[a-z]*$ and that each key maps to one title?
6. mteb/benchmarks/benchmarks/benchmarks.py:2972: this is still the arXiv @misc, while the task files use the published @inproceedings (argu_ana_pl_retrieval.py:30). After the rename, they share wojtasik_beir-pl_2024, so one key has two different entries. Same for yu_visrag_2025 at L3780 vs visrag_models.py:173. Could these copy the published entries? (I guess I missed them)
7. mteb/tasks/retrieval/eng/touche2020_retrieval.py:40: the title breaks mid-word, which is why the key above ends in -. Could it go on one line?
8. mteb/models/model_implementations/liquidai_models.py:8: author={Liquid AI} gives ai_lfm2_2025. Writing it as {{Liquid AI}} gives liquidai_lfm2_2025.