Can the search box within AEM Guides be configured to index DITA content?

[ScottFa4]

I have been struggling to identify an answer to this question via documentation or previous posts.  Our users are finding the behavior of this search box in Guides confusing / unhelpful in comparison to, say, the Assets search.   Is it possible to change/configure what is searched via a query within this search box specifically?

From testing, searches performed within this search box do not cover the range of properties or within the content that the Assets search does. Near as I can tell, this search is more limited to terms present in file names and/or titles.    However, users do not want to leave Guides to find what they need and then have to navigate back into Guides to work on it.  Ideally for our users, they would be able to search here and get hits within the DITA map/topic content.

Note that I am familiar with the instructions at https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/install-guide/on-prem-ig/... and have successfully created options to search DITA elements as an advanced search option within the filtering menu.  But, that is NOT what I need, as it does not appear to index those same fields/xpaths to the box above as part of a more general search experience unless I am missing something.

Please direct me to the right configuration location to configure this if it is possible.  Even just using the same search index as the Assets search here would be an improvement.  Thank you.

[punagpal]

The repository search in AEM Guides supports full-text search with various filters, such as DITA, Image, last modified date, etc., similar to the Assets search functionality.

To perform a custom search or add custom filters, you can modify the uiconfig.json file in the FolderProfile to include your specific query.

For instance, to search for the property cq:name in the AEM repository, you can add it to uiconfig.json (as shown in Screenshot 1), displaying results like those in Screenshot 2.

If you have additional feedback regarding the repository search, feel free to reach out to me directly (I’ve DMed my email ID) or contact your CSM.

Screenshot 1

Screenshot 2 

-Pulkit Nagpal

 

[ScottFa4]

Respectfully, that did not answer my question.  I do not want to add a new custom search box.   I want to improve what the existing search box does (the one I indicated in my screenshot, and is at the top of yours).  That search box does not search full text as it stands today.   I was trying to get clarity on whether that is something that is configurable / misconfigured in our implementation.