[
https://issues.apache.org/jira/browse/TIKA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916481#action_12916481
]
Staffan Olsson commented on TIKA-482:
-------------------------------------
Attached a combined svn patch for the fixes above.
* Added XMP parsing of Title, Subject and Description with encoding support
* Date extraction to Dublin Core fields matches javadoc for the fields
* All EXIF parsing done the same way
* EXIF tags that are mapped to fields of the same name unless the name is a
defined Tika field (for backwards compatibility -- they should have been added
with a namespace such as "exif:" from the start)
* multi-value keywords
Questions:
* Reading the same input stream twice in JpegParser and TiffParser, is this
how to do it in Tika?
* Finding out if a string is a defined Tika field, is the new class necessary?
* What if the parsing of an exif field throws exception, should we attempt to
extract the remaining fields anyway?
> 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, 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.
