Calendar:Import Export: Difference between revisions
(→Comma Separated Value: Field Mapping) |
mNo edit summary |
||
Line 19: | Line 19: | ||
"Berlin Wall came down","1989-11-09" | "Berlin Wall came down","1989-11-09" | ||
=== Field Mapping === | ==== CSV Field Mapping ==== | ||
{| | {| | ||
| # || '''Events<br />header''' || '''Tasks<br />header''' || '''Calendar<br />property''' ||| '''Outlook<br />field values''' | | # || '''Events<br />header''' || '''Tasks<br />header''' || '''Calendar<br />property''' ||| '''Outlook<br />field values''' | ||
Line 35: | Line 35: | ||
| 6 || All day event || - || VALUE=DATE attribute || True, False | | 6 || All day event || - || VALUE=DATE attribute || True, False | ||
|- | |- | ||
| 7 || Reminder on/off || Reminder On/Off || VALARM component || True, False | | 7 || Reminder on/off || Reminder '''On'''/'''Off''' || VALARM component || True, False | ||
|- | |- | ||
| 8 || Reminder Date || eq. || TRIGGER || | | 8 || Reminder Date || eq. || TRIGGER || |
Revision as of 11:09, 2 March 2008
Calendar can import data in iCalendar (iCal) and Comma Separated Value (CSV) formats. Export is possible in these formats and is additionally in Hypertext Markup Language (HTML).
iCalendar
Recommended for data exchange. The format is standardized in RFC 2445 and widely used.
Comma Separated Value
CSV import and export are optimized for collaboration with Outlook which can't handle the iCalendar format in the necessary extent. CSV offers an easy way to exchange data with spreadsheets or word processors too.
Currently Calendar imports only "well formed" CSV files. The first line should contain the header names. Each header name and each data field has to be enclosed in double quotes. Data fields need to be separated with commas.
Effective as of version 0.8: Mandatory are the two fields "Subject" and "Start Date" in their localized naming only. Recommended date format is YYYY-MM-DD
with a four digit year at the beginning. Time format should be HH:MM:SS
with 24-hour values. Calendar will also understand dates and times in the locale scheme of the operating system but data format must not change within a file. The universal indicators AM
, a.m.
, PM
and p.m.
are always recognized.
The header names are localized and follow Outlook. Column order is not important. If the two mandatory headers could not be recognized all files with 22 headers are assumed to have the column order of an English CSV file from Outlook .
Sample CSV file
"Subject","Start Date" "Berlin Wall came down","1989-11-09"
CSV Field Mapping
# | Events header |
Tasks header |
Calendar property |
Outlook field values |
1 | Subject | eq. | SUMMARY | |
2 | Start Date | eq. | DTSTART | |
3 | Start Time | - | DTSTART | |
4 | End Date | - | DTEND | |
5 | End Time | - | DTEND | |
6 | All day event | - | VALUE=DATE attribute | True, False |
7 | Reminder on/off | Reminder On/Off | VALARM component | True, False |
8 | Reminder Date | eq. | TRIGGER | |
9 | Reminder Time | eq. | TRIGGER | |
10 | Meeting Organizer | - | (ATTENDEE) | |
11 | Required Attendees | - | (ATTENDEE) | |
12 | Optional Attendees | - | (ATTENDEE) | |
13 | Meeting Resources | - | - | |
14 | Billing Information | eq. | none | |
15 | Categories | eq. | CATEGORIES | |
16 | Description | - | DESCRIPTION | |
17 | Location | - | LOCATION | |
18 | Mileage | eq. | none | |
19 | Priority | eq. | (PRIORITY) | High, Normal, Low |
20 | Private | eq. | PRIVACY | True, False |
21 | Sensitivity | eq. | (CLASS) | Normal, .... |
22 | Show time as | - | (TRANSP) | 2, ... |
23 | Status | (STATUS) | ||
24 | Due Date | (DUE) | ||
25 | Date Completed | (COMPLETED (in UTC!)) | ||
26 | % Complete | (PERCENT-COMPLETE) | Fractions of one | |
27 | Total Work | - | ||
28 | Actual Work | - | ||
29 | Companies | - | ||
30 | Contacts | - | ||
31 | Notes | (DESCRIPTION) | ||
32 | Role | - | ||
33 | Schedule+ Priority | - |
Currently only events are imported and fields in parenthesis are skipped.
Hypertext Markup Language
HTML export gives an event list with the todo items on top of that list.