Provide Out of the box Vocabularies

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Categories
• Labels:
  • d_20_05
  • echo-board-in
  • echo-not-test-scope
  • fc_20_06
  • fc_20_07
  • fc_20_08
• Epic/Theme:
  • Content_Performance_Analytics
• Epic Link: echo-taxonomies-for-marketers
• Sprint: TANGO | SP_36 | May12-May26, TANGO | SP_37 | May26 - Jun09
• Git Pull Request: https://github.com/ealonso/liferay-portal/pull/2991

Motivation

Vocabularies’ new configuration options (see LPS-115314) are aimed at increasing flexibility in application and covering more use cases. They also seek to empower different kinds of users that may have specific requirements in terms of content metadata, so content can be tracked, searched and reused by other areas of the organization. 

Specifically, OOTB Audience and Stage vocabularies will allow marketers to audit their content as they will be able to know which content areas are best covered and also to spot content gaps, in order to improve their content strategy execution. 

To facilitate the onboarding and adoption of this new content auditing feature, we will provide OOTB vocabularies that won’t be deletable, along with contextual help to show users how to use them. Topic vocabulary will also be provided OOTB with a different preset.

The new vocabularies to create are:

1. Audience
2. Stage 

These vocabularies should be configured to apply only to Web Content articles. 

These vocabularies should be global and usable for content of all sites of Virtual Instance.

Also we will maintain Topic as OOTB Vocabulary with the current configuration.

Persona

Content author / content strategist / marketer.

Design

https://www.figma.com/file/NPKvcY0e7rdqJGTRlw4gFG/LPS-111333-vocabularies-configuration-extension?node-id=306%3A2354

Technical Requirements

Audience and Stage vocabularies will have the following attributes:

• will be set by default in the CE and DXP versions. 
• will have virtual instance as scope
• will have no categories defined

• For internal use only will be ON

• Allow user to select multiple categories will be ON
• will be associated with web content
• won't be required
• won't allow creating subcategories
• All preset configurations can be edited
• will be created and edited by users with permissions to create web content AND edit these new vocabularies
• An informative text will show in all vocabularies tabs: Learn how to tailor categories to your needs. "Learn how" will link to a video /documentation page in the Help Center (TBD).

Topic OOTB vocabulary will have the current configuration, and: 

• For internal use only will be OFF

Acceptance Criteria

• Given a CE or DXP installation
• When the user accesses the Categories administration application in the Global Site 
• Then the Global vocabularies Audience and Stage show

–

• Given the Global vocabularies section in a site's Categories administration application
• When a change in Global Vocabularies is made (deleted, new categories added, new vocabularies added)
• Then the Global vocabularies section in a site's Categories administration application updates accordingly

–

• Given a site which is not Global
• When the site administrator accesses to the Categories administration application
• Then the existing Global vocabularies appear as locked and it's not possible to edit them

–

• Given the Audience or the Stage vocabularies
• When the user goes to Edit
• Then default values are:
  • For internal use only ON 
  • Allow user to select multiple categories ON 
  • will be associated with web content 
  • won't be required

–

• Given any site 
• When the user goes to the categories section
• Then a help message with a link to documentation shows 

Test Scenarios

AC ID	Test Strategy	Test Scenarios	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd? (unit or integration)	Poshi?
01	Smoke	When the user goes to Edit the Audience or Stage vocabularies, the default values are: For internal use only ON , Allow user to select multiple categories ON, will be associated with web content, won't be required	no	no	yes
02	Regression	When the user goes to the categories section, a help message with a link to documentation is displayed	no	no	yes
03	Sanity	When the user clicks on the link to documentation, the documentation link is opened	no	no	yes