Calendar:Import Export: Difference between revisions

(→‎iCalendar: RFC 2445)
(→‎Comma Separated Value: Field Mapping)
Line 7: Line 7:


=== Comma Separated Value ===
=== Comma Separated Value ===
CSV import and export is optimized for collaborating with Outlook which can't handle the iCal format in the necessary extent. CSV offers an easy way to exchange data with spreadsheets or word processors.
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 needs "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.  
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 <code>YYYY-MM-DD</code> with a '''four''' digit year at the beginning. Time format should be <code>HH:MM:SS</code> 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 <code>AM</code>, <code>a.m.</code>, <code>PM</code> and <code>p.m.</code> are always recognized.  
Effective as of version 0.8: Mandatory are the two fields "Subject" and "Start Date" in their localized naming only. Recommended date format is <code>YYYY-MM-DD</code> with a '''four''' digit year at the beginning. Time format should be <code>HH:MM:SS</code> 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 <code>AM</code>, <code>a.m.</code>, <code>PM</code> and <code>p.m.</code> are always recognized.  
Line 19: Line 19:
  "Berlin Wall came down","1989-11-09"
  "Berlin Wall came down","1989-11-09"


=== Field Mapping ===
{|
| # || '''Events<br />header''' || '''Tasks<br />header''' || '''Calendar<br />property''' ||| '''Outlook<br />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 ===
=== Hypertext Markup Language ===
Confirmed users
59

edits