[
https://issues.apache.org/jira/browse/TIKA-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552078#comment-17552078
]
Nick Burch commented on TIKA-3768:
----------------------------------
If we can put something into a properly typed + structured metadata field, we
will!
The full list of metadata property definitions are spread across the interface
in
[https://tika.apache.org/2.4.0/api/org/apache/tika/metadata/package-summary.html]
grouped by type. Wherever possible we re-use existing well known definitions
While we always store the metadata values as strings, the definition properties
will help you turn it back into the underlying java types, eg get the date back
as a java Date
> message/rfc822 does not include Headers in extracted text
> ---------------------------------------------------------
>
> Key: TIKA-3768
> URL: https://issues.apache.org/jira/browse/TIKA-3768
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 2.4.0
> Reporter: Sam Stephens
> Priority: Major
> Attachments: email.txt
>
>
> When running AutoDetectParser on message/rfc822 structured text documents,
> such as the attached [^email.txt], the extracted text does not include any of
> the headers, such as the Subject and From and To lines.
> However these lines contain useful text I'd like to be able to extract. I'm
> surprised it's not there based on the include everything bias I saw on
> https://issues.apache.org/jira/browse/TIKA-3710.
> Interestingly, if I exclude org.apache.tika.parser.mail.RFC822Parser as a
> parser, my debugging appears to show
> org.apache.tika.parser.csv.TextAndCSVParser being used for parsing, and we
> get the full text, but the returned content type is 'message/rfc822;
> charset=windows-1252'.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
