"OdsCalendarSyncML" . "2017-06-13T05:38:37.020704"^^ . . "2017-06-13T05:38:37.020704"^^ . . . "OdsCalendarSyncML" . . . "e7a605fa445372601330b842c01e0402" . "OdsCalendarSyncML" . . . . . . . "---++ODS Calendar SyncML\n\nNow ODS Calendar supports synchronization to DAV SyncML folder and back. In order to perform sync, follow the steps:\n\n 1. Go to http://host:port/ods\n 2. Login as user\n 3. Click the Briefcase link from the left vertical navigation. \n 4. As result will be open your DAV/home/[ods-user] folder file content.\n 5. Click New Folder\n 6. Create regular folder for ex. with name mysync\n 7. Go to the new folder and click again New Folder\n 8. Now enter name for ex. calendar and specify SyncML version for ex. 1.1 and SyncML type, for ex. vcalendar 11\n 9. Click Calendar from the left navigation of the ODS UI\n 4. As result will be created Calendar instance ( if you do not have already such) and you will be redirected to its UI.\n 5. Create several events/tasks.\n 6. Go to Import/Export->Manage SyncML\n 7. Click New SyncML\n 8. In the shown form:\n 1. Specify name, for ex. test\n 2. Enter WebDAV SyncML Path, for ex. /DAV/home/[ods-user]/mysync/contacts\n 3. enter username and password\n 4. select (by default) events and tasks to be synced.\n 9. Click Create\n 10. Click Sync\n 11. Specify direction of the synchronization and click the button Sync.\n 12. As result should be shown as message how many events and tasks were synced to the Calendar instance (In) and how many were synced to the DAV location (Out)\n \n---+++Synchronization in Background\n\nSuppose you already have synced your events/tasks from the Calendar instance to the DAV location as described above. Then, when there is a change on some of the fields for a current event/task in your Calendar, this change on Save action will be also triggered to the DAV location's event/contact. \n\n---+++References\n\n * [[VirtuosoSyncML][Virtuoso SyncML]]\n\nCategoryODS CategoryOpenSource CategoryCalendar" . "2017-06-13T05:38:37Z" . . . . "2017-06-13T05:38:37Z" . . . . . . .