[MGNLDAM-747] Indexing configuration should not exclude mgnl:tags property Created: 04/Apr/18 Updated: 15/Jul/20 Resolved: 26/Apr/18 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | DAM JCR Provider |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.1 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Periscope back-end MVP | ||||||||
| Sprint: | Basel 141, Basel 143 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
By default Magnolia ships with an indexing configuration which excludes all so-called "system" properties. However, at least one of such properties, mgnl:tags, needs to be indexed and searchable.
This is required by Periscope since we want customers to search by image tag in the search bar.
PR at https://git.magnolia-cms.com/projects/PLATFORM/repos/main/pull-requests/592/overview |
| Comments |
| Comment by Federico Grilli [ 19/Apr/18 ] |
|
As agreed during arch meeting, since not all workspaces are tag-able, this should be more a per workspace indexing configuration rather than a system-wide one. I'm therefore going to revert the changes from this ticket. |