[jira] Commented: (TIKA-482) Refactor image and jpeg parsers for access to MetadataExtractor API

["Staffan Olsson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TIKA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922448#action_12922448 ] 

Staffan Olsson commented on TIKA-482:
-------------------------------------

I've had this running for quite a while now and it looks stable. If the patch is too complex I suggest (again) that we remove the non-namespaced EXIF fields. It will break backwards compatibility as you said Nick, but Tika is still 0.X and the names of EXIF fields differ between cameras anyway. I suggest copying all the fields with an "exif:" prefix instead, as there would be no risk for conflicts with defined fields and the raw output of all metadata fields would be clearer.

> Refactor image and jpeg parsers for access to MetadataExtractor API
> -------------------------------------------------------------------
>
>                 Key: TIKA-482
>                 URL: https://issues.apache.org/jira/browse/TIKA-482
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 0.7
>            Reporter: Staffan Olsson
>         Attachments: testJPEG_commented_pspcs2mac.jpg, testJPEG_commented_xnviewmp026.jpg, testTIFF.tif, TIKA-451-DublinCore_and_TIKA-482.patch, TIKA-482_exif_and_xmp.patch
>
>
> When I added support for more image metadata in TIKA-472, i realized
> the current design had some restrictions:
>  * I could not access the typed getters from Metadata Extractor, such
> as getDate (to format iso date) and getStringArray (for keywords).
>  * The handler function was called one field at a time which prevents
> logic where one field depends on the value of another (there is for
> example record versions and fields that specify encoding)
> See attached patch. It refactors TiffExtractor to MetadataExtractorExtractor.
> The patch also includes the date fix, see https://issues.apache.org/jira/browse/TIKA-451#action_12898794
> We can later add more Extractors using other libraries, and map to parsers based on format. For example we already use ImageIO in ImageParser so maybe there should be an ImageIOExtractor.

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