We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.