Exporting to HTML and then parsing the result is a pretty good idea actually. I might give it a shot when I have a bit more time.
Thanks for your help!
Thanks, slowly but surely it gets better with each new release.
* At present I have no plans on importing from Surfulater. The main problem being that Surfulater has no export capability.
* Clibu has a snapshot capability already, however I haven't exposed it's user interface as yet.
* Search across KBs is definitely coming.
Apologies for the delay replying, but I put it on the back-burner over the xmas break so I could focus on new Clibu development and planning.
Would it be difficult to build out an export capability, or potentially something we can build out ourselves? From memory the data is stored in a sql lite database in a non-proprietary format (I don't know what the clibu interface is like.. I assume it has a REST interface?).. I suppose the mapping wouldn't be exactly 1-1 given that clibu has no folders (so you'd have to create the equivalent hierarchical tags in clibu)
Surfulater content is stored across three databases which is pretty messy. I doubt whether there is an easy way to directly access the databases to extract what's needed for export.
There is no REST interface, nor a HTTP Server in Surfulater.
The only thing I can think of that may be possible is to use Surfulater's Publish to Web KB capability and then process the html output files and convert them into a format suitable for importing into Clibu.
Note that Clibu doesn't have import/export yet, but both a coming.