The Interchange format file begins with a header describing the owner of the file (the person to whom the schedule belongs) and when it was exported or created. The header is followed by descriptors for projects, tasks, notes, standard appointments, and recurring appointments. Although meetings are supported in the interchange format, they are not documented here. Meetings can be imported as standard appointments by the scheduling or calendar software that is exchanging data with Schedule+. The order of descriptors is not significant, except that projects must precede tasks.
The following section describes the syntax for individual descriptors.
If you export a Schedule+ calendar to the interchange format, you will find that each descriptor begins with a line defining a field called aid. This is an appointment ID defined and maintained by Schedule+; it should not be included in the import file.
Table 9.1 Key to Interchange Format Syntax
Item | Description |
� | Tab |
italic | Required input |
nonitalic | Fixed-field definitions |
m | Month or minute |
d | Day |
h | Hour (24-hour format) |
y | Year |
SCHEDULE+ EXPORT BY mailbox name ON m/dd/yy AT hh:mm AM/PM
FixedAppt:
�szText
project description
�fTask � � � � �T
�aidProject � � � � � �project id # (integer, number in sequence)
End
FixedAppt:
�szText
project description
�aaplWorld � � � � �Read
�fTask � � � � �T
�aidProject � � � � ��project id # (integer, number in sequence)
End
Note The fTask line is present for all projects; other lines, like the aaplWorld line above, are present only for private projects.
FixedAppt:
�szText
task description
�fTask � � � � �T
�bpri � � � � � �priority # (1�35, where 1�9 = priority 1�9 and 10�35 = priority A�Z)
�aidParent � � � � � �project id # of associated project (integer)
End
FixedAppt:
�szText
task description
�aaplWorld � � � � �Read
�fTask � � � � �T
�bpri � � � � � �priority # (1�35, where 1�9 = priority 1�9 and 10�35 = priority A�Z)
�aidParent � � � � ��project id # of associated project (integer)
End
FixedAppt:
�dateStart � � � � ��due date in format m-d-yyyy hh:mm
�dateEnd � � � � ��due date in format m-d-yyyy hh:mm
�szText
task description
�fTask � � � � �T
�nAmtBeforeDeadline � � � � ��nteger # (with unit below, indicates start work before due date)
�tunitBeforeDeadline � � � � �unit: Day, Week, or Month (indicates start work before due date)
�bpri � � � � ��priority # (1�35, where 1�9 = priority 1�9 and 10�35 = priority A�Z)
�aidParent � � � � ��project id # of associated project
End
Note The dateStart and dateEnd lines ask for hh:mm. This must be supplied but won't be used for these date-oriented (rather than time-oriented) tasks. hh:mm should be 00:00.
FixedAppt:
�dateStart � � � � � �start date and time in format m-d-yyyy hh:mm (time is 24 hour)
�dateEnd � � � � � �end date and time in format m-d-yyyy hh:mm (time is 24 hour)
�szText
appointment description
�aaplWorld � � � � �Read
End
FixedAppt:
�dateStart � � � � � �start date and time in format m-d-yyyy hh:mm (time is 24 hour)
�dateEnd � � � � � �end date and time in format m-d-yyyy hh:mm (time is 24 hour)
�szText
appointment description
�dateNotify � � � � � �specification of alarm in format m-d-yyyy hh:mm (time is 24 hour)
�nAmt � � � � � �integer defining how long before an appointment the alarm should go off
�tunit � � � � �the unit (Minute, Hour, Day, Week, Month) defining the alarm
End
Note The dateNotify line asks for hh:mm. Place any time here; a value is required. The actual time used for the alarm is set in the nAmt and tunit lines.
If the alarm is in minutes, the tunit line is not required.
RecurAppt:
�ymdStart � � � � �start date of recurrence pattern in format m-d-yyyy
�ymdEnd � � � � �end date of recurrence pattern in format m-d-yyyy
�wgrfValidMonths � � � � �used to define recurrence pattern (see next section for detail)
�bgrfValidDows � � � � � �used to define recurrence pattern (see next section for detail)
�trecur � � � � � �used to define recurrence pattern (see next section for detail)
�timeStart � � � � �start time in format hh:mm
�timeEnd � � � � �end time in format hh:mm
�szText
Recurring appointment description
End
Note The ymdEnd line is required only if the recurring appointment has an end date. If it does not, omit the ymdEnd line. See the following section for more information about this type of entry.
MonthNotes:
�date of Note in format m-d-yyyy
note #1 text
�date of Note in format m-d-yyyy
note #2 text
End
Note All notes for the month are listed together in sequence.