[SRCHIDXFDR-2] Stories are index too fragmented making it hard to use the data in the algolia search frontend Created: 06/Jul/22 Updated: 28/Jul/23 |
|
| Status: | Open |
| Project: | Search Index Feeder |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jan Schulte | Assignee: | Raphael Falvo |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
When we hit that within our content editor apps (Stories) we end up with every sub-node of the composition.Is this expected?On the one hand I can see some usefulness in pushing more content recursively, but on the other hand it results in a TON of records pushed to Algolia that are hard to relate back to an actual content item, making it not all that useful for the Algolia frontend. |
| Comments |
| Comment by Raphael Falvo [ 25/Jul/22 ] |
|
Hello jschulte , for website context, Algolia module is filtering on mgnl:page node, to transmit only pages data. There is no filter for stories context. "mgnl:composition" is used as root type for story app entries. Shall we add a filter on this node type on stories context to fix this ticket? [EDIT on 2022/07/25 14:26]: well, it's a little bit more complex, while page has all content information as attributes, stories are using subnodes for blocks. Limiting to only root node would prevent indexing any blocks information, which is I guess not what we want either |