[daisy] Daisy 101

[Steven Noels]

On 31 Oct 2006, at 18:04, Peter wrote:

> Thanks for your help Steven.
>
> Let me try to provide more details/answers
>
> - The system would have two types of users - sales rep's and customers
> - The main document type is a sort of portal page that is  
> personalized for
> the customer. It should be populated with two classes of content  
> (actually
> links to mainly office documents). The classes are (1) common for all
> customers and (2) specific for that customer.

Have a look at the ContextDoc search function for this.

> - The act of adding content should be simple (it is the sales rep
> task...need I say more :)). So when adding content, the action  
> should be -
> upload the document, name it and then tag it as common or customer  
> specific
> (and customer name). Perhaps an extra class is needed to say what  
> kind of
> content it is -e.g. information, meeting summary,..... The customer  
> specific
> content should indeed be protected with some kind of acl security  
> mechanism
> (but that should not be the concern of the sales rep).

Use the customer name as a field - you can then also use that in the  
ACL list.

> - Adding a customer can be a more complicated process.

Yes, you would need to set up a role/user for each customer, and add  
that customer to the selection list mentioned above as well.


> The thing I am concerned about is the learning time from my side (not
> knowing daisy nor cocoon) and the amount of custom development that  
> will be
> needed. I am a bit worried that, given the limited workflow and  
> overall cms
> requirements, at the end of road it might be faster to not use any  
> cms at
> all.

I doubt you'll get the editing side up any fast than when using any  
sort of CMS. ;-)

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought                              Open Source Java & XML
stevenn at outerthought.org                stevenn at apache.org