Background
In both Composer and Video Center, content producers are allowed to associate tags with pieces of content. But the experience and what is output through the APIs is different. The difference in output formats leads to unexpected front end experiences as well as unpredictable data parsing between the two types of content in external tools.
Expected Results
When a topic is searched for in Composer (ex: "bg" searching for a tag "bghgtv"), the producer is presented a list of TAG NAMES associated with a tag containing the letters "bg". From there the producer can then select the TAG NAME "Bluegrass Home and Garden TV" and it is added as a tag.
Once saved, the content can be queried on the API `/content/v4/?website=gray&_id=U6S5QSI7CNBJRBESF6TN7UQBQI`. The returned results contain all (description, slug and text) of the information that is associated with that tag in Global Settings.
EX:
{ "taxonomy": { "tags": [ ... { "description": "Bluegrass Home and Garden TV", "slug": "bghgtv", "text": "Bluegrass Home and Garden TV" } ] }, "type": "story", "canonical_website": "gray", "_id": "U6S5QSI7CNBJRBESF6TN7UQBQI" }I would expect this same result to happen in Video Center. Even if the user experience isn't the same the result should be.
Actual Results
When a tag is selected in video center, this is what get's rendered on the API. Note how the slug is actually displayed in the text key/value pair and that the slug and description are missing.
{ "taxonomy": { "tags": [ { "text": "bghgtv" }, ... ] }, "type": "video", "canonical_website": "gray", "_id": "d7154a9a-fe46-41c5-979a-e1f04e94ea70"}
Sebe Dale
Hi,
I see this has been marked for future consideration for over a year. Is there any update on this?
Thanks,
Luke