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

Staffan Olsson updated TIKA-482:
--------------------------------

    Attachment: testTIFF.tif

New version of testTIFF needed for the added tests. Metadata diff:
9c9
< Exif.Image.StripOffsets                      Long        2  8 19208
---
> Exif.Image.StripOffsets                      Long        2  3084 22284
17a18,19
> Exif.Image.XMLPacket                         Byte      2500  (Binary value 
> suppressed)
> Xmp.dc.subject                               XmpBag      2  cat, garden


> 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.

Reply via email to