You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before I open new issue with adding/changing class, I want to focus your attention on language property of the specific type of fields. All "free form" fields, especially verbatim and remarks ones can be filled with different languages (or mix of them). For clarity and future usage (for example machine translation) we should add information in which language description is made. Another example is vernacularName where we state organism name, but without information from witch language. Translations of labels or field notes are specific case too, where we have two or more languages in one field.
Draft proposition is to add FieldLanguage class which can be duplicate or linked all over other classes where it is necessary.
Or, if this information can be conveyed by existing terms, please explain how to do so.