tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (TIKA-451) Inconsistent date format for Metadata.CREATION_DATE and Metadata.LAST_MODIFIED
Date Mon, 06 Sep 2010 17:54:32 GMT

     [ https://issues.apache.org/jira/browse/TIKA-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Nick Burch resolved TIKA-451.

    Fix Version/s: 0.8
       Resolution: Fixed

I think all the key metadata keys are now defined as Date Properties, and all the main parsers
are updated, so I believe this one is now resolved.

> Inconsistent date format for Metadata.CREATION_DATE and Metadata.LAST_MODIFIED
> ------------------------------------------------------------------------------
>                 Key: TIKA-451
>                 URL: https://issues.apache.org/jira/browse/TIKA-451
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata, parser
>    Affects Versions: 0.7
>            Reporter: Nick Burch
>            Assignee: Nick Burch
>            Priority: Minor
>             Fix For: 0.8
> Currently, the PDF Parser does   calendar.getTime().toString()   which means dates end
up in your local timezone, and are hard to parse
> The Open Document parsers output in iso 8601 format, which avoids these two problems
> The poi ole2 based parsers also output in date.toString() format, with the same timezone/parsing
> We should probably select one format, and update the parsers to all output in it

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message