Boris Pereira | 9 Apr 11:32
Picon

Re: Migration options?

Scott,

I am a bit confused, what exactly is the output format of your export?
Is it any "standard" wiki db format ? Something an other wiki can import
? (if so which one ?)

Boris Pereira

Scott Heaberlin wrote:
> Leo -
>
> My approach was to use hibernate to read from the database into model
> objects, then take that data and feed it into an import api (like I
> said, I wrote my own using Google's Feed api for Blogger).  In
> hindsight I was only able to do this because I accepted the limitation
> of not having access to SnipSNap attachments and limiting the export
> to blog entries on the main snip only.  I'd be happy to share the
> source (it's already on sourceforge) ; I believe with a little work it
> could be generic enough to support export from snipsnap DB or XML
> dump.
>
> I also hooked into SnipSnap APIs to render macro content (worked for
> most macros) in HTML prior to importing into the target blog system;
> that met my needs for the most part.
>
> The code I started with (undocumented, use at your own risk, ASL2.0,
> blah blah blah) is stored in SVN on sf.net:
> http://sourceforge.net/projects/snipsnap-export/
>
> Note - there are some pretty obvious places where someone else would
> want to clean up / alter for their own use.  But I couldnt think of
> another place to store the code and didn't want to just sit on it.
>
> -Scott Heaberlin
>
>   

Gmane