Create models

[david2242]

Student:

• name: string -> Kálmán Ferencz
• class: -> 2022. b.

Competition:

• name: string
• location: string
• subject: string[]
• teacher: string[]
• year: string -> 2004-2005
• date: Date (might be unneccessary)
• level: 'local' | 'state' | 'regional' | 'national' | 'international'
• round: 'school' | 'regional' | 'state' | 'national'
• form: 'written' | 'oral' | 'sport' | 'submission' []
• "result":{
  • position:null,
  • special_prize: boolean compliment: boolean
  • next_round: boolean }
• other: string

[norbfr]

I have some questions:

1. What data would the "location" field work with? I see that the type would be string, but why is there a () sign behind it?
2. Could the "other" field will work as a comment/note functionality? If so, I would give it a suitable name for it.
3. If I understand correctly, the "subject" and "teacher" fields will function as an array based on the [ ] notation, right?
4. In the case of the "form" field, more than one of the possible values ​​can be specified, so would this field exist as an array? Is that why the array [ ] notation is behind it?

[david2242]

1. Yes, the "()" was not intended. It should store some kind of city i think, like "Budapest", or "Debrecen" etc.
2. Yes the other field is for any other comments related to the competition, but here is no field for it specified. What suggestion do you have with this naming?
3. The subject can be an array because the competition can have multiple subject such as ["mathematics", "physics"]. It would be nice to use enums but at the same time it should handle unspecified subjects, like new ones emerging in schools, like "visual culture" :D.
4. Yeah the form should be an array as well because the competition can have multiple forms like ["oral", "written"].

[norbfr]

Thanks for the answer.

I suggest a name for the "other" field like a "note" or "comment". Which one do you think is appropriate? However if you think we should stick with the original name, that's OK for me.

[david2242]

Note is perfect, I'll change it on backend as well. Thanks!