d6_term_node migration overwrites node changed timestamps

Created on 24 June 2016, over 8 years ago

Updated 25 December 2023, 11 months ago

Problem/Motivation

The d6_node migration preserves the original 'changed' timestamp for nodes on migration. But, then the d6_term_node migration comes along and sets 'changed' to the import time for any nodes with term references.

Proposed resolution

#2597650: Term references should be incorporated into D6 node migration → would prevent this from happening by migrating the whole node in the first place. Alternatively, though, if we don't get that change in it probably could be fixed by

Adding a changed: changed mapping to d6_term_node.yml.
Adding .changed to the fields returned by the source plugin's query().

Remaining tasks

Implement the fix above (novice task).
Write a fail test (validating that the changed timestamp after running both d6_node and d6_term_node matches the original D6 timestamp). (less novice)

🐛 Bug report

Status

Closed: duplicate

Version

9.5

Component

Entity →

Last updated 2 days ago