[jira] [Commented] (TIKA-2455) Flag in metadata for alternative email bodies

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on TIKA-2455:
--------------------------------------

mattcg opened a new pull request #205: TIKA-2455: flag the containing multipart type
URL: https://github.com/apache/tika/pull/205
 
 
   Flag the type of bodies contained within a multipart body.
   
   This allows alternative bodies to be distinguished from attachments, for example, and ensures that information on this structure is not lost in the output from Tika.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Flag in metadata for alternative email bodies
> ---------------------------------------------
>
>                 Key: TIKA-2455
>                 URL: https://issues.apache.org/jira/browse/TIKA-2455
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.16
>            Reporter: Matthew Caruana Galizia
>            Priority: Minor
>              Labels: attachments, multipart, rfc822, rfc822parser
>
> When multipart RFC822 emails are being parsed, there's no way to distinguish between alternative versions of the body and attachments.
> It would be ideal if some kind of flag were set in the metadata passed to the {{EmbeddedDocumentExtractor}} that indicates that the stream is an alternative.
> In GUIs that present the data extracted from the email, alternative bodies can be distinguished from attachments and presented separately.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)