Project

General

Profile

Feature #7719

Updated by Yannick Warnier over 4 years ago

As developed in a separate branch for icpna, the sessions should have six dates in total:

* student access start date (this is the current session start date)
* student access end date (this is the current session end date)
* coach access start date (this is the current session start_date modified with the "days before" setting)
* coach access end date (this is the current session end_date modified with the "days after" setting)
* session visual start date (this is the start date as shown visually in sessions lists - by default the same as the student access start_date)
* session visual end date (this is the end date as shown visually in sessions lists - by default the same as the student access end_date)

Ideally, these start/end date should all be datetimes (for more precise control) although I don't think we need more than a precision of an hour)

The current global setting for default coach_access_start_date and end_date should be taken into account when auto-generating the coach start and end date on the basis of the student start and end date).

These 6 options should all be an *alternative* to the *session_duration* attribute, which doesn't allow for any specific dates. In this case, the students get a calculated access date, and the tutor has always access to the session.

Web services should also be modified to accept multiple dates (optionally), in a way that lets previous webservice calls still work but that enables the optional setting of more dates.

Back