Active
Project:
IMP
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
8 Oct 2013 at 02:14 UTC
Updated:
26 Nov 2013 at 15:24 UTC
Jump to comment: Most recent, Most recent file
Plugin/migrate/source. Will have a base class and a SQL base class. Core likely will only have SQL-derived plugins.source:
id: drupal6_node
process:
-
source: language
destination: langcode
-
source: field_alt_text
destination: image:alt_text
-
id: skip
source: field_foobar
-
source: image
file_plugin: fid
destination:
id: drupal8_node
As you can see, every process item might contain arbitrary configuration data which will be passed to the destination plugin.
Note: more to come! This doesn't yet contain id mapping.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | Migration 1.1 - Current Glossary-1.png | 24.6 KB | eliza411 |
| #1 | Migration - My previous understanding-1.png | 36.23 KB | eliza411 |
| #1 | Migration - Current Glossary-2.png | 34.03 KB | eliza411 |
Comments
Comment #0.0
chx commentedUpdated issue summary.
Comment #1
eliza411 commentedHere's how I visualized the process based on our discussions at PNWDS:
Did I understand correctly and does this revised glossary mean it would be labeled more like this? If so, I'd mostly want to know what we call the source and destination:
Comment #4
eliza411 commentedMy refined understanding, based on clarification from chx in irc:
MigrateExecutable uses the Source, Destination, and Process defined in Migration.
MigrateExecutable reads a row at a time from Source, then passes it back and forth to Process plugins
Process ultimately returns the processed row to MigrationExecutable, which in turns writes it to the Destination.
I'm not sure the diagram is helpful, but it's closer to the process, hopefully:
Comment #4.0
chx commentedUpdated issue summary.
Comment #5
mikeryan