Time Default Values Guideline

1 Guideline

1.1 Problem

Several features in ILIAS have input fields to define date and time, e.g. sessions, exercises, booking tool, calendar, a.m.m. The current implementation of this date time input form comes always with default values. Unfortunately, these input fields do not use always reasonable values, e.g. the enddate of a future booking with recurrencies uses the date of creating the booking as default, see discussion posting at Jan 16, 2015.
 

1.2 Guideline

Default values of date time input fields should always use reasonable values for the related activity. Especially end dates should never use the current date and time.
 

2 Status

• Effective from release: { not approved yet | x.y }
• Approved by Jour Fixe at: { link to Jour Fixe agenda }
  
• Implementation status: { implemented completely | partly implemented | needs implementation }
• Funding for streamlining existing features: { name of organisation }
• Implementation of guideline: { all developers | name of responsible developer }

3 Components that are not compliant with the Guideline

• …

4 Discussion

Matthias Kunkel, 17 Jan 2015: In relation to this guideline I see also the problem of context-sensitivity of date input fields: If the start date is changed to a date X, the end date should not last at a value X-n but always update itself to a value X+m where m is a reasonable enddate for such an activity, e.g. 2 hours for a session or "today plus 14 days" for an event with a recurrency of 2 weeks.