Database Options

[costas]

Hi Guys,

I have a question.

Need opinion of best way to structure data. I have some idea but need direction.

I want to list people based on skill. E.g. music add main category and then subsets, e.g. piano, etc.

Etc. main category and then subsets.

These need to be searchable per person.

Also need to be displayed under person as individual values for that person.

A person may have multiple skills.

What’s the best way to structure the data to collect it?

I tried option sets but not sure how to creat parent and child relationship.

Should I just make the full list database values under person and display?

When I display I’m happy to display all the child values.

But when collecting I would like to allow it to select music and then piano, etc.

Hope it makes sense.

Any ideas welcome.

Thanks

[Baloshi69]

in your situations i guess you also need user to be searchably by either of main or sub category.

and can you confirm, is the list of your category is defini5or indefinite which mean user can add category if the cant fine one.

you need 3 entities … User … Main category … sub category

inside user you can have two field.

• Main Category ( either as one item main category …OR… list of Main category if user can hv many)
  sub category (list of sub category, depending on main category )

*the reason we have both separate so it be easy to search user defending on category … the only lengthy part is when we are adding or removing any things … only there we need 2 or 3 more action that set.

Main category entity just have one field as display which is the name of category.

subcategories entity will hv two fields

• Display … the label of sub category
• parent … the main category this belong to.

[costas]

Hi Baloshi,
I trust you are well. Thanks for quick reply. Greatly appreciate it it.
This was very helpful. I was thinking on these lines also. I just needed to have a play to see it in action. So far the trials are working great. Again, much appreciated!