Allow contests and analyses to continue indefinitely

[stefano-maggiolo]

The outline of the proposal:

• we retain the current fields: contest_{start,stop}, analysis_{enabled,start,stop}
• all timestamps are nullable meaning "extending indefinitely in that direction"
• contest_stop = null => analysis_enabled = False
• analysis_enabled = False => analysis_start = null and analysis_stop = null
• analysis_enabled = True => analysis_start != null
• whenever non-null, contest_start <= contest_stop <= analysis_start <= analysis_stop

(probably the conditions can be simplified a bit, this is just for illustrative purposes)

[lw]

The proposed rules imply that analysis_enabled == true <=> analysis_start is not none, meaning that analysis_enabled is effectively redundant. This doesn't mean we couldn't "emulate" it on the interface.

On Tue, Apr 11, 2017, 00:49 Stefano Maggiolo [email protected] wrote:

The outline of the proposal:

• we retain the current fields: contest_{start,stop}, analysis_{enabled,start,stop}
• all timestamps are nullable meaning "extending indefinitely in that direction"
• contest_stop = null => analysis_enabled = False
• analysis_enabled = False => analysis_start = null and analysis_stop = null
• analysis_enabled = True => analysis_start != null
• whenever non-null, contest_start <= contest_stop <= analysis_start <= analysis_stop

(probably the conditions can be simplified a bit, this is just for illustrative purposes)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cms-dev/cms/issues/748, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHX6gzB_kXEUCu5huKz-7qrV1WA3aGPks5ruwZ0gaJpZM4M5ngG .