After running the Tree Count Report, I have a total of 395 persons that are not related. This was determined with a Count of 1. Requesting if there is an easier way to mark and delete these perons in a “batch”. Any advice is greatly appreciated.
Could you - yes most likely – but I would be selective on how I did those batches.
I would find out why I ended up with that many - and how many diff trees you have – sometimes small fixes can fix many things at once – though it is not always easy to find what removed person or relationship broke things
Background: I had been working with my tree for more than 20 years and it was just getting very dirty and would take a long time to clean and get in a “decent shape”. So, I exported all my persons (a total of more than 26000) with just the names, events dates and places for importing into clean file. Then I could get the places straight (in a good format) and with a cleaner file. (hope this makes sense as I was trying to save 30 plus years of some of work.)
As an alternative, I tried to start a new on Ancestry and then build from me, but I was struggling with the persons. As was moving backwards from the 1950 census, there were children being born, growing up and leaving and parents moving in with the family.
Since I don’t like the way Ancestry creates sources, I have a source file naming system. For my documents, I use Clooz to handle these files.
Hopes that this provides some background. If your recommendation is to “start over with me”, then that is doable.
Thank you so much a that did the results - 312 unattached were deleted.
Mic drop words of wisdom right there.
As an I.T. professional, I learned lonnnggg ago to always back-up first and then always do small incremental changes rather than sweeping ones.
In this particular case, there’s a reason why those people made it into the database. Deleting them without identifying why that happened could result in deletions that cause havoc or loose important data. And you won’t realize it until much later.
2 Likes
exactly – and must harder to get things back even if half them should be deleted for example
1 Like
Similarly often why they do “roll outs”
1 Like
Maybe a silly question, but why delete them at all? These people got into your database for some reason, even if it was a long time ago. As has already been said, deleting them without knowing exactly why they were there in the first place may cause you more problems than it solves. Less than 400 out of 26,000 doesn’t strike me as being unreasonable - less than 2% of the total.
1 Like
I have two trees in my database. My main tree and one call ZZ, Unconnected tree. The later has all those little trees I’m not sure where they fit into the main tree. I have them colored tan so I spot them in the indexes. Once I know where they fit I unconnect them from that second tree.
2 Likes
exactly my thoughts – but its their database – but It sounds like their OCD to have not other detached people is more important to them…