search

cessda / cessda.cvs.two

Apache License 2.0
0 stars 2 forks source link

Discuss again with DSO and TM about the implementation process of new translations with possible adaptation of the text "Vocabulary Translation" in the Editor User Guide #872

Open Lorenz1983 opened 2 months ago

Lorenz1983 commented 2 months ago

According to Martin Šeleng, the process is oudated and doesn´t match the current procedure. https://vocabularies.cessda.eu/contentguide/translations.html

Lorenz1983 commented 2 months ago

@pakoselo Hello Martin, you can also write the process documentation here.

pakoselo commented 2 months ago

3 digit versioning system: major.minor.patch - major.minor is possible to change only when the new Source Language vocabulary is created (from existing one) by the SL Admin patch - can be changed only in case that new Target Language is created (from existing one) by the SL/TL Admin

Creating/Publishing workflow: Adding a new Target Language (not existing in the current vocabulary bundle). Source Language admin must create a new Source Language with updated major.minor number (automatically the minor number is added by 1). After the status of the Source Language reaches the Ready to be Translated (from DRAFT to REVIEW to READY TO BE TRANSLATED) the SL/TL admin(s) is/are able to add the new translation. TL admin(s) can make new translations and move the TL(s) from DRAFT to REVIEW and to READY TO BE PUBLISHED status. After all TL(s) are moved to READY TO BE PUBLISHED (in case that some of them are still in DRAFT or REVIEW state - the track changes will be lost) the SL admin can publish the whole vocabulary bundle. TL admin is able to add a new version of Target Language (it already exists in the vocabulary bundle) by clicking on the Create new version TL (language). The patch number is increased automatically by 1 and TL admin can update/change/… properties of the TL version. After moving from DRAFT to REVIEW and to READY TO BE PUBLISHED, the SL admin can publish the whole bundle. This will increase the patch number in all TL languages.

john-shepherdson commented 2 months ago

Process for documentation updates