This section covers all data-entry and command useage details that may not have been fully elucidated in the preceding scenarios.

2.9.1. Date Formats

Ed. Note: I think it would be quite good to summarize these requirements in tabular form, with one table for each class of dialog, with one table row for each data-entry field in the dialog.

The following data entry formats apply to any scheduling dialog where the indicated field appears:

1. The Title and Location fields are free-form, one-line strings. If the text is longer than will fit in the provided data-entry area, then it will automatically scroll as the user types and can be repositioned using the normal text movement arrow keys or such other forms of horizontal scrolling as may be available.

2. The (Start) Date and End Date are type-in fields, with checking for legal date syntax. The following are legal forms of date entry: ...

If the user specifies a recurring event without checking any box in the additional recurring information, the event will be set by default to recur weekly, on the day of the week that is specified for the start date of the event. [Sketch: some other defaults are made clear by default display of selection box.]

2.9.4. Required Fields

When scheduling or changing an item, the following fields are required to be non-empty and properly formated: Title, (Start) Date, Start Time, and Duration. If one or more of these fields is missing when the user presses the 'OK' or 'Change' button, the system responds with the error dialog shown in Figure 42.

The system provides a three-way option to control the scheduling of items with overlapping times. The option settings are the following:

1. disallow overlapping times entirely

2. allow overlapping times, with warning

3. allow overlapping times, no warning