CivicDataLab / CivicDataLab/IDS-DRR-Data-Management
i18n options for imported indicators and geographies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Imported indicators and geographies have a single language name.
If we want to support i18n later, we can add a model for translations, and make it available in the Django admin.
Another option is to do translation in the source files (e.g. indicatorTitle_es, etc. columns), but I don't think that matches the flow of the project.
Or, we can have entirely separate deployments for each language backend. This is simplest to develop (just change the backend API base URL when switching languages), but probably the most work to operate (sync geometries, etc.).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the imported indicator and geography models, the Django admin flow, and the source-file columns mentioned in the issue. Compare the proposed translation-model, translated-source-column, and separate-deployment approaches; this issue is done when one approach, its data and admin changes, and its deployment implications are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, database, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100