Changes between Version 1 and Version 2 of RelationalDesignAIUsage
- Timestamp:
- 08/29/26 13:33:16 (8 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RelationalDesignAIUsage
v1 v2 13 13 '''Diagram:''' 14 14 15 The official relational diagram will be exported from DBeaver after the scripts are executed in the assigned PostgreSQL database. 15 The official relational diagram was exported from DBeaver after the scripts were executed in the assigned PostgreSQL database. 16 17 [[Image(relational_schema.png, width=100%)]] 16 18 17 19 '''Model description:''' … … 80 82 81 83 '''Prompt 10:''' 82 Create realistic sample data for `data_load.sql` using my existing schema and the following constraints: realistic UKIM fields of study for FINKI, FEEIT, MFS, TMF, and PMF; fulfilled Board and Non-Board functions; accepted core-team applications for the organised event editions; weekly meetings in Baraka 2.2; workshops in Baraka 2.1, 2.2, 3.1, 3.2, Netaville, or Base42; full-member, Board, and core-team meetings in BEST Office; BCS meetings at the BEST Benches; realistic event descriptions and locations for Job Fair, Hackathon, BEST Course in Summer, Motivational Weekend, BOMBA, beBESTIE, and BEST Skopje Birthday; appropriate core-team functions for each event type; realistic responsible members, participation, absences, volunteers, companies, and cooperation records.84 Create realistic sample data for `data_load.sql` using my existing schema and the following constraints: realistic UKIM fields of study for FINKI, FEEIT, MFS, TMF, and PMF; fulfilled Board and Non-Board functions; accepted applications for event function slots; weekly meetings in Baraka 2.2; workshops in Baraka 2.1, 2.2, 3.1, 3.2, Netaville, or Base42; full-member, Board, and core-team meetings in BEST Office; BCS meetings at the BEST Benches; realistic event descriptions and locations for Job Fair, Hackathon, BEST Course in Summer, Motivational Weekend, BOMBA, beBESTie, and BEST Skopje Birthday; several core-team functions for larger events, only Main Organiser functions for smaller events, and no Main Organiser for BOMBA because it is coordinated by HR; realistic responsible members, participation, absences, volunteers, companies, and cooperation records. 83 85 84 86 '''AI response 10:''' 85 The AI drafted connected sample data based on those constraints. The sample data included students, members, membership-stage history, organisational functions, event types, event editions, event locations, event sessions, core-team functions, applications, activity sessions, event-related activity-session links, participation/RSVP records, announced absences, responsible members, volunteers, companies, and cooperation records. The data was then reviewed and corrected against the ER model and project requirements.87 The AI drafted connected sample data based on those constraints. The sample data included students, members, membership-stage history, organisational functions, event types, event editions, event locations, event sessions, core-team/event-function slots, applications, activity sessions, event-related activity-session links, participation/RSVP records, announced absences, responsible members, volunteers, companies, and cooperation records. The data was then reviewed and corrected against the ER model and project requirements. 86 88 87 89 '''Prompt 11:''' … … 103 105 The AI helped update the final documentation to reference ERModel_v09 and adjusted the relational representation of `volunteers` and `cooperation` so that `volunteer_role` and `cooperation_type` are stored as relationship attributes instead of being part of the primary key. 104 106 107 '''Prompt 14:''' 108 I think `application_id` for `applications` should be automatically generated. How to do this in PostgreSQL? 109 110 '''AI response 14:''' 111 The AI shared the solution: "application_id integer GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY". 112 113 '''Prompt 15:''' 114 Job Fair is public and does not have participation applications. beBESTie also has open registration and does not need a motivational letter. Hackathon and BEST Course in Summer have applications through external Google Forms with more fields than the ER model. How should this be represented? 115 116 '''AI response 15:''' 117 The AI suggested keeping public/open attendance outside the `applications` relation, so Job Fair and beBESTie participation were not modeled as applications. For Hackathon and BEST Course in Summer, the AI suggested keeping only the most important summarized application information in `applications`, such as the applicant, event edition, status, application type, and main motivation/answer, while leaving the full Google Form outside the current phase scope. 118 119 '''Prompt 16:''' 120 I noticed that there are no Main Organiser applications for beBESTie, Birthday, and Motivational Weekend, even though those events should still have a Main Organiser or event function slot. 121 122 '''AI response 16:''' 123 The AI explained that the current `core_team_functions` relation was being used more generally as an event-function relation in the physical schema. It suggested adding Main Organiser function slots and accepted applications for Motivational Weekend, Birthday, and beBESTie, while still leaving BOMBA without a Main Organiser because it is coordinated by HR. 124 125 '''Prompt 17:''' 126 For an event edition to be held, it must have had a Main Organiser or a core team, except for BOMBA. Is that the case currently? 127 128 '''AI response 17:''' 129 The AI checked the sample data and confirmed that every event edition except BOMBA has either a Main Organiser function or a full core team with accepted applications. BOMBA was left as the exception because it is coordinated through the HR function. 130 105 131 == Changes made based on AI assistance == 106 132 … … 117 143 * The `RelationalDesign` wiki page was prepared according to the required phase template. 118 144 * This `RelationalDesignAIUsage` page was prepared according to the required AI-use template. 145 * `application_id` was implemented as an automatically generated identity value in the physical schema. 146 * Public attendance for Job Fair and open registration-style attendance for beBESTie were kept outside the `applications` relation. 147 * Participation applications were kept only for event editions where an actual application process exists in the sample data, such as Hackathon and BEST Course in Summer. 148 * Event function slots were adjusted so larger events have several core-team functions, smaller events have only a Main Organiser function, and BOMBA has no Main Organiser because it is coordinated by HR.
