[TIKA-928] Separation of Tika Core Properties From Metadata Processing

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.1
• Fix Version/s: 2.0.0-BETA, 2.1.0
• Component/s: metadata
• Assignee: Unassigned
• Reporter: Ray Gauss II
• Created: 16/May/12 22:06
• Updated: 17/Aug/21 13:30

Description

The Metadata class is a bit overloaded with both processing and core Tika properties defined in the same place.

Separating the core properties into a TikaCoreProperties class which contains only composite properties which reference other standards like DublinCore will allow the Metadata class to focus on processing and ease the transition from the now deprecated String properties that were directly included in Metadata via the implements clause.

This will also allow us to cherry pick only the properties we want from a standard as Tika core properties rather than having to include all the properties in a standard's interface, some of which may be more specific to a particular content type than we want.

Issue Links

• is related to: TIKA-947 AbstractMetadataHandler addMetadata Does not Check Property.isMultiValuePermitted