AEM Taxonomy Implementation

[nsvsrk]

Hi all,

I am following https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/page-authoring/expert-advi... to understand AEM Taxonomy.

This subject looks very dry.

Could you share an implementation (even a fictitious one) with AEM Taxonomy please?

That way I will be able to correlate it with the implementation to get a better view.

Appreciate all your replies.

Thanks,

RK.

[Tethich]

AEM Taxonomy is more like a concept, a best practice on how to organize things as per your needs. A taxonomy can vary a lot depending on what each project needs to implement. But at the end of the day it a custom scheme meant to ease your work by categorizing things into groups or classes or however you want to call it. Usually they should help to quickly find things by marking them with specific elements from the taxonomy.

The documentation page already gives an fictional example with the cars.

[nsvsrk]

Hi,

Thanks for replying.

"The documentation page already gives an fictional example with the cars.".

Which page?

 https://experienceleague.adobe.com/en/docs/experience-manager-learn/sites/page-authoring/expert-advi...

I could not complete reading it.

But does it explain the schema, customizing it and applying?

Thanks,

RK.

[nsvsrk]

Checked up the whole page.

It only depicts the categorization and sub categorization like:

/subject/car/
/subject/car/sportscar
/subject/car/sportscar/porsche
/subject/car/sportscar/ferrari

I am fine till this.

But after this step what should we do?

How to implement this in AEM?

Is it like we add /subject/car/sportscar/ferrari to a ferrari asset as a tag, so that search results become more precise?

Will a tag accept "/" in its body?

Where is Taxonomy Schema here?

I am not getting this subject end to end.

That is why a sample implementation will probably help.

Thanks,

RK.

[Tethich · Accepted solution]

AEM has some good documentation on how and why to use Tags: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/siteandpage...

But here we are talking about taxonomy, which is only a concept helping you to decide how to organize your tags, the idea being to later best support the site functionalities.

And yes, tags can have / in their paths. Below is a simple example of nested tags, which is like a taxonomy. How you leverage the taxonomy (eventually through some custom development which may read and use this taxonomy) is totally up to you. Your project AEM architect should have a saying in this.

[Harwinder-singh]

@nsvsrk  I came across a linkedin article where the author has made an attempt to come up with some guiding principles when it comes to AEM taxonomy. Have a look at this and may be this will help you in your quest  

https://www.linkedin.com/pulse/mastering-tags-adobe-aem-practical-approach-boost-content-mgsqe