Looking to draw a simplified logical ER diagram and relation schema $($with attributes, PKs and FKs$)$ in relational database chen format based a few attributes provided and include appropriate ones need to be included in relation schema. Any complex relationships shall be converted into composite entities.

Case: Data will be collected for a cooking meet up that has multiple cook shows grouped into different tracks for the spectators. Each type of cuisine has its own track with title and a description with each track having a minimum of $1$ and maximum of $3$ shows.

SHow Spectators can register for unlimited individual shows under different tracks. Each sign up will need details like ID$,$ show number$/$ code, possible discounts. Each spectator details are stored in the datasheet even before sign up has started.

Any track will be organized by atleast one Masterchef upto $2$ per track. Masterchefs can choose the shows and competing chefs in their track. Each masterchef details are assigned to the track including their resume and they are eligible to be a spectator of any show. All the spectators details including name and email are taken optionally besides the employment company details. The meet up organizer would like to capture the employer details from participants.

Each show should have atleast one dish cooked by only one $$competing chef$$ and the dish details such as name, cooking time, etc. are noted in the meeting notes. Any competing chef can cook in multiple shows based on their choice. Any competing chef of the show can also be a spectator of other show without paying registration fee. Any other information of the competing chefs is collected as 'extras'. The studio where the meet up is happening has multiple kitchens with tags describing the name, kitchen ID and more details that can hold only one show in one kitchen at a time. Studio charges only for those rooms that are operated during the meet up$.$