[CONTTAGS-3] Use the existing tags workspace Created: 12/May/17  Updated: 24/Aug/17  Resolved: 23/Aug/17

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

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: AntonĂ­n Juran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLTAGS-75 Migrate to new workspace (5.6.x)/ pre... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Tagging
Sprint: Kromeriz 102, Kromeriz 110
Story Points: 3

 Description   

Persist content tags in the tags workspace. Store them hierarchically as the number of nodes in the workspace can grow rapidly impacting performance of the Tag Management app. See Technical prerequisites, recommendations

Use the mgnl:tag node type.

The workspace and node type are currently used by the Marketing Tags module. You will have a conflict until we can resolve it in the next major release.

  • Warn users about the conflict. It should not be possible to use the Tags module and the Marketing Tags module simultaneously.
  • Add a conditional install task that prevents the user from installing both modules on the same instance.
  • Don't bundle the new Tags module with Magnolia.

In the next major release (Magnolia CORE 5.6):

  • Increment the major version of Marketing Tags.
  • Migrate marketing tags out of the tags workspace into a new marketing-tags workspace.
  • Create a new content type mgnl:marketing-tag
  • Start using the tags workspace for content tags.
  • Start using the mgnl:tag content type for content tags

Generated at Mon Feb 12 00:24:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.