Very interesting...
Went to enter children of a profile...in tree view....and some of the children cloned themselves...(duplicated).....but NO 'tree match' flags appeared....
There are also NO tree matches showing in the SEARCH, Merge Issues..
So that is a new thing.....I also made sure to wait for the spinning cycle to finish...AND had just shut down and re-started.
Very interesting...
Went to enter children of a profile...in tree view....and some of the children cloned themselves...(duplicated).....but NO 'tree match' flags appeared....
There are also NO tree matches showing in the SEARCH, Merge Issues..
So that is a new thing.....I also made sure to wait for the spinning cycle to finish...AND had just shut down and re-started.
Very interesting...
Went to enter children of a profile...in tree view....and some of the children cloned themselves...(duplicated).....but NO 'tree match' flags appeared....
There are also NO tree matches showing in the SEARCH, Merge Issues..
So that is a new thing.....I also made sure to wait for the spinning cycle to finish...AND had just shut down and re-started.
Entering a new child from Tree View gets duplicated, too. (example where I merged them: Anna Matilda Ammidon ).
Entering a new child from Tree View gets duplicated, too. (example where I merged them: Anna Matilda Ammidon ).
The duplicates crop up when we're having load problems, as we were this morning. I suspect it may have to do with the configuration of our load balancer, and made an adjustment there (about 90 minutes ago) that I hope will reduce or eliminate the duplicates (at the cost of seeing more broken pages.. time to design a Fail Whale!) About half an hour ago we appear to have resolved the load issues, so everything should be back to normal now. Our apologies for the troubles.
Mike Stangel - not getting my - Mail Notificatons.
It applies to Discussion- not sure about the others
Question...why is it that 'data conflicts' has to be re-visited twice....the 1st time you resolve it...you get the response "data has been updated"......but it remains in the queue.....until you re-enter it...and THEN it will say that "conflict has been resolved." ...and THEN it removes itself from the queue.
It gets tiresome if you have a lot of 'data conflicts'.
Judith: Is this a technical question? That is, are the data conflicts not being 'resolved' after you choose them? If so, give a link to a specific example.
If you are referring to source/reference data conflicts, then that's not a "technical difficult" (the focus of this topic of discussion); that is a genealogical question which -- if it can't easily be documented in the current Geni profile fields -- can be noted in the "About" and/or in a discussion attached to that profile ... and even in a curator note, if it is important for guiding future merges.