request the nested fields will be available also in the Content Mining UI as well.

Our client are using the Box crawler in the Watson Discovery.

This crawler is crawling data from the Box, however when analyzing documents in the Content Mining UI, it is unable to use facets which comes from metadata such as the author, folder name so on.

When trying to add a new facet in the collection edit view in the Content Mining UI, there are no facets related with the metadata as above.

However, In case of the tooling UI, we can add a metadata facet as a new facet in "Facets" page under "Improve and customize".

We tried this way, unfortunately it didn't work well due to the strange behavior.

If we add "metada.source.path_collection.entries.name" as a new facet on "Facets" page, the Watson Discovery appears to have successfully saved the setting.

After for a while, this setting is disappeared as if facet setting we added has been initialized.

Of course, re-indexing are not performed and we can't see this facet in the MinerUI.

We inquired this issue as CS2563571.

As a result, we received the answer, which users can define facets from nested fields like "metada.source.path_collection.entries.name" in tooling UI, however CM doesn't support facets from nested fields.

(Support team answered they will fix Tooling UI side not to be able to add nested field as facet.)

What our customer want to realize:

The customer's Box has folders which are divided by year, such as "2020", "2021".

Moreover, there are many folders which are divided by month and by department underneath the folder divided by year.

They are seeking for a best practice to analyze the trend for each department or each year.

The lack of this feature is very disadvantageous, because the metadata obtained by Box crawler are most usefulness for text mining analysis.

We strongly desire the nested fields such as "metada.source.path_collection.entries.name" will be available also in the Content Mining UI as well.