Open SteadyCadence opened 6 years ago
Some thoughts and concerns about solutions:
my
language, then updates that data, if we were to support data entry in the translated language we would need to translate the data back to the system values before sending it to our servers.alias
property that is designed to offer a more readable title. It may be useful for us to put the translated labels for questions in this location, allowing us to preserve the system's name
value.I recommend that we allow a user to enter in a preferred language. If data is available in that language, convert it to that language. Else, keep it as system values. We don't really have a select set of "supported languages" per questionnaire, so rendering a list of used languages would require us to iterate through all questions and options and question groups and create a set of used languages. This does not guarantee that we would have translations for every value (afaik). Additionally, we would probably want to translate the language abbreviations to their long-form, translated versions (eg. en
-> English
).
The questionnaire supports many languages with the XLS Form's label features.
At the moment, the only data that is being pulled and pushed with the QGIS plugin is the "name" columns, which are forced to be Roman characters.
The QGIS plugin should be able to display the multiple languages (of the fields and values) that are stored in Cadasta.
Example project:
https://platform-staging.cadasta.org/api/v1/organizations/example/projects/example_proj/spatial/?format=json
https://platform-staging.cadasta.org/api/v1/organizations/example/projects/example_proj/spatial/?format=json
The questionnaire has a
location_attributes
question group defined, with a single question:type_of_ground
. The location record from thespatial/
endpoint contains an attribute wheretype_of_ground: 'soil'
. Currently, we this data would appear in QGIS' data table under a column titledtype_of_ground
and with a value of'soil'
. This makes it difficult for non-english speakers to understand the data. You can see that translation labels for both the question (type_of_ground
) and the question options (in this case,soil
) are available in English (en
) and Myanmar (my
). It should be possible to view this data in its converted form.