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.
When using the "istool" command for glossary import, if in the .xml file that is imported there are relationships (Synonyms, Has A, Is A etc) between terms also present in the xml file and other terms that are not in the xml file nor on the target IGC, the whole import fails. For Synonym relationship it gives the following error: Term <<term_name>> defined as a synonym, does not exist. Synonym groups can only refer to existing terms or terms defined in the import file. For other types of relationships, it gives only an Untyped Exception and in the service logs it gives a Null Pointer Exception, without stating the term that causes the error. So basically no terms can be imported just because a few relationships, each time when new imports need to be done. Because of this it's very difficult to keep one IGC as a central instance for other IGC environments, so the impact is on daily basis.
Do not place IBM confidential, company confidential, or personal information into any field.