[STANBOL-414] Refactor EnhancementEngine to support contents with multiple related parts

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Component/s: Enhancer, Rules
• Assignee: Unassigned
• Reporter: Reto Gmür
• Created: 07/Dec/11 16:18
• Updated: 09/May/12 13:47
• Resolved: 23/Feb/12 05:26

Description

Some notes from a discussion with Rupert and Olivier

ContentItem

• getBlob() returns a blob of type multipart/mime iff the ContentItem was created from a multipart/mime content
• ci.getBlob() eq ci.getPart(0, Blob.class)
• ci.getUri()+"_main" eq ci.getPartUri(0)

Rest
/enhancer
/enhancer/engine/<engineId>
/enhancer/chains/<chaiId>

• query params:
  Optional inputWithMetadata -> expects multipart/mime with 2 sections of which the first is rdf
  Optional outputWithContentParts[=<section-ordinal>] -> the result is multipart (instead of rdf) containing rdf as the first section and the parts in the second section, if there is more than one part this second section is itself multipart, this argument might be repated to have different sections
  Optional omitMetada -> no metadate in the result, makes only sense with outputContentParts argument, the result will correspond to the second section of the malipart returned without this argument

Issue Links

• is related to: STANBOL-44 Use an adapter pattern in ContentItem
• relates to: STANBOL-478 Change Metaxa Engine to create PlainText version as ContentPart and change other Engines to retrieve PlainText version from ContentPart

Sub-Tasks

• Multi ContentPart RESTful API extensions: Closed