Avoid unnecessary ES update of related description when a term name is changed through the GUI
|Category:||Performance / scalability|
|Target version:||Release 2.5.0|
|Google Code Legacy ID:||Tested version:|
When a tern name is changed, it triggers an update for all its related description in ES. This is necessary for terms that are fully indexed inside its related description, but it isn't for terms where the related description only store the term id.
Also, that update should be done asynchronously, as noted in #11855.
#5 Updated by José Raddaoui Marín over 1 year ago
- File update_term_name.php added
Attached is a script to update a term name and its related archival descriptions in the ES index. It allows to add/edit/remove the term name on any culture.
Execution example, from the AtoM folder:
$ php symfony tools:run update_term_name.php Have you created a backup of the database? [y/N]: y Enter taxonomy name (case insensitive): material type Enter taxonomy name culture (default: en): Enter current term name (case insensitive): graphic material Enter current term name culture (default: en): Enter new term name (leave empty to remove): Photographs Enter new term name culture (default: en): Term name updated. Updating related descriptions ..... Done! - 17 descriptions updated.
#12 Updated by José Raddaoui Marín over 1 year ago
- Status changed from Feedback to QA/Review
- Assignee changed from José Raddaoui Marín to Dan Gillean
Only places, subjects and genres should trigger the update of its related descriptions after this changes. And they should do it using a job and showing a notification.