> Thanks Nico for your wisdom. After considering my options, I think
> it's most practical to write an import/conversion-tool and do a
> manual export/import periodically (In my use case this procedure
> will probably be done on a weekly basis).
Good choice :)
The way I usually did this was to use the syncnodes builder to keep
the relation between the externally imported data and the data that is kept in the database.
This helps performing better imports. The downside with regular imports that merge is that you have to handle data that was removed in a separate batch.
I always did things like this using the rmmci . It;s slow,but great when developing and can be started from the command line.
There is also the remote publishing framework http://mmapps.sourceforge.net/remotepublishing/ that might give you ideas
success!
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
