Add new data fixtures translations to existing installations
For instance the Publication status "Published" has been translated into 29 cultures:
But installations that have been upgraded from previous versions of AtoM may only have a fraction of these translations. For many taxonomies the terms can be manually added via the UI as a workaround, but the Publication status taxonomy is "locked" and not editable via the UI.
The ideal solution would be a general-purpose data migration or CLI script that would read the fixtures file and automatically add new translations for existing terms to the database.
#5 Updated by Dan Gillean about 4 years ago
- Priority changed from Medium to High
- Target version changed from Release 2.3.0 to Release 2.4.0
Bumping this forward rather than removing the milestone and bumping up priority so we try to include it in the next release - if volunteer contributed translations are not getting into our releases, we should prioritize it so as not to alienate our wonderful volunteers!
#6 Updated by Dan Gillean about 4 years ago
- Project changed from Access to Memory (AtoM) to AtoM Wishlist
- Category deleted (
- Target version deleted (
Actually, after clarification, moving this to the wishlist. It would be really nice to get this into a future release, but it is apparently a pretty big piece of work. User-submitted translations for UI elements are still getting into our releases, and new installations should have all terms translated. This affects new translations of existing terms for users who upgrade from an older version of AtoM. It would be great to see this improved, but it will require sponsorship for us to really be able to investigate and solve.
#8 Updated by José Raddaoui Marín over 2 years ago
For those restricted taxonomies, which terms can't be updated through the GUI, the script attached in https://projects.artefactual.com/issues/11906#note-5 could be used from the CLI to add/modify/remove any translation to the term name.
#10 Updated by José Raddaoui Marín 3 months ago
I just found a function (that I think was executed only in the 1.2 upgrade) to update existing resources based on the fixtures files:
It may need some tweaks, but it shouldn't be hard to adapt it for the new versions and run it on each upgrade task call.