summaryrefslogtreecommitdiffabout
authorzautrix <zautrix>2004-08-02 17:53:44 (UTC)
committer zautrix <zautrix>2004-08-02 17:53:44 (UTC)
commit82cd729d654323a599f4fecfc6b358ccfb857ec8 (patch) (side-by-side diff)
treed515325f3485c8da562896e17be4549530174018
parentd8b187d8760766416a9527f3e12789198b30840a (diff)
downloadkdepimpi-82cd729d654323a599f4fecfc6b358ccfb857ec8.zip
kdepimpi-82cd729d654323a599f4fecfc6b358ccfb857ec8.tar.gz
kdepimpi-82cd729d654323a599f4fecfc6b358ccfb857ec8.tar.bz2
Compledted migration-howto
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/korganizer/Migration-HowTo.txt52
1 files changed, 44 insertions, 8 deletions
diff --git a/bin/kdepim/korganizer/Migration-HowTo.txt b/bin/kdepim/korganizer/Migration-HowTo.txt
index a5fa02c..f213b82 100644
--- a/bin/kdepim/korganizer/Migration-HowTo.txt
+++ b/bin/kdepim/korganizer/Migration-HowTo.txt
@@ -161,190 +161,226 @@ Choose menu:
File - Import - Import from OL...
You will get a dialog which shows all "Personal Folders" of Outlook.
Choose the Contact Folder(s) you want to import and select them with a hook.
(All other folder but the contact containing folders are shown, but disabled).
(If the data you want to import is not stored in one of the shown folders,
please read step 2.) and click on "close" ).
Click the "import" button.
Now Outlook asks you to allow access to the contact data.
Select "Allow access" amd click "Yes" in this dialog.
Now the importing is performed and KA/Pi will show a progress bar.
After importing, KA/Pi shows a dialog, how much contacts are imported.
If you press a second time "import" , already imported contacts are not imported again.
After importing you can choose another "Contact Folder" to import or close the import dialog.
Please close the import dialog.
Now you see the imported contacts in KA/Pi on the left in the list view.
Please verify, that the import was correct.
About problems of mapping particular Outlook-data-fields to KAdressbook-data-fields see Appendix A).
Choose menu:
File - Save
and close KA/Pi.
Now you should have the contact data in the file std.vcf in your home directory in the path
(YOURHOMEDIR)\kdepim\apps\kabc\std.vcf
Copy that file to a moveable disk or memory stick or just copy it via network to the destination.
Import that file into KAddressbook/Kontact via Import - Import vcard.
Details about importing you can read at: 7) How to import your contact data into Kontact
Now you have your Outlook200X contact data on the KDE desktop available and you are done with the migration of contacts.
*************************************************************
6) How to get the calendar data out of Outlook200X
*************************************************************
Note: When accessing Outlook to read the data, it should not be possible, that there is any data lost in Outlook, because the progam accesses Outlook only Read-Only.
You have the file
kopi.exe
and the other needed files accessable on your workstation.
Getting the calendar data
NOTE: Before extracting the calendar data, it is recommended to extract the contact data first.
If you extract the contact data first, the identity (UID) of attendees of a meeting can be mapped correctly in the newly created appointments, such that you can access the attendee contact data later directly from KOrganizer.
Please start kopi.exe.
You will see a dialog, that you started KO/Pi for the first time and that the timezone configuration will be shown now. Confirm with "Ok".
Now you will see the configuration dialog of KO/Pi.
Please choose your timezone and adjust the daylight saving settings.
The dialog shows defaults for CET (Central European Time), such that users located in central Europe simply can press "OK" in that dialog.
(Note: Don't forget to set the timezone in KDE KOrganizer before importing data there. The timezone in KDE KOrganizer is set per default to UTC (GMT), that is -1h of CET).
Now you will see the KO/Pi main window.
Choose menu:
File - Import from OL
You will get a dialog which shows all "Personal Folders" of Outlook.
Choose the Calendar Folder(s) you want to import and select them with a hook.
(All other folder but the calendar data containing folders are shown, but disabled).
(If the data you want to import is not stored in one of the shown folders,
please read step 2.) and click on "close" ).
Click the "import" button.
Now Outllok asks you to allow access to the contact data.
Select "Allow access" amd click "Yes" in this dialog.
Now the importing is performed and KO/Pi will show a progress bar.
After importing, KO/Pi shows a dialog, how much calendar items are imported.
If you press a second time "import" , already imported calendar items are not imported again.
After importing you can choose another "Calendar Folder" to import or close the import dialog.
Please close the import dialog.
Now you see the imported calendar items in KO/Pi.
Please verify, that the import was correct.
About problems of mapping particular Outlook-data-fields to KOrganizer-data-fields see Appendix B).
Close KO/Pi - data will be saved automatically.
Now you should have the calendar data in the file mycalendar.ics in your home directory in the path
(YOURHOMEDIR)\kdepim\apps\korganizer\mycalendar.ics
Copy that file to a moveable disk or memory stick or just copy it via network to the destination.
Import that file into KOrganizer/Kontact.
Details about importing your calendar data you can read at: 8) How to import your calendar data into Kontact.
(Warning again: Don't forget to set the timezone in KDE KOrganizer before importing data there. The timezone in KDE KOrganizer is set per default to UTC (GMT), that is -1h of CET).
Now you have your Outlook200X calendar data on the KDE desktop available and you are done with the migration.
Hint:
If you want to use KO/Pi and KA/Pi on your windows desktop, you should read all the help information available in the KO/Pi Help menu. One Highlight of KO/Pi is the easy syncing with another *.ics file.
(Information about syncing available in the KO/Pi help menu).
Another hint:
KO/Pi + KA/Pi ( = KDE-Pim/Pi ) are available for the Sharp Zaurus PDA.
Syncing data works for KO/Pi ( version 1.9.3) but not yet for KA/Pi.
*************************************************************
7) How to import your contact data into Kontact
*************************************************************
-
-
-MISSING
-
-
+We want to import and upload our contacts to a Kolab server.
+You should have access to a properly configured Kolab client.
+This Kolab client is Kontact in KDE.
+Make sure, you have the needed IMAP resources configured in KAddressbook.
+To configure IMAP resources, you should do:
+
+ Open KDE control center, choose there
+ KDE Components - KDE Resource Configuration
+ Choose there:
+ Resources: contact
+ and then:
+ Add...
+ IMAP
+
+Now start Kontact and select the Contacts icon on the left side.
+Choose menu:
+File... - Import - Import VCard...
+Select the imap resource as destination of the import
+and choose the file to import.
+Now the contacts should be imported and you are done.
+
+Don't forget to sync the IMAP account to upload to contacts to the server.
*************************************************************
8) How to import your calendar data into Kontact
*************************************************************
-
-MISSING
-
+We want to import and upload our calendar data to a Kolab server.
+You should have access to a properly configured Kolab client.
+This Kolab client is Kontact in KDE.
+Make sure, you have the needed IMAP resources configured in KOrganizer.
+To configure IMAP resources, you should do:
+
+ Open KDE control center, choose there
+ KDE Components - KDE Resource Configuration
+ Choose there:
+ Resources: calendar
+ and then:
+ Add...
+ Calendar on IMAP-server via KMail
+
+Now start Kontact and select the Calendar icon on the left side.
+Choose menu:
+File... - Import - Merge Calendar...
+Select the imap resource as destination of the import
+and choose the file to import.
+Now the calendar data should be imported and you are done.
+
+Don't forget to sync the IMAP account to upload the calendar data to the server.
*************************************************************
APPENDIX A) Problems and solutions when reading contact data
*************************************************************
All data, which can be displayed and accessed in KAddressbook is imported from Outlook.
In Outlook you can assign an attribute "This is the mailing address" to one of the addresses.
This address shows up in KAddressbook twice.
The first time with the original attribute from Outlook ( e.g. "work" for "business" in OL ).
The second time with the attribute "postal".
All telephone numbers of OL are imported.
OL offers special case telephone numbers, like "Assistant", which have no counterpart in KAdressbook.
In that case, the imported number has special combined attributes in KAddressbook.
Here is the mapping of types in OL to attributes in KA:
OL type Attributes in KA
Assistant Work + Voice
Business Work
Business2 Work
BusinessFax Work + Fax
Car Car
Home Home
Home2 Home
HomeFax Home + Fax
ISDN Isdn
Mobile Cell (displayed as Mobile Phone)
OtherFax Fax
OtherTelephone Voice
Pager Pager
PrimaryTelephone Pref ( displayed as typeless, with attribute preferred )
TTYTDD Modem
Telex Fax + Bbs (Bbs displayed as MailBox - not very senseful, sorry ...)
CompanyMain Work + Pref
Radio Video
Callback Voice + Pref
Some mapping may not be very senseful, but it helps to identify the original OL types.
*************************************************************
APPENDIX B) Problems and solutions when reading calendar data
*************************************************************
Almost all data, which can be displayed and accessed in KOrganizer is imported from Outlook.
Attachments of appointments are not imported.
KOrganizer may crash, when reading some kinds of attachments.
These may be changed in future versions.
Attendee lists of meetings and their state are imported in KOrganizer.
A problem is importing some kinds of recurring events:
First problem:
OL offers a recurrence like
- Yearly recurrence, every second Tuesday of July.
KOrganizer ( in versions < 3.3.0 ) does not offer that kind of recurrence.
Such that
"Yearly recurrence, every second Tuesday of July."
is converted to
"Monthly recurrence, every 12. month, second Tuesday in month, StartMonth = July."
which can be edited in KO.
Second problem:
OL offers an exception in a recurrence with other data/time.
KO offers only an exception in a recurrence , where the exception is deleted from the row of all occurences.
Such that
"Recurring event with exception, that date XX should be at date YY"
in OL is converted to two events in KO:
"Recurring event with exception, that date XX is not included"
"Non-recurring event at date YY with same data like the recurring event (e.g. Summary, location, attendee list, ...)"