migration

Hi Folks,

Just wondering if there is anyone in this group working on ning to drupal migration tools? Its is possible to get all the data out of a Ning network using the Ning Archiver tool:
http://help.ning.com/cgi-bin/ning.cfg/php/enduser/std_adp.php?p_faqid=3796

But it'd be really great if this project were able to build a module/ or write a tutorial about how best to get the data IN to a fresh drupal install.

Is anyone working on this?

Thanks,

Josef.

I'm working with two stacks - Acquia on my desktop and XAMPP on my laptop. (And I'll be using LAMP at Modwest, my hosting service.)

My understanding is I should be able to move a completed SITE back and forth between these, but it is my responsibility to make sure the needed MODULES are in place across all of the installations. Is this correct?

I found this presentation today from the guys at Yale who transitioned to Drupal: http://dl.dropbox.com/u/5585354/Drupal_On_Demand_PICC10.pdf

This presentation is for a technical audience, as it is mostly a discussion of the architecture. Very good stuff.

Hi! I haven't seen anything mentioned here about helping folks who aren't up to speed with Git getting up to speed with Git (couldn't resist). So -

The biggies -

• The official Git site.

There's some good stuff on here, especially the Book. The Book starts at the beginning, and I can't tell you where it ends, because I just haven't had to get that far with it yet.

• GitHub.

I'm working on a fairly large migration project. For this project, I will be migrating legacy data into Drupal 6. For this, I would like to create a new node with a specified nid so I can import data and maintain correct paths. I have looked everywhere for any tips on how to accomplish this, however, it doesn't seem like a very common practice. I have considered adding aliases, but for my case, I really feel like if I can directly map legacy ids to drupal nids, it will really make my life easier down the road. Has anybody had success doing anything like this?

I recently developed a website for a film festival.
People registered their film with a webform. After that, every film had to be re-added as regular nodes to appear on the website.
I had no time at that particular time, but I thought about a module migrating webform results to nodes, like Migrate does with databases, mapping webform fields to node & cck fields.
I've found nothing similar, does someone has ever seen a module doing that?

As we all know, one of Drupal's major shortcomings is exporting configuration. I believe that the source of this problem is that there is no standard way to store and retrieve settings. Most modules use variable_get and variable_set. The problem with this is that there is no association between a variable and a module.

I propose an api for saving and retrieving settings. I am currently working on a settings module as a proof of concept.

Here is a glimpse of the current api:

I'm in the middle of implementing Update migrated content in-place, while thinking ahead to Workflow integration. The checkboxes on the current dashboard basically are defining a default workflow, for use by cron processing or the drush migrate all command, and adding the update option is making this just a little too complicated. So, I'm going to take a little poll here, followed by a description of what I'm thinking of in terms of a V1 dashboard and workflow approach, while anticipating a full implementation of defined workflows in a future version.

Here it is: http://drupal.org/node/570906

Let me know if there are any grievous errors.

-glass.dimly