[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24946#action_24946
 ] 

Boris Kraft commented on MGNLDATA-88:
-------------------------------------

I think that we already have a flat example with the Address Book. So this 
example here could focus on the hierarchical part. I understand much of what 
you say, however the sample shouldn't try to solve these organizational issues; 
it should be something that is easy to grasp, fulfills expectations and somehow 
seems to convey the benefit of hierarchical data management. As you rightly 
point out, the issue of putting employees in a hierarchy is in practice more 
complicated; and tags might be better for some scenarios. Also, adding a 
relation (from employee to department) makes sense in some use-cases, while for 
others, having the hierarchy explicit might be more natural.

Our goal should be to come up with an example where managing data in the 
hierarchy provides immediate benefit compared to management in a relational 
database.

One example is that in a relational DB, you need to set the relationship 
explicitly. In the hierarchy, if you add an employee below the "sales" dept. it 
is obvious the employee belongs to the sales department, and no such 
relationship needs to be maintained separately.

BTW - if anybody has a great example for this, let us know.

> Samples for hierarchical data types have incorrect hierarchy
> ------------------------------------------------------------
>
>                 Key: MGNLDATA-88
>                 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-88
>             Project: Magnolia Data Module
>          Issue Type: Bug
>         Environment: Magnolia 4.2 RC 2
>            Reporter: Boris Kraft
>            Assignee: Philipp Bärfuss
>
> The samples for the hierarchy ("Big-Flower-Inc") seem to have the wrong 
> hierarchy.
> The defined hierarchy is as follows:
> Company
> * Employees
> ** Developer
> ** Director
> ** Manager
> * Department
> As you can see, this doesn't allow to create employees within a department.
> It would make more sense to have the following hierarchy:
> Company
> * Department
> ** Employees
> *** Developer
> *** Director
> *** Manager
> The sample content should also reflect this different structure.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to