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
When research teams login to the Translations app, they are able to select from an extensive list of languages and create project-level translations for any of the listed options. However, the platform only fully supports a limited number of languages for PFE (and even fewer for FEM), where translations are available for shared, platform-level content. From the Translations app, there is no indication that a certain option will not be able to be published. It is only when the research team goes to "publish" the translation that they see there is no option to do so.
Proposed Behavior
While it is useful to allow creation of translations for currently unsupported languages (i.e., this is how a team would start the process of communicating with the Zoo team and get recruited to contribute platform-level content; I don't advocate for limiting the in-app list to only fully supported languages), I propose we provide early feedback about the absence of platform-level content for a selected language. Adding pop-up messaging would also provide an in-app opportunity to present the research teams with info regarding the process for contributing platform-level content, whereas currently that only exists as a canned response distributed to teams if they get to the point of writing in to contact@zoo.
The text was updated successfully, but these errors were encountered:
Current Behavior
When research teams login to the Translations app, they are able to select from an extensive list of languages and create project-level translations for any of the listed options. However, the platform only fully supports a limited number of languages for PFE (and even fewer for FEM), where translations are available for shared, platform-level content. From the Translations app, there is no indication that a certain option will not be able to be published. It is only when the research team goes to "publish" the translation that they see there is no option to do so.
Proposed Behavior
While it is useful to allow creation of translations for currently unsupported languages (i.e., this is how a team would start the process of communicating with the Zoo team and get recruited to contribute platform-level content; I don't advocate for limiting the in-app list to only fully supported languages), I propose we provide early feedback about the absence of platform-level content for a selected language. Adding pop-up messaging would also provide an in-app opportunity to present the research teams with info regarding the process for contributing platform-level content, whereas currently that only exists as a canned response distributed to teams if they get to the point of writing in to contact@zoo.
The text was updated successfully, but these errors were encountered: