[MGNLPER-41] Support content-tags in an EE context Created: 30/Jul/18  Updated: 30/Aug/18  Resolved: 29/Aug/18

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

Type: Task Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPER-35 Convert NeuralNetwork into an EE modu... Closed
relates to CONTTAGS-70 Provide content tags via PeriscopeTag... Closed
dependency
depends upon MGNLPER-40 Make Periscope work in CE (without co... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Periscope back-end MVP
Sprint: Basel 154
Story Points: 8

 Description   

Whenever Periscope runs in an enterprise-edition context, make sure filtering by content-tags is supported. This could potentially be achieved by having an EE specific module for periscope.

Furthermore, enable the corresponding filter in FindBar.

Add an interface to core or similar and use it in Periscope and FindBar.
The implementation of the interface will be in content-tags-core and it'll simply delegate to the constant (TagManager.TAGS_PROPERTY) as well as having the necessary methods to replace usage of TagManager directly from FindBar and instead of that intermediate interface. Perhaps even having a method which checks whether the tags-module is installed or not. (optional)


Generated at Mon Feb 12 10:28:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.