In order to manually merge the relationship data from one company to another, I went to the Company > uses Gold smelted by research page for CPI International Holding Corp. where I would try to 1) add Foxconn Technology Group (Hon Hai Precision Industry Co) to the relationship answer list and 2) delete Hon Hai Precision Industry Co. (Foxconn) from the relationship list.
So, I added Foxconn TG, there were two fields, one for company name and one for answer, where 134 was automatically filled in. I did not change the number, because I thought I will delete the other value and it will end up at 134 again anyway. I submitted, and then noticed that all the other relationship answers were Yes. I went back into the edit interface and tried to change the 134 to Yes, but that got a rat. Then, I realized that I had not even added the data for the correct year! It was supposed to be 2014, not 2015. I went to delete it and the message I got (see screenshot attached) deterred me - will it delete only that answer, or the entire list of relationships mapped?
I haven't yet tried to delete the Hon Hai value, because I screwed up the other company so much, and am afraid of deleting all the data. So if I get confirmation on the above issues (adding the correct answer of Yes, and deleting only one answer within the entire relationsip data set) I will go ahead.
This is related to the automated merging, but I did just discover that there were some relationship data problems with one of the seemingly successful merges. I merged Hon Hai into F this afternoon, but check the data now it seems Hon Hai shows up alongside F in 2014, and for 2015 has an answer (though F does not)
https://wikirate.org/CSP_Inc?filter%5Bnot_ids%5D=&sort=answer&filter%5Bname%5D=hon
Just to overly confuse things, I realized after the merge fact that I shouldn't have merged Hon Hai into F in the first place, so if it was easy enough, I'd be happy if we could restore Hon Hai to its previous state. In any case I wanted to flag the potential merge issue.
Am I correct in thinking:
1. The above issue is resolved, BUT
2. relationship editing is still broken, and
3. so is relationship counting (or at least it's not getting triggered as it should)
note: discussed in slack. She thinks above is accurate but is going to look closer to confirm.
The relationship editing is fixed, and we have a separate ticket (https://wikirate.org/Relationship_answer_rendering_incorrect_numbers) for the counting issues.