Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
-
Empty show more show less
-
Empty show more show less
-
Add-Ons 19
-
1
Description
1. We provide app-specific aggregators for our magnolia apps like Pages or E-commerce (plus a generic one for content apps).
However, users must specify their own text aggregator in their custom module configuration (in for example pages-content-tags-integration):
map of app-name, textAggregator class and optional workspace and content node type
(YAML?) that the text classification module needs to analyze.
To decorate text-classification yaml cofiguration and add entry to map of text aggregators (entry should contain app-name, textAggregator class and optional workspace and content node type)
Document how to do this.
2. Update the list of supported field types in line with development. See info from Evzen in slack + look at results of TXTREC-48.