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.
Add a hook in ingestion API to get latest document security information from 3rd party API
If ingestion API supports adding a hook or callback to add an "access control meta-data" enrichment, it could stream integration with custom content with strict permission requirements. Our customer can provide us with an API (hosted in their site...
The Discovery Query Language doesn't allow negated operators for nested querys (ticket existed but hast been closed). Negated operators within a nested query work fine: attributeList:(id::“KEY:9553”,value_string:!Quad-Core-Prozessor),attributeList...
The system entitie is recognized when you write "mi" in spanish language, that's because mi is refered to "miercoles", the next Wednesday of the week. Is confuse used that because if i said "mi tarjeta" I'm refered to my.
Query results for entities extracted with a WKS should include a list of all mentions that are in the entities coreference chain
Currently entities are reported in query results with only one "text" field, even if they are part of a coreference chain (and hence count > 1). This is problematic if you need to search parts of the query results for this entity since it may h...
What a powerful, wonderful teacher Watson could be!!!
Cost effective Watson learning classes would be universally available on the internet!! Watson becomes an individually oriented, teacher and mentor to human users. Watson would bridge the language, location and availablility of classes and learnin...
Often a single concept is repeated in many different intents. If that concept were defined as an entity and that entity includable as part of an example of an intent, it would greatly simplify the definitions of intents.
For example, suppose the c...
Alchemy had types associated with concepts, but Discovery does not. It was useful to filter returned concepts to remove people and locations, particularly if we were displaying those elsewhere. The people returned as concepts, for example, were of...
The relation argument offsets come back relative to the Discovery text, but if you want to do something useful with those offsets it would probably be to add tags to the html. Computing the corresponding offset in the html is possible, but inconve...
Do not place IBM confidential, company confidential, or personal information into any field.