Re: Migration options?
Scott Heaberlin <heabdogg <at> gmail.com>
2008-04-09 04:06:59 GMT
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
On Mon, Apr 7, 2008 at 10:41 PM, Matthias L. Jugel
<matthias.jugel <at> first.fraunhofer.de> wrote:
> Hi,
>
> that's correct. For the conversion I would consider using xslt and a good
> framework around it to act on some of the specific wiki features.
> If you are going to transport the content to another blog or wiki that has
> an XML import you can probably make a transition between the required tags
> easily. However, more difficult is the wiki language, like [ and ] for links
> etc.
>
> It can be done in Java, but intercepting the trancoding of the content tag
> and putting the actual content through a text matcher that changes entities
> and other wiki-language specific parts. Another choice is PHP which I had to
> work with once, and it works quite well if you have to sift through lots of
> data.
>
> If there are questions regarding any of the specifics, just ask please. I
> will try to answer questions.
>
> Regards,
>
> Leo from Seoul.
>
>
>
> On 08.04.2008, at 11:20, Scott Heaberlin wrote:
>
> > I think this is a very appropriate topic.
> >
> > I was in the same situation; I went through the labor of massaging
> > nearly 8 years of blog / personal website content into snipsnap then
> > two years into using snipsnap it goes out of development.
> >
> > While on some paternity leave I ended up writing a small framework for
> > exporting snipsnap data to another wiki / CMS engine. I'm a developer
> > by trade, and I had some free time so I was up for the task. I wrote
> > the app in such a way that I thought it could be extended to export to
> > other systems (I chose to port to Blogger and further submit my soul
> > to Google) but I haven't actually implemented other export schemes.
> >
> > I uploaded the Java code to sourceforge.net nearly a year ago; I
> > suspect it's nearing deletion as I haven't updated the code in a long
> > while (haven't needed to) and I haven't even gotten around to
> > documenting it.
> >
> > That being said, I'd be willing to participate to some degree in an
> > official / grassroots export-app. I know what it feels like to have
> > years of content stuck in a dead, albeit very likeable, CMS / wiki
> > system.
> >
> > Scott Heaberlin
> >
> > On Sun, Apr 6, 2008 at 5:18 PM, Sam Hahn <S <at> mhahn.com> wrote:
> >
> > > Hi - I'm sorry if this is off-topic for the group: I'm a very satisfied
> > > user (since February 2005) of SnipSnap (uttoexeter, of course, on
> > > Postgres). It serves as a family wiki & blog where the kids do their
> > > journaling, and we have family agreements, practices, reference info,
> > > etc. However, I'm wondering since SnipSnap isn't being maintained any
> > > more, whether it's possible to migrate to another framework, eg. Drupal,
> > > MediaWiki, Twiki, DekiWiki, Trac, or SharePoint, or ??. Have others
> > > considered this question? What options might have been considered? How
> > > would one go about doing this migration? Curious. Thanks - Sam
> > > _______________________________________________
> > > SnipSnap-Users Mailing List
> > > snipsnap-users <at> snipsnap.org | http://snipsnap.org/
> > > http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
> > >
> > >
> > _______________________________________________
> > SnipSnap-Users Mailing List
> > snipsnap-users <at> snipsnap.org | http://snipsnap.org/
> > http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
> >
>
> --
> Matthias L. Jugel (마티아스 유겔), M.Sc.
> FIRST Representative, 12F, KGIT Sangam Center
> 1601, Sangam-dong, Mapo-gu, 121-270 Seoul
> Tel: +82 2 6393 3507
> Email: matthias.jugel <at> first.fraunhofer.de
>
> Fraunhofer Institut fuer Rechnerarchitektur und Softwaretechnik, FIRST
> Kekulestr. 7, 12489 Berlin, GERMANY ** http://www.first.fraunhofer.de/
>
>
>
> _______________________________________________
> SnipSnap-Users Mailing List
> snipsnap-users <at> snipsnap.org | http://snipsnap.org/
> http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
>
_______________________________________________
SnipSnap-Users Mailing List
snipsnap-users <at> snipsnap.org | http://snipsnap.org/
http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
RSS Feed