If I create a tag with the name "pröva", AEM will create a cq:tag with:
If I now tag an asset with this tag, the asset nodes metadata\cq:tags property references the jcr:name of the tag and not the jcr:title of the tag, e.g. the asset will now have cq:tags set to "prova".
This means when using the omnisearchbar to try and retrieve the asset using the native spelling of the tag (i.e. searching for "pröva") nothing is returned.
This is because the omnisearchbar performs the following query:
(/jcr:root/content/dam//element(*, nt:folder)[(jcr:contains(., 'pröva'))] | /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(., 'pröva'))])
And of course jcr:contains will only look at the cq:tags property and won't find pröva anywhere.
I have contacted Adobe support, but they told me to " update the indexes definition so that tags jcr:title are also part of the index" which as far as I can tell is a useless response.
Are the only options:
Appreciate any guidance, as Adobe support were unable to help, despite insisting AEM has full support for languages.
In other words, the problem is just looking for the name of the tags (because it's part of the reference to the tag), and not the jcr:title of the tags, which are referenced from the assts. Is that correct?
From a technical point of view this is expected, because JCR imposes some limitations on node names. That means if jcr:title does not match the name, you won't find the asset. Another limitation is also, that if you change the title of a tag but not its name, and you are using this new name to find any asset, you won't get any result.
In both cases it's the problem that the jcr:title of a referenced path is not considered for search, thus more likely a missing feature than a bug.
Search is built on Lucene.
So this isn't so much an omni-search issue rather than the index definitions are not tokenizing the characters.
For example, ootb AEM will not tokenize Chinese.
You need to look at adding an analyzer to your index definition to handle your Swedish word
You can probably get away with the StandardAnalyzer.
There's some rough steps on how you can do this if you scroll most the way down this article :
Look for this section "SPECIFYING THE ANALYZER CLASS DIRECTLY"