[daisy] Daisy vs Confluence, was: howto move content from one Daisy to another?

[Marc Portier]

Thomas L Roche wrote:
> Tom Roche Tue, 12 Dec 2006 17:30:48 -0500
>>> My group has access to a well-maintained (not by us :-) and
>>> performant Daisy install, so we'd like to consolidate our current
>>> wikis on it.
> 
> Mark Thomas Wed, 13 Dec 2006 11:29:06 -0500
>> I'd be interested to hear the reasons why you're moving from a
>> highly-touted commercial wiki (Confluence) to Daisy.
> 
> Part of it is that the folks who run the Daisy instance to which we'll
> be migrating have done a very good job for a couple of years now, and
> as a result lots of other teams with which we collaborate are already
> on that instance. So one reason is just consolidation.
> 
> That being said, everyone I know who has used both prefers Daisy to
> Confluence. (And that's a lotta folks, since IIUC (and I Could Be Very
> Wrong) the main corporate-supported wiki @ IBM (w3ki) is Confluence,
> but a large part of Rational is using this Daisy instance, so most
> users of the latter also use the former.) Confluence may be easier to
> support, since that seems to be one of its major selling points, but
> Daisy seems easier to use: particularly, the combination of HTML and
> richtext editors excels. (Now, if it was only easier to import from
> one Daisy to another :-)
> 

I know I'ld hate it as an answer: but it will be easier in 2.0

Still, in pre 2.0 installations you have guaranteed open access to your
documents/repositories via the API. The (only) tricky part is the
required link-rewriting in the case you're merging two repositories.
(since the receiving end will have been using the same id's as the ones
you are importing)
It will require some time of a seasoned Java/XML programmer to build you
the custom transferring code though.

While 2.0 continuous to guarantee that open API freedom, it will also
bundle a ready import-export utility for convenience. Based on the
changed ID-scheme in 2.0 which allows to avoid much of the link
rewriting.  A benefit shared to those still wanting to do things
themselves over the API in fact.)


I would advise to schedule reading up on the relevant sections[1] of the
docs before you guys upgrade.

[1] http://cocoondev.org/daisydocs-2_0/impexp


Anyway, for now: "good luck with the custom transfer code" is more
appropriate. Please, report back to this list on progress or with more
detailed questions.



And many thx for the open and honest account of your experiences with
Daisy, heart-warming and much appreciated.

regards,
-marc=
-- 
Marc Portier                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at                http://blogs.cocoondev.org/mpo/
mpo at outerthought.org                              mpo at apache.org