Multilingual Searchability for Site Name and Term Store

%3CLINGO-SUB%20id%3D%22lingo-sub-2733984%22%20slang%3D%22en-US%22%3EMultilingual%20Searchability%20for%20Site%20Name%20and%20Term%20Store%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2733984%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EAs%20someone%20who%20works%20constantly%20with%20multilingual%20organizations%2C%20I%20do%20want%20to%20take%20the%20opportunity%20to%20share%20some%20frustrations%20around%20the%20limits%20of%20the%20current%20multilingual%20support.%20While%20many%20are%20grateful%20to%20see%20some%20subtle%20but%20useful%20improvements%20like%20elevating%20the%20labelling%20of%20translations%20into%20the%20UI%20(e.g.%2C%20Site%20Name%2C%20Site%20Description%2C%20Navigation%20Links%2C%20etc.)%20there%20are%20some%20really%20big%20gaps%20for%20large%20enterprise%20clients.%20I'll%20focus%20on%20a%20couple%20here%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E1.%20Site%20Name%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3ECurrently%20the%20Site%20Name%20is%20only%20searchable%20by%20its%20original%20name%2C%20not%20any%20of%20its%20translations.%20A%20French%20user%2C%20for%20example%2C%20may%20not%20know%20the%20Site%20by%20any%20other%20name%20than%20what%20he%2Fshe%20sees%20in%20French%2C%20so%20this%20result%20in%20Search%20is%20very%20confusing.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22DavidFrancoeur_1-1631132147761.png%22%20style%3D%22width%3A%20569px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F309071iB7972AC73A178F96%2Fimage-dimensions%2F569x158%3Fv%3Dv2%22%20width%3D%22569%22%20height%3D%22158%22%20role%3D%22button%22%20title%3D%22DavidFrancoeur_1-1631132147761.png%22%20alt%3D%22DavidFrancoeur_1-1631132147761.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20understand%20this%20is%20likely%20the%20current%20product%20of%20the%20fact%20that%20only%20original%20values%20are%20being%20%3CU%3Eindexed%3C%2FU%3E%2C%20(while%20translations%20are%20being%20swapped%20in%20on%20the%20fly)%20we%20do%20need%20to%20be%20able%20to%20search%20by%20by%20crucial%20properties%20in%20alternate%20languages%20otherwise%20we%20are%20delivering%20a%20seriously%20sub-par%20experience%20to%20these%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20only%20current%20workaround%20is%20to%20add%20the%20French%20Site%20Name%20to%20the%20site's%20English%20Description%20which%20does%20help%20connect%20the%20dots%20but%20does%20not%20solve%20the%20root%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EExample%20adding%20the%20French%20site%20name%20in%20the%20English%20description%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22DavidFrancoeur_2-1631132173731.png%22%20style%3D%22width%3A%20564px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F309072iF942CF12F4D40B96%2Fimage-dimensions%2F564x181%3Fv%3Dv2%22%20width%3D%22564%22%20height%3D%22181%22%20role%3D%22button%22%20title%3D%22DavidFrancoeur_2-1631132173731.png%22%20alt%3D%22DavidFrancoeur_2-1631132173731.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E2.%20Term%20Store%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EThis%20same%20problem%20plagues%20the%20effective%20searchability%20of%20metadata.%20While%20I%20am%20the%20first%20to%20applaud%20the%20updated%20Term%20Store%2C%20the%20inability%20to%20search%20by%20translations%20is%20a%20huge%20thorn%20in%20the%20side%20of%20any%20organization%20attempting%20to%20leverage%20effective%20content%20management.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20updates%20would%20be%20greatly%20appreciated%20and%20I'll%20be%20happy%20to%20disseminate%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2733984%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Search%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2754141%22%20slang%3D%22en-US%22%3ERe%3A%20Multilingual%20Searchability%20for%20Site%20Name%20and%20Term%20Store%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2754141%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F293102%22%20target%3D%22_blank%22%3E%40DavidFrancoeur%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20bringing%20that%20up%2C%20I%20totally%20agree%20with%20you!%20I%20am%20also%20implementing%20a%20bilingual%20environment%20and%20I%20am%20struggling%20with%20the%20searchability%20of%20the%20translation%20from%20the%20Term%20Store.%20I%20spent%20a%20considerable%20amount%20of%20time%20translating%20each%20term%20and%20only%20to%20find%20that%20they%20are%20not%20searchable%20is%20a%20very%20big%20disapointment%20and%20a%20huge%20thorn%20in%20my%20foot%20for%20change%20managment.%20The%20only%20reason%20we%20used%20this%20feature%20is%20to%26nbsp%3Bto%20encourage%20better%20collaboration%20between%20our%20French%20and%20English%20speaking%20employees.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20I%20would%20like%20to%20add%20that%20the%20communication%20sites%20can%20be%20bilingual%2C%20but%20it%20is%20not%20the%20case%20for%20team%20sites.%26nbsp%3BThe%20homepage%20of%20a%20team%20sharepoint%20site%20is%20therefore%20available%20in%20only%20one%20language%20and%20the%20pages%20cannot%20be%20translated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20love%20to%20see%20solutions%20to%20those%20pain%20points.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

As someone who works constantly with multilingual organizations, I do want to take the opportunity to share some frustrations around the limits of the current multilingual support. While many are grateful to see some subtle but useful improvements like elevating the labelling of translations into the UI (e.g., Site Name, Site Description, Navigation Links, etc.) there are some really big gaps for large enterprise clients. I'll focus on a couple here:

 

1. Site Name

Currently the Site Name is only searchable by its original name, not any of its translations. A French user, for example, may not know the Site by any other name than what he/she sees in French, so this result in Search is very confusing.

DavidFrancoeur_1-1631132147761.png

I understand this is likely the current product of the fact that only original values are being indexed, (while translations are being swapped in on the fly) we do need to be able to search by by crucial properties in alternate languages otherwise we are delivering a seriously sub-par experience to these users.

 

My only current workaround is to add the French Site Name to the site's English Description which does help connect the dots but does not solve the root problem.

 

Example adding the French site name in the English description

DavidFrancoeur_2-1631132173731.png

2. Term Store

This same problem plagues the effective searchability of metadata. While I am the first to applaud the updated Term Store, the inability to search by translations is a huge thorn in the side of any organization attempting to leverage effective content management.

 

DavidFrancoeur_4-1631132936716.png

 

Any updates would be greatly appreciated and I'll be happy to disseminate them.

1 Reply

Hello @DavidFrancoeur 

 

Thank you for bringing that up, I totally agree with you! I am also implementing a bilingual environment and I am struggling with the searchability of the translation from the Term Store. I spent a considerable amount of time translating each term and only to find that they are not searchable is a very big disapointment and a huge thorn in my foot for change managment. The only reason we used this feature is to to encourage better collaboration between our French and English speaking employees.

 

Also, I would like to add that the communication sites can be bilingual, but it is not the case for team sites. The homepage of a team sharepoint site is therefore available in only one language and the pages cannot be translated.

 

I would love to see solutions to those pain points.