Oumar-
On a different list some folks were discussing the best way to represent ideophones in FLEx.
One aspect that came out is that in the entry for the ideophone, one may want to list the specific items it can modify, but in the entries for those items, one may not want to list all the ideophones that can go with them. Thus, the need for a unidirectional relationship.
Others noted that normally when providing ideophone information, it may be quite important to include an example, to show how it is used in context.
In your example towards the end of your message, it sounds like you don't want an entry for the ideophone itself, but you want the information about it in the entry it modifies--is that correct?
To respond to a couple specific technical aspects of your question:
- When you set up a Lexical Relation, you have the choice of *what kind* of relation it is, as well as what level of the hierarchy it occurs at. Thus, a relation can be an entry-level relation, or sense-level, or "entry or sense"-level. If you created a relation but don't see it on the Senses, please to to the Lists area and look at your lexical relation, and in the field "reference set type", see if it has the word "entry" or "sense" or "entry/sense".
- Lexical relations are bidirectional links between two main entries. If you want a link where one entry is a main entry and the other is a minor entry, then that relation would need to be either Variant or Complex Form.
I'll stop here; there is much that could be written about this topic.
-Beth