home edit page issue tracker

This page pertains to UD version 2.

Metadata harmonisation: align spoken-data fields with UniDive naming conventions

Back to Abaza ATB · Back to index

Repo: https://github.com/UniversalDependencies/UD_Abaza-ATB

Cross-posting from the UniDive WG1 T1.5 (spoken language guidelines) metadata harmonisation review. We compared UD_Abaza-ATB’s current CoNLL-U metadata against the proposed naming conventions (see also the full treebank status table). This is a suggestion for maintainers to review - feel free to push back on anything that doesn’t fit the corpus.

1. Document-level (naming conventions)

Field Suggestion
text_name this is a document identifier but is wrongly repeated on every sentence (only 6 distinct values across 98 sentences) — convert to # newdoc id = ... set once at the first sentence of each of the 6 documents, dropping the per-sentence repetition and the .eaf extension
no genre field exists, even though topics are recoverable from the text_name filenames (e.g. Professija = “profession”, O_muzhe = “about (my) husband”, Deti_v_pole = “children in the field”) — these read as personal narrative/interview elicitations; could add # genre = narrative or interview per document, please confirm
no sound_url field, though the corpus homepage (lingconlab.ru/spoken_abaza) implies underlying audio recordings exist — could individual recording links be added?

2. Speaker-level (naming conventions)

Field Suggestion
no speaker metadata exists at all. The 6 text_name filenames each seem to encode one speaker/informant (e.g. AjsanovaFB, SanashokovaCKh, DzhuzhuevKM) — once text_name becomes newdoc id, could a speaker_id be derived from the same filename component?

3. Sentence-level (naming conventions)

Field Suggestion
text_orth this is a morpheme-segmented orthographic form (hyphens mark morpheme boundaries, stress marked) rather than a duplicate of text — rename to text_morphemic
text_transcription this is a Latin-script rendering of the Cyrillic orthographic form, not a phonetic/IPA transcription — rename to text_transliteration

This issue was prepared as part of the UniDive WG1 T1.5 spoken language guidelines effort. Happy to help implement these changes ourselves if that’s easier than doing it on your end - just let us know.