Migration to FeedAPI

Hi Mike,

Migration - yess!!

I would write a module that you turn on and that then either runs automatically or runs on a certain path the upgrade script. Only give user 1 the permission to run this script - I think update.php is a good example that we should follow.

Use those functions for increasing execution time and available memory:

ini_set('memory_limit', '200M');
set_time_limit(60*10);  

(make sure to wrap them in a test wether they are actually available on the host).

I would add the module to the project (the leech project in our case) - not on a seperate project on d.o. From this point of view it doesn't seem so overkill-y to me...

Let's see the possibilities:
- the to-be-migrated module has a separate module to handle the migration
- FeedAPI handles the migration from several aggregation-modules

For the user maybe the most comfortable if after enabling the FeedAPI, it simply solves the migration. BUT: migration is not a trivial task, so there are differences between the sites. I do not think it's reasonable to write in FeedAPI flexible migration paths to the most of the aggregation modules.
So I also advice to create a separate module for the migration, then share it on your project page. Migration is for the skilled users, they'll know how to customize the migration module.

any word on the migration module? Interested in moving to feed_api on site that is under construction....

thanks,

art

http://drupal.org/node/189464