[TIKA-759] Better handling of content type metadata

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: metadata, mime
• Assignee: Unassigned
• Reporter: Jukka Zitting
• Created: 21/Oct/11 11:04
• Updated: 15/Jul/15 16:53

Description

Currently we use the "Content-Type" metadata key for storing (and looking up) the media type of a document. This is simple enough and works well especially with HTTP, but not too well in line with XMP or other metadata standards like Dublin Core. So as an improvement I propose the following:

• Switch to "dc:format" as the standard metadata key for the content type
• Keep the existing "Content-Type" key for backwards compatibility with existing clients
• Make the Metadata class aware of such aliases
• Add getFormat() and setFormat() utility methods to Metadata to simplify client code and to make the exact metadata key more of an implementation detail in Tika

Issue Links

• depends upon: TIKA-859 DublinCore Metadata Keys Should be Prefixed and Property Objects