[JIRA] Created: (DSY-735) import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of repository server)

import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of repository server)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------

         Key: DSY-735
         URL: http://issues.cocoondev.org//browse/DSY-735
     Project: Daisy
        Type: Bug
  Components: Import-export  
    Versions: 2.3    
 Reporter: Marc Portier
    Priority: Minor


Apparently XMLizerUtil uses the same code for format/parse of the date value to/from XML for both date and datefields.

For the Date-fields this causes unexpected effects: 28/07/2009 ends up in the exported file as
<field type="My-Date-Field" value="2009-07-27T22:00:00.000+00:00"/> simply because it was exported on a repository running in GMT+2

In the case of date-fields however I think it would be enough to just export the value without time and timezone fragment, thus like:
<field type="My-Date-Field" value="2009-07-28"/>


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

    [ http://issues.cocoondev.org//browse/DSY-735?page=comments#action_13821 ]

Marc Portier commented on DSY-735:
----------------------------------

This issue is mildly related to DSY-577.
(Different area though, but same 'too much detail for dates' leading to similar effects)

> import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of repository server)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DSY-735
>          URL: http://issues.cocoondev.org//browse/DSY-735
>      Project: Daisy
>         Type: Bug
>   Components: Import-export
>     Versions: 2.3
>     Reporter: Marc Portier
>     Priority: Minor

>
> Apparently XMLizerUtil uses the same code for format/parse of the date value to/from XML for both date and datefields.
> For the Date-fields this causes unexpected effects: 28/07/2009 ends up in the exported file as
> <field type="My-Date-Field" value="2009-07-27T22:00:00.000+00:00"/> simply because it was exported on a repository running in GMT+2
> In the case of date-fields however I think it would be enough to just export the value without time and timezone fragment, thus like:
> <field type="My-Date-Field" value="2009-07-28"/>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

    [ http://issues.cocoondev.org//browse/DSY-735?page=comments#action_13822 ]

Marc Portier commented on DSY-735:
----------------------------------

Workaround:

Given the fact that the timezone is applied in the VM doing the import-export (and not directly the repository in this case)
The unwanted effects of this bug can be avoided by introducing -Duser.timezone while running the daisy-export, daisy-import tools.

> import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of repository server)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DSY-735
>          URL: http://issues.cocoondev.org//browse/DSY-735
>      Project: Daisy
>         Type: Bug
>   Components: Import-export
>     Versions: 2.3
>     Reporter: Marc Portier
>     Priority: Minor

>
> Apparently XMLizerUtil uses the same code for format/parse of the date value to/from XML for both date and datefields.
> For the Date-fields this causes unexpected effects: 28/07/2009 ends up in the exported file as
> <field type="My-Date-Field" value="2009-07-27T22:00:00.000+00:00"/> simply because it was exported on a repository running in GMT+2
> In the case of date-fields however I think it would be enough to just export the value without time and timezone fragment, thus like:
> <field type="My-Date-Field" value="2009-07-28"/>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

     [ http://issues.cocoondev.org//browse/DSY-735?page=all ]

Marc Portier updated DSY-735:
-----------------------------

    Summary: import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of host running the imp/exp)  (was: import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of repository server))

Proposed workaround (previous comment) made me realize the timezone causing the trouble is not the one of the host/vm running the repository

Still, the proposed solution (trimming time part) seems the more robust way to handle things.

> import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of host running the imp/exp)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DSY-735
>          URL: http://issues.cocoondev.org//browse/DSY-735
>      Project: Daisy
>         Type: Bug
>   Components: Import-export
>     Versions: 2.3
>     Reporter: Marc Portier
>     Priority: Minor

>
> Apparently XMLizerUtil uses the same code for format/parse of the date value to/from XML for both date and datefields.
> For the Date-fields this causes unexpected effects: 28/07/2009 ends up in the exported file as
> <field type="My-Date-Field" value="2009-07-27T22:00:00.000+00:00"/> simply because it was exported on a repository running in GMT+2
> In the case of date-fields however I think it would be enough to just export the value without time and timezone fragment, thus like:
> <field type="My-Date-Field" value="2009-07-28"/>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

     [ http://issues.cocoondev.org//browse/DSY-735?page=all ]
     
Marc Portier closed DSY-735:
----------------------------

    Resolution: Fixed
     Assign To: Marc Portier

Fixed in 5307
http://svn.daisycms.org/viewsvn/daisy?view=revision&revision=5307

> import/export includes time and timezone fragment on DATE fields, causing dates to shift when imp/exp happens in different timezones (setting of host running the imp/exp)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DSY-735
>          URL: http://issues.cocoondev.org//browse/DSY-735
>      Project: Daisy
>         Type: Bug
>   Components: Import-export
>     Versions: 2.3
>     Reporter: Marc Portier
>     Assignee: Marc Portier
>     Priority: Minor

>
> Apparently XMLizerUtil uses the same code for format/parse of the date value to/from XML for both date and datefields.
> For the Date-fields this causes unexpected effects: 28/07/2009 ends up in the exported file as
> <field type="My-Date-Field" value="2009-07-27T22:00:00.000+00:00"/> simply because it was exported on a repository running in GMT+2
> In the case of date-fields however I think it would be enough to just export the value without time and timezone fragment, thus like:
> <field type="My-Date-Field" value="2009-07-28"/>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy