Suppose I have term A with children B and C where the children have a 550 tag with broader indication to A. If I go to record A, the tree is built showing B and C. If I add a child D to A, the tree for A is not rebuilt but still showing the old situation. A related problem: If I change term A setting it to a be child of B with a 550 (which it obviously not is), this cyclic relation will trigger deep recursion. Resulting in a gateway timeout and a process eating up resources..
Katrin, If I am not mistaken, you are using it? Could you comment on this?
(In reply to Marcel de Rooy from comment #1) > Katrin, > If I am not mistaken, you are using it? Could you comment on this? Sadly not at the moment, see major bug 23190 - I can't get it to work at the moment.
(In reply to Katrin Fischer from comment #2) > (In reply to Marcel de Rooy from comment #1) > > Katrin, > > If I am not mistaken, you are using it? Could you comment on this? > > Sadly not at the moment, see major bug 23190 - I can't get it to work at the > moment. Could it be related to the first thing mentioned here?
I am not sure - could you try my cataloging example on the other bug or tell me if it looks right to you? Really confused by this one.
(In reply to Marcel de Rooy from comment #3) > (In reply to Katrin Fischer from comment #2) > > (In reply to Marcel de Rooy from comment #1) > > > Katrin, > > > If I am not mistaken, you are using it? Could you comment on this? > > > > Sadly not at the moment, see major bug 23190 - I can't get it to work at the > > moment. > > Could it be related to the first thing mentioned here? A closer look tells me that they are not the same.
(In reply to Marcel de Rooy from comment #0) > Suppose I have term A with children B and C where the children have a 550 > tag with broader indication to A. > If I go to record A, the tree is built showing B and C. > If I add a child D to A, the tree for A is not rebuilt but still showing the > old situation. What you're saying is that if you sit on the parent, it doesn't have a way to know a new child showed up, and you're proposing some automatic bi-directional linking? I like this. > A related problem: > If I change term A setting it to a be child of B with a 550 (which it > obviously not is), this cyclic relation will trigger deep recursion. > Resulting in a gateway timeout and a process eating up resources.. Had to deal with this in production. I wrote a tiny script that does a DFS to find cycles from a leaf, following the $wg path (the $wh are not considered in most of the code as far as I can tell.)