IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Enhance Knowledge Studio support for commonly accepted CSV formats

Problem

The current implementation of Watson Knowledge Studio imposes very strict (narrow) limitations on the CSV content format that is used for importing Dictionaries.

Knowledge Studio requires that each value is enclosed in double-quotes.

This makes it a) very difficult to produce Dictionaries that are accepted by Knowledge Studio and b) very difficult for novice users to figure out why their dictionaries are rejected by Knowledge Studio.

Solution

While there's no official standard for CSV content formatting, there are widely used and accepted rules in practice that pretty clearly define several flexible options for unambiguously specifying the CSV content, while not imposing strict single format.

See a good example here: https://tools.ietf.org/html/rfc4180

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 16 2018
  • Future consideration
Why is it useful?

Importing and using dictionaries in Knowledge Studio is fundamental for almost every Knowledge Studio project. Very often dictionaries are prepared by the clients outside of Knowledge Studio, and these pre-existing dictionaries may follow different CSV formats.

Most projects start with importing existing dictionaries. Not supporting commonly used CSV formats becomes a roadblock for Knowledge Studio adoption.

Who would benefit from this IDEA? Knowledge Studio project manager who organizes the work, including creating/importing various assets, like dictionaries.
How should it work?

Knowledge Studio should support dictionaries in commonly used CSV formats, like https://tools.ietf.org/html/rfc4180

  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions