tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-2747) Expose custom MAPI properties as a result of the OutlookExtractor metadata
Date Fri, 05 Oct 2018 12:17:00 GMT

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

Nick Burch commented on TIKA-2747:

We'll certainly need a sample file with some of these properties to be able to work on this

I'd guess we'd expose them with a custom prefix, as we do for some other formats for their
custom extension properties?

The TODO (probably written by myself some time ago...) does make me worry about how easy it
will be to properly process them though!

> Expose custom MAPI properties as a result of the OutlookExtractor metadata
> --------------------------------------------------------------------------
>                 Key: TIKA-2747
>                 URL: https://issues.apache.org/jira/browse/TIKA-2747
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 1.17
>            Reporter: Vittorio
>            Priority: Blocker
> We'd like to be able to access through the OutlookExtractor metadata result to custom
MAPI (not listed in  org.apache.poi.hsmf.datatypes.MAPIProperty) properties for .MSG files.
> In particular we're referring to this comment on MapiProperty class in apache poi-scratchpad
>     // 0x8??? ones are outlook specific, and not standard MAPI
>     // TODO See [http://msdn.microsoft.com/en-us/library/ee157150%28v=exchg.80%29]
>     // for some
>     // info on how we might decode them properly in the future
>     private static final int ID_FIRST_CUSTOM = 0x8000;
>     private static final int ID_LAST_CUSTOM = 0xFFFE;
> It's a blocker for our business because our customers' classification system uses the
range in question.

This message was sent by Atlassian JIRA

View raw message