I think this whole process needs to be explained.
By the way, I would not be surprised to learn that you have to read and re-read this explanation a couple of times. The only reason I understand how all this worked and is working today is because I have lived through it. Bear in mind that I have had this explained to me by many different people, not all of whom knew what they were talking about. This post is my best guess so far as to how all this happened.
To begin the explanation, it is important to realize that the database making up the named individuals in New.FamilySearch.org (NFS) came from multiple sources. Those sources included the following:
- The Ancestral File
- The Pedigree Resource File
- The International Genealogical Index (IGI)
- The Church membership records
- The existing Temple ordinance records
NFS tried to resolve these duplicates by using a method of combining records. The idea was to preserve all the information but make a package of all of the differences. Problems began to appear immediately with these individuals that had too many copies in the system. For a reason that remains obscure, FamilySearch cut off the total number of duplicates that could be combined. That total number was changed upward a couple of times, but there were still a significant number of individuals whose duplicate entries exceeded the larger combinatory target number. These individuals are the ones referred to as IOUSs.
That was only the tip of the NFS iceberg. The biggest problem was that users of NFS began combining people who were not the same individual. So we began the process of uncombining (separating) individuals improperly combined.
Now, Family Tree comes on the scene. Theoretically, there is only one place in the Family Tree for each individual. So what happens when Family Tree is using the same database as NFS? The duplicates are still there in the database. Family Tree introduced a "merge" function, so rather than combining the records for duplicate individuals as in NFS, Family Tree merges the individuals and only one is left in the system. Theoretically, again, this should resolve the problem. Except that the merge function did not apply to those IOUS individuals. What about individuals who were improperly combined in NFS? For a while the users could uncombine these individuals in NFS but now what happens? My best guess is that the wrongly combined individuals just come up missing in Family Tree. See Common Family Tree Problems from 11 September 2013 and the comments.
Where does this leave the IOUSs? As long as the two databases, NFS and Family Tree, are using the same data, all the limitations of NFS apply to Family Tree. Hence, nothing can really be done with the extra duplicate ancestors. The problem with this is that the extra people are not just extra people; they are extra entire pedigrees. So making changes to any of the IOUS people is a high risk activity. Your changes may simply disappear when they are finally merged or worse yet, someone could delete the person you are working on.
Yes, Family Tree allows users to delete individuals. There are tons of warning messages but the people do disappear (with all their Temple ordinances attached). So what am I going to do? Continuing waiting. I have been working back about 3 or 4 generations until I get to the level when there are IOUSs and then I am effectively stopped.
Let me know if some of these details are not exactly correct.