Sample reportory - Hireracy/Taxonomy table

[Former Member]

Hi,

I am trying to build my frist repository and my model is as below.

Employeeid(Integer)

EmployeeName(Text)

EmployeeDepartment(Lookup[Hierarcy]) ................. Departments is the LOOKUP table.

Look up table Departments contains 3 departments SD,FI & PP.

SD conatins 2 SubDepartments - 1) telesales 2) direct sales

FI contains 2 SubDepartments - 1) CA 2) NonCA

PP contains 2 subDepartments - 1) Managerial 2) NonManagerial.

I had arranged Department is the following Hierarcy 1) SD 2) FI 3) PP

The doubt that is araising in my mind is how should I assingnment subdepartment does they need to be assigned as attributes(taxonomy) or as siblings to Departments.

How can we judge when to assign taxonomy or sibling ?

Thanks

Edited by: SDN POWERED on Dec 31, 2008 5:58 AM

[Former Member · Accepted solution]

Hi,

How can we judge when to assign taxonomy or sibling/child ?

U mean, Attribute or sibling.......... Right?

If u r creating Hierarchy of Products Then u will maintain, what all types of products u have.......

e.g. Electronic products, Kitchen Products etc........... (these r siblings... at same level)

Now inside Electronic products u will have again sub categories... (child) & then ur product e.q, T.V

Now T.V can have attributes Color, Size, No of channels.

In Color attribute u can have values like Black, Silver.

For No of channels u can hv values 50,70, 100

Now Kitchen Products will not have these attributes but they will have something else.

So basically attribute is something which tells something extra about ur node.

I hope u undestand the difference between child/sibling & attribute

Thanks,

Maheshwari

[Former Member]

Hi,

It completely depends on the data.

Example

Printer

- Lazer

- - Epson

- Dot Matrix

Now various attribtues in above hierarchy can be Price, Speed etc. Your records should point to particular printer, hence you cannot put Speed as a Child for Epson.

Regards,

Jitesh Talreja