[ANY23-280] Refactor ContentExtractor to improve extraction flexibility

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 2.2
• Component/s: core, extractors
• Assignee: Lewis John McGibbney
• Reporter: Lewis John McGibbney
• Created: 02/Apr/16 20:01
• Updated: 07/Apr/22 20:19
• Resolved: 27/Dec/17 20:10

Description

As discussed on ANY23-247, the ContentExtractor is simply not fit for purpose. This issue was discovered and the cause has plagued our builds ever since. Any extractors which implement BaseRDFExtractor are based on the Extractor.ContentExtractor and hence work off of an 'unfixed' raw data stream as oppose to a more flexible model such as the TagSoupDOMExtractor.
This issue should refactor RDF extractors to enable more flexibility and to avoid issues we encounter with the strict SAX parsing logic.

Issue Links

• is superceded by: ANY23-318 ExtractionException handling in BaseRDFExtractor.java kills entire extraction
• links to: GitHub Pull Request #24
• links to: GitHub Pull Request #24