Term references should be incorporated into D6 node migration

Created on 20 October 2015, over 9 years ago

Updated 21 May 2025, 13 days ago

Problem/Motivation

Right now, the relationships between taxonomy terms and nodes are migrated in their own migrations - the d6_term_node and d6_term_node_revision templates are instantiated once for each vocabulary (or is it each vocabulry/node type combination?). This means that during a migration process, any given node is saved not only by the node migration, but is again saved for each vocabulary it references, which is... inefficient. It's also illogical - the node migration should be complete in itself and not require additional migrations to "finish" it. The node migrations should pull in and map the term_node relationships directly.

Proposed resolution

Do it.

Remaining tasks

Add tests for new solution
Add deprecation notices to old
Remove old term node migration (but keep the source for BC)
Make sure there are BC tests for term node migrations

User interface changes

n/a

API changes

n/a

Data model changes

n/a

📌 Task

Status

Postponed

Version

11.0 🔥

Component

migration system

Created by

🇺🇸United States mikeryan Murphysboro, IL, USA

Live updates comments and jobs are added and updated live.

migrate-d6-d8

neworleans2016

Performance
It affects performance. It is often combined with the Needs profiling tag.

Baltimore2017

Needs change record
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

CSKyiv18

Needs tests
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 13 days ago →
🇳🇿New Zealand quietone
The Migrate Drupal Module was approved for removal in 📌 [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL Fixed .

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 📌 [12.x] [Meta] Tasks to remove Migrate Drupal module Postponed and the removal work in 📌 [12.x] [Meta] Tasks to remove Migrate Drupal module Postponed .

Migrate Drupal will not be moved to a contributed project. It will be removed from core after the Drupal 12.x branch is open.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024