[CONTTAGS-15] Select content items by tag for display Created: 24/Jan/13  Updated: 19/Jul/17  Resolved: 19/Jul/17

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

Type: Task Priority: Major
Reporter: Antti Hietala Assignee: Robert Šiška
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Tagging
Sprint: Kromeriz 105
Story Points: 5

 Description   

User story:

Phase 1: As an editor, I want to select content items by tag in a component. For example, I add a tour carousel component on a page and in the component dialog I enter tags "beach" and "family". Now my carousel displays any tours tagged with beach AND family.

Phase 2: As an editor, I want to have the option to start from the page. I add a tour carousel component on a page. In the component dialog I enter a tag "september-sale". No content is tagged with that tag yet but the tag is saved as soon as I save the component dialog. Now I go to the Tours app and tag some tours with "september-sale". The system autocompletes the tag for me because it already exists, helping me avoid typos.

Tasks:

  • Make the tag field configurable so a developer can add it to any component dialog.
  • Allow an editor to use the tag field to select (filter) content.
  • Store the entered tags under the component node.
  • Phase 1: Disallow tags that are not in the container. If a tag does not exist yet don't let the user type use it in the component.
  • Phase 2 (do in Phase 1 if trivial): Allow the user to enter tags that are not yet in the tags workspace. Persist new tags into the tags workspace.

Mockup: 07 Add content to a component by tags
https://invis.io/EUBJ9PG9K



 Comments   
Comment by Robert Šiška [ 19/Jul/17 ]

Adding the TagField to any dialog is already possible. Simply add the field to any component dialog, e.g. like this:

fields:
- name: tourTags
  class: info.magnolia.contenttags.form.field.TagFieldDefinition

Tags are then saved as multi-value property under the component node (or its variation).

Therefore, I'm closing the issue.

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