Use-Case: Successfully migrated a content-type w/ 11 CCK fields. Few days later, realization a 12th 'node reference' field was left out.

What is the best course of action to update previously migrated content?

  1. Use SystemofRecord(Destination)? Just add the field you need to do in a new class? ex. class beerUpdate?
  2. Edit the original class by adding the node-reference field in the mappings? And then when migrating append --update to the end?

Having trouble understanding where appending --update to the end of a migration class is appropriate ? Is it only used when using SystemOfRecord? Thanks for the wonderful module.

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Fixed

#2. --update doesn't have anything to do with systemOfRecord - it's for exactly your scenario, as well as cases where the source data is changing and you want to make sure you pull all the updates.

chadchandler’s picture

chadchandler commented

Thanks Mike

Through 'Trial-and-Error' I've started to use --update in place of SystemOfRecord<i>(Destination)</i>

Can you provide an example where --update would not work and using SystemofRecord would be called for?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

If you have data on the Drupal side you don't want overwritten by the migration, you would set your systemOfRecord to DESTINATION, and leave the fields you want to preserve unmapped. See http://drupal.org/node/1117454.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

killtheliterate’s picture

killtheliterate commented

Somehow I can't get --update to work.
drush migrate-import UnitedProductDisplay --update
Unknown option: --update. See `drush help migrate-import` for [error]
available options. To suppress this error, add the option
--strict=0.

killtheliterate’s picture

killtheliterate commented

I was a version off on migrate. Works now.