Problem/Motivation
Right now, d7_rdf_mapping is a monolithic migration. It would be nice to derive these migrations per entity type and per bundle, and skip those rdf mappings whose destination entity (type) is missing.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | interdiff-3115073-4-7.txt | 4.67 KB | huzooka |
| #7 | core-derived_rdf_mapping_migration-3115073-7.patch | 6.98 KB | huzooka |
| #4 | 3115073-4.patch | 5.4 KB | wim leers |
| #4 | interdiff.txt | 1.07 KB | wim leers |
| #2 | core-derived_rdf_mapping_migration-3115073-2.patch | 4.97 KB | huzooka |
Comments
Comment #2
huzookaComment #3
huzookaComment #4
wim leersThe
migration_dependencieswere not yet being updated.Comment #5
wim leersLooks like this generates a
d7_rdf_mapping:taxonomy_term:forumsvocabulary. Butforumsis just the D7 bundle, we have to use logic like in\Drupal\taxonomy\Plugin\migrate\process\ForumVocabularyto make sure we use the correct destination bundle.Comment #7
huzookaComment #10
quietone commentedChanging component so mgirate maintainers will see this.
Comment #14
quietone commentedRDF is deprecated in 9.5 and removed in Drupal 10, moving to the contrib project.
Comment #15
smustgrave commentedSo unfortunately this didn't land and migrations are going to be removed from 4.0.x (soon to release) now that migrate_drupal is now deprecated too. I am assigning credit though
Thanks.