Ideas for Arc XP

In many content management systems, when an editor adds a tag to a story, a list of parent tags is suggested as relevant to that story also, as there’s a hierarchical structure behind it. This “automatic” metadata enrichment is not only positive in terms of SEO, but is also available to feed other services such as DMP clusters on a more granular way, as well as introducing an accurate level of analytics and data in terms of consumption metrics, being part of a specific field in a datalaye at a fronte end levelr.

In ARC, there’s no hierarchy in the tag service , so there’s no relationship available to create an automatic enrichment function, which will for sure reduce the capacities of all the mentioned areas in customers already using a hierarchical tag service.

In order to mitigate this we though that “custom embed” could be a good way to extend Ellipsis capabilities re. tags when an external source is available:

1. A Custom Embed panel would allow the introduction of a tag.
2. Given this tag, we could feed its parent tags through an external service calling (i.e. calling our current hierarchical tag service)
3. The best approach as a last step would be to fill in the “tags” field with that information coming from our system. If this is not possible in ANS, any other field would at least allow storing that relevant information for business and metric purposes.