Contrib.social

Provide migration path for D7 Kaltura

Open on Drupal.org →
Created on 22 February 2024, 4 months ago
Updated 26 February 2024, 4 months ago

Problem/Motivation

Hello!

If a Drupal 7 site is using this module - https://www.drupal.org/project/kaltura → - and they have the field_kaltura_entryid field type attached to certain nodes this will throw an error during migration.

I believe this module accomplishes the same thing but in a D8+ manner and as such we should be able to provide a migration path from D7 --> D10 using a migrate field plugin → .

Steps to reproduce

  1. Install Kaltura on a D7 site
  2. Add the field_kaltura_entryid field to a content type
  3. Create a new Drupal 10 instance
  4. Connect the D7 site to the D10 instance for migration
  5. Run drush mim d7_field:node
  6. Verify error message

d7_field:node:type: Can't migrate the '<your_d7_field_name>' field storage for 'node' entities, because the field's type 'field_kaltura_entryid' is not available on the destination site.

Proposed resolution

Provide a migrate field plugin that maps the old field type to the new one

Remaining tasks

User interface changes

n/a

API changes

n/a

Data model changes

n/a

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States dan612 Portland, Maine

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @dan612
  • Comment 4 months ago →
    🇺🇸United States dan612 Portland, Maine

    attaching a basic file to get started. i believe using this will at least stop the warnings/error during a migration and will allow this new field type to be set, but i believe we need to define how the underlying data gets mapped to the new field as well.

  • Comment 4 months ago →
    🇺🇸United States jienckebd

    Great start Dan!

    As you noted, the data does need to be mapped in 2 ways:

    1. D10 field property "entry_id" was field property "entryid" in D7.
    2. D10 field property "partner_id" was a Drupal variable applied to all Kaltura field values.

    The attached patch works on a sample client.

    There may be a better way to map a D7 Drupal variable to a D10 field value property. But the only examples I saw for mapping D7 variables required a "variable" source plugin, while MigrateField plugins have their own source plugin.

  • Merge request !33423262: Migration from D7 kaltura module. → (Open) created by jienckebd
contrib.social Blog FAQ Discussions
Production build 0.69.0 2024