Timeline for Migration bringing in duplicate taxonomy terms
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2016 at 9:05 | comment | added | UltraBob | My source data is correct for the system I'm migrating from, but is in a state that needs to be improved since it currently provides no utility. The answer I wrote here addresses that. | |
| Mar 8, 2016 at 9:02 | comment | added | Jan Baelemans | High UltraBob, seems you have to apply the first rule of migration. Ensure that your source data is correct. So first dedub your source and make sure there is only one occurrence per term is present. Then do the migration. Otherwise you have to do all sorts of acrobatic during your migration. | |
| Mar 8, 2016 at 0:23 | comment | added | UltraBob | Neither of those do what I want. dedupe ensures that each term comes in as unique, which is the behavior I am trying to avoid. Select distinct will mean that there is only a migrate map mapping for one of the instances of the term. What needs to happen is for there to be a row in the migrate map for every source, but for all identical sources to map to the same destination. This enables future node migrations to properly map terms onto the nodes. | |
| Mar 5, 2016 at 16:38 | review | First posts | |||
| Mar 5, 2016 at 17:38 | |||||
| Mar 5, 2016 at 16:36 | history | answered | Jan Baelemans | CC BY-SA 3.0 |