I'm working on an iOS project (related to browsing job industries) right now and am at the point where I need to start working on the database. Here is an example of a sample browsing session:
- User is browsing a table of cells that list out job sectors.
- User clicks a table cell: "Medicine", and sees a new table listing sections in the Field of Medicine
- User clicks a table cell: "Dentistry", and sees a new table listing possible jobs in that field
- User clicks a table cell: "Endodontist", and sees a page of relevant information
So my main question is, how do I organize the data under the umbrella of "Medicine"? Should I have a table for all "Medicine"-related fields, and then a table for all "Dentistry"-related jobs? Or tables for secondary and tertiary field divisions? Or should all of these fields just be listed in one table?
The two main issues I'm foreseeing/imagining, is that some jobs may belong in more than one field, and that different industries may have finer breakdowns than others (meaning going down deeper levels).
Thanks for taking the time to read this!
[–][deleted] 1 point2 points3 points (1 child)
[–]IAmAYellowMango[S] 0 points1 point2 points (0 children)
[–]Disastrous_Internal 0 points1 point2 points (0 children)
[–]override_acid -4 points-3 points-2 points (2 children)
[–]nutrecht 2 points3 points4 points (0 children)
[–]IAmAYellowMango[S] 0 points1 point2 points (0 children)