[daisy] Daisy Wiki Inquiry

[Marc Portier]

Pienaar Wehrner wrote:
> I am researching Daisy Wiki and I am having trouple getting answers to the following questions.
> 

Most answers are to be found in

* the documentation
http://cocoondev.org/daisydocs-2_2/154-cd.html
* the knowledge-base
http://cocoondev.org/kb/1-dsykb.html

Treat yourself to the read!

Anyway, you've catched me on a rare morning where proza is dripping off 
my fingertips, so here are some quick responses anyway.


> D1. Can blogs be monitored?
> 

Unsure what you understand with 'monitoring' but it's rather easy to 
build a custom rss feed for daisy-documents that meet any criteria you 
can express in the daisy-query-language.

On the other side of things it should be fairly easy to use the built-in 
apache cocoon to read external rss feeds and syndicate and blend that 
content into your own pages.

Note though that Daisy does not come with a ready blog application (on 
either side of the feeds)

Building a blog on top of Daisy is pretty much your typical hello-world 
kind of thing to build, so very do-able indeed.


> D2. Can blogs be reviewed before being published?
> 

yes.
You can build in such checks through ACL controlled 'publish', but you 
can also build up your own and elaborate workflow in our embedded 
workflow system

> D3. If blogs and discussions are supported then can they be referenced in articles?
> 

Sure, however you organize your document schema, all 'documents' in 
daisy are stored in a similar way, and can be referenced easily


> D4. What are the space limitations? (i.e. Page limitations)
> 

Technically there are very little absolute boundaries. (There is of 
course your disk's size and Long.MAXVALUE for the various used id's)

Anyway what do you mean? Number of pages or size of 1 page?

Size of 1 part in a page is limited but configurable and tested with 
ridiculously large settings.

Catering for the number of pages in the repo might introduce some tuning 
of the cache to keep things practically acceptable.  By default it is 
set to hold 10000 documents and take approx 256 MB of memory.  This can 
be tuned/modified to cater for larger deployments (one needs to make 
sure the memory-setting grows along).

YMMV and it is hard to predict performance in typical environments, we 
know about deployments that have scaled well above the default cache.


> D5. Can it force users to follow a certain teplate or standards for writing?
> 

The document-type itself works as a schema (template?) of parts and 
fields to fill in.

Additionally you can easily provide 'master' or 'template' instances of 
those with ready filled content to clone from (through duplicate action)

> D6. What type of information is maintained or can be maintained for each document?
> 

See document-types and schema.
http://cocoondev.org/daisydocs-2_2/373-cd/378-cd.html

> D7. What are the space limitations? (i.e. Page size limitations)
> 

ah here is the page size question then,
see above.

> D8. How many plugins are there for the wiki currently? (+/-)
> 

The daisy architecture itself is rather flexibly build up, but we see 
very little people tweaking the plugins being launched (so most of the 
time everybody just runs all plugins shipped with the project)

Next to those there is no real ecosystem of shared plugins, extensions 
or re-usable mini-applications.  Some people do share their work and 
insights on this list, the issue tracker, or the community wiki @ 
http://cocoondev.org/wiki/210-cd.html

This lack of ready and reusable customizations is probably due to two 
things:
* probably the size of the community has yet to reach some threshold 
and/or maturity
* lack of standardized way for people to bundle up and share their extra's


> D9. Is Ability to mark documents as confidential, with different status (i.e. complete) and with different priority available.
> 

Just provide fields for this in your document-type (possibly use 
collections) and/or let the ACL react on them.


> D10. Does it have the ability to form groups like project groups and teams to collaborate on the team?
> 

Yes. All sorts of collaborative hooks are available. It really is a 
matter of getting into the thing and customizing it to your needs.

HTH,
-marc=