[TXTREC-56] Implement multibinding for text aggregators Created: 21/Aug/19  Updated: 03/Sep/19  Resolved: 03/Sep/19

Status: Closed
Project: Text Classification
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Evzen Fochr Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 7h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by TXTREC-58 DOC: how to configure a custom text a... Closed
is depended upon by TXTREC-57 Create generic text aggregator for co... Open
is depended upon by ECOMMERCE-253 Implement text aggregator for ecommerce Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Epic Link: Txt Classification integration
Sprint: Add-Ons 19
Story Points: 8

 Description   

Configuration should be be text-classification module.
map of workcpase, textAggregator class and node type

After start of text classificaton module, we should try to classify texts for all configured aggregators.

App action should be able to target its own text aggregator.

Move move PageTextAggregator to pages-content-tags-integration

Generify TaggingHelper, and SupportedTaggingPagePredicate, pass nodetype and workspace as argument


Generated at Mon Feb 12 11:05:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.