Page MenuHomePhorge

Investigate kolab2 to kolab3 conversion issues
Closed, ResolvedPublic8 Story Points

Description

A migration led to a lot of invalid kolab objects. Figure out why they were created in the first place and how to deal with them

Details

Ticket Type
Task

Event Timeline

mollekopf raised the priority of this task from 60 to High.Mar 7 2016, 10:06 AM

An event has been transformed with empty created date:

From:
<creation-date>2012-09-12</creation-date>
<last-modification-date>2012-09-12</last-modification-date>

to:

<created>
  <date-time/>
</created>
<dtstamp>
  <date-time>2012-09-12T00:00:00Z</date-time>
</dtstamp>

The full message looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<event version="1.0" >
 <product-id>Test</product-id>
 <uid>testuid</uid>
 <creation-date>2012-09-12</creation-date>
 <last-modification-date>2012-09-12</last-modification-date>
 <sensitivity>public</sensitivity>
 <pilot-sync-status>0</pilot-sync-status>
 <start-date>2012-10-10T14: 00:00Z</start-date> <summary>test</summary> <organizer> <display-name>Display Name</display-name> <smtp-address>test@test.com</smtp-address> </organizer> <attendee> <display-name>Test Test</display-name> <smtp-address>test@test.com</smtp-address> <status>accepted</status> <request-response>false</request-response> <invitation-sent>false</invitation-sent> <role>required</role> </attendee> <show-time-as>busy</show-time-as> <end-date>2012-10-10T16:00:00Z</end-date>

Which is not even valid xml (the event closing tag is missing.
Also, creation-date and last-modification-date MUST be UTC date-times, not date-only values.

libkolabxml has been enhanced to detect invalid creation dates. Also, kolab-format has been enhanced to not write out objects that had an error during conversion.

vanmeeuwen subscribed.

The tests clearly start failing with this commit added.

https://git.kolab.org/harbormaster/build/3035/?l=0