Please enable JavaScript.
Coggle requires JavaScript to display documents.
Possible FIA2 Data Design - Coggle Diagram
Possible FIA2 Data Design
Users (Table)
Email (varchar, unique, required)
First Name (varchar, required)
Username (varchar, unique, required)
Surname (varchar, required)
User ID (varchar, pk)
Note: The reason that house, tutor group, year level, etc. (i.e. student attributes) are not included within the users table is because that would be a double storing of information, which is inefficient and storage consuming
Role: The type of user - may be:
Administrator
Organiser
Student
Events (Table)
Event name: (varchar, required)
This is not necessarily a unique attribute/value, as there are multiple instances of Terrace v Nudgee, for example
Event ID: (varchar, pk)
Location: (varchar, required) - an event must have a location in order to be attended; this is so that students and organisers know where to go
Time-date (date, required) - note that this is a date, not varchar
Point worth (int, required) - an event has a point worth; in this way, administrators (event-adders) can add events with varying levels of importance; this adds another level of manipulation for admins, as they may increase the point worth of an event in order to encourage attendance
Attendance (Table)
Event ID (fk)
Note that foreign keys must be used here in order to create the table
User ID (fk)
The attendance table is the table that tracks all of the relevant attendances (student instances) - by specifying events, users, and the time/date at which that user attended that particular event, the attendance
Userbase (Table, as supplied by Mr Whitehouse)
Email (varchar, required, unique)
House (varchar, required)
Surname (varchar, required)
First Name (varchar, required)
Tutorgroup (varchar, required)
Student ID (varchar, pk)