[daisy] Daisy 101

[Peter]

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. 
- 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). 
- Adding a customer can be a more complicated process.

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.

All thoughts warmly appreciated

Thanks,

Peter

> -----Original Message-----
> From: daisy-bounces at lists.cocoondev.org [mailto:daisy-
> bounces at lists.cocoondev.org] On Behalf Of Steven Noels
> Sent: Tuesday, October 31, 2006 2:40 PM
> To: Daisy: open source CMS - general mailinglist
> Subject: Re: [daisy] Daisy 101
> 
> On 30 Oct 2006, at 18:07, Peter wrote:
> > I understand this is an extremely incomplete description, but
> > nevertheless, before I attempt to achieve this with Daisy, would
> > anyone like to comment on the achievability of this project with
> > Daisy? Any ballpark as on how long it would require to setup/
> > configure/develop? Any other advice?
> What you describe sounds feasible - though some planning upfront
> would still be required.
> 
> * what will be the main document types? 'customer info sheet',
> 'customer', ?
> * parts and fields? what fields will be used in navigation and/or
> access control?
> * what actions for what documents should be reserved for which roles/
> users? if they are included in queries/navigations, they are
> automatically filtered against ACL
> * for 'personalized' homepages, you should perhaps take a look at
> custom publisher requests (currently under-documented somewhat)
> * categorization: hierarchical or tagging-style? keep in mind that
> hierarchical field values can only be managed by someone with admin-
> level access, however you can also use link hierarchies for that
> 
> if you do your thinking in public, I'm sure we'll be happy to help
> 
> </Steven>
> --
> Steven Noels                            http://outerthought.org/
> Outerthought                              Open Source Java & XML
> stevenn at outerthought.org                stevenn at apache.org
> 
> 
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/site/services/daisy/daisysupport.html
> mail to: daisy at lists.cocoondev.org
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy