-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: use structure sync to track Taxonomy term, Menu and custom block updates. #44
Comments
see miura/bise@1b5a364 for and example structure_sync.data.yml This was the status in October. |
Export process worked nicely, cin worked nicely but then import taxonomy got stuck. Inverstigating.. |
ok, some patch pending and open issue, maybe not ready for using .. Let's Watch the next version, for now not ok. https://www.drupal.org/project/issues/search/structure_sync?status%5B0%5D=8&status%5B1%5D=13&status%5B2%5D=14 |
Revival: please agree to use this module, to avoid the disappearance of contributions like we are seeing this time... |
In terms of importing, doing it from the GUI works. |
@florian-levet @PerrineGilloteaux @vcaldas
please comment.
Updating the workflow for taxonomy terms
Kota
20181023
Current way of Adding, Editing, Weighting Taxonomy Terms
Up until October 2018 Taggathon, taxonomy terms incuding BISE ontology was handled in the following way.
Recommended update in the workflow
By using an add-on package "structure sync", it's possible to export taxonomy terms as yml file and handle them just like other settings.
Expexted workflow is as following
Exporting taxonomy updates from database to yml file
drush export-taxonomies
and it will be ready to be exported as files (changes at this stage only happens within the database)drush config:status
(short formdrush cst
). If there is difference, you should see structure_sync.data.yml in the list.drush cex
(config:export) will updatestructure_sync.data.yml
file according to the updates in the database.git add .
&git commit - m "taxnonomy updated"
or so will add these changes to the version tracking.git push origin <branch name>
dev
branch. Wait (or insist) someone else to merge the PR.What Florian can do from now on, is these 7 steps. Extract taxonomy from Webprotege and update your local drupal database using the python script. Then follow step 1 to 6 to push the changes to the Github repo.
Importing taxonomy updates from file to yml file
git pull upstream dev
pulled any change instructure_sync.data.yml
, If this happened, then taxonomy term has changed and you need to do the following.drush cim
(config:import) to update your local database using updated yml file.drush import-taxonomies
to update taxonomy.The text was updated successfully, but these errors were encountered: