[CONTTAGS-76] Default implementation of content tagging for Assets Created: 18/Jun/19  Updated: 23/Aug/22

Status: Open
Project: Content Tags
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: AuthorX

 Description   

In M6.0 the Assets app has content tags enabled. I can see any existing tags in the browser view and the detail view.

In M6.1-SNAPSHOT 2019-06-18 the Assets app does not show any tags, although when I view the assets in the JCR browser I see that they do have tags.

The Assets app should have tags enabled as this is a standard use-case for tagging.

Notes:

  • related to dx-core module not containing image recognition modules anymore
  • tags in JCR come from 6.0 demo
  • should Content Tags provide the default implementations or should this move to the DAM module?
  • customers can enable content tagging on any app


 Comments   
Comment by Christopher Zimmermann [ 19/Jun/19 ]

If DAM module adds the tag UI, what will happen on community edition where tags are not present/supported?
I would rather expect the Content Tags module to decorate any app where tags should show up.

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