Easier program loading #37

New Issue

2023-05-21T10:54:20+03:00

krokodilerian commented

2023-05-21 10:54:20 +03:00

(Migrated from github.com)

Currently, the program for the event, with slots and everything is done manually, i.e. every year I do stuff like

INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 704, '2022-10-15 10:15:00+3'::timestamptz, '2022-10-15 11:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 668, '2022-10-15 11:15:00+3'::timestamptz, '2022-10-15 12:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 674, '2022-10-15 12:15:00+3'::timestamptz, '2022-10-15 13:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 726, '2022-10-15 13:15:00+3'::timestamptz, '2022-10-15 14:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 720, '2022-10-15 14:15:00+3'::timestamptz, '2022-10-15 15:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 658, '2022-10-15 15:15:00+3'::timestamptz, '2022-10-15 16:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 699, '2022-10-15 16:15:00+3'::timestamptz, '2022-10-15 17:00:00+3'::timestamptz);
INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 727, '2022-10-15 17:15:00+3'::timestamptz, '2022-10-15 18:00:00+3'::timestamptz);

based on a xls table that gets given to me by the program committee like this one Untitled spreadsheet.ods

This should match in the end what's visible at https://www.openfest.org/2022/bg/full-schedule-bg/ and is rendered by the stuff in https://github.com/OpenFest/initfest/tree/master/schedule

There should be an easier interface that the program committee can use directly instead of google sheets, that would also show conflicts, will make visible language, speaker (not to schedule a speaker in two rooms at the same time, for example), etc., etc..

As a bonus, it should be able to offer suggestions for slots based on the following:

the event is accepted
it's in language that's not for a talk in another room
it's in a track that's not currently in another room
preferrably it's in the track of the previous event in this foom
doesn't conflict with an event in another room based on the public voting from gauge

If more input is needed on usability, etc, I think the program committee can probably test a few things and give pointers.

Currently, the program for the event, with slots and everything is done manually, i.e. every year I do stuff like ``` INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 704, '2022-10-15 10:15:00+3'::timestamptz, '2022-10-15 11:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 668, '2022-10-15 11:15:00+3'::timestamptz, '2022-10-15 12:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 674, '2022-10-15 12:15:00+3'::timestamptz, '2022-10-15 13:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 726, '2022-10-15 13:15:00+3'::timestamptz, '2022-10-15 14:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 720, '2022-10-15 14:15:00+3'::timestamptz, '2022-10-15 15:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 658, '2022-10-15 15:15:00+3'::timestamptz, '2022-10-15 16:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 699, '2022-10-15 16:15:00+3'::timestamptz, '2022-10-15 17:00:00+3'::timestamptz); INSERT INTO slots(hall_id, event_id, starts_at, ends_at) VALUES(43, 727, '2022-10-15 17:15:00+3'::timestamptz, '2022-10-15 18:00:00+3'::timestamptz); ``` based on a xls table that gets given to me by the program committee like this one [Untitled spreadsheet.ods](https://github.com/OpenFest/clarion/files/11523883/Untitled.spreadsheet.ods) This should match in the end what's visible at https://www.openfest.org/2022/bg/full-schedule-bg/ and is rendered by the stuff in https://github.com/OpenFest/initfest/tree/master/schedule There should be an easier interface that the program committee can use directly instead of google sheets, that would also show conflicts, will make visible language, speaker (not to schedule a speaker in two rooms at the same time, for example), etc., etc.. As a bonus, it should be able to offer suggestions for slots based on the following: - the event is accepted - it's in language that's not for a talk in another room - it's in a track that's not currently in another room - preferrably it's in the track of the previous event in this foom - doesn't conflict with an event in another room based on the public voting from gauge If more input is needed on usability, etc, I think the program committee can probably test a few things and give pointers.

Sign in to join this conversation.