[TXTREC-58] DOC: how to configure a custom text aggregator Created: 21/Aug/19 Updated: 05/Sep/19 Resolved: 05/Sep/19 |
|
| Status: | Closed |
| Project: | Text Classification |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Julie Legendre | Assignee: | Julie Legendre |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 1.0 | ||
| Remaining Estimate: | 1h | ||
| Time Spent: | 5h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Epic Link: | DOC: Text Classification add-ons documentation 1.0 | ||||||||||||||||
| Sprint: | Add-Ons 19 | ||||||||||||||||
| Story Points: | 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): 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 |
| Comments |
| Comment by Julie Legendre [ 05/Sep/19 ] |
|
Reviewed by Evzen. |