Good question Private User... I've been mulling over whether we should talk about reverting to that as the solution.
1. It's a huge endeavour to find Curators to service that many profiles, because, of course, it doesn't prevent duplicates being made at a dozen a day; it just prevents them being merged in - so now that Curator has to come and sort the duplicate out, every time one is made. That's a lot of work to keep doing year in and out after your paid day job - The hundredth time you've merged in an unsourced duplicate for Charlemagne (and checked that the parents, siblings, marriages etc all match - & fixed the tree conflicts where they don't - often involving research to check details), you start to lose your sense of humour :-) or your interest in maintaining that part of the tree. Fewer and fewer curators are prepared to keep doing this. It's pretty thankless.
2. Before power mergers, leaving the profile unlocked, or just locking known fields was the way to go, because then ordinary managers could still help complete the merges, and follow through on any tree conflicts; but now that there are people who can create 20 tree conflicts in one power merging session on Geni - and who aren't stopping to fix the conflicts as they create them, we simple can't keep up. Which means errors compound upon errors.
So it's a bit of a 'damned if you do & damned if you don't' situation.
This is an attempt to stem the tide by catching the unsourced duplicates BEFORE they're grabbed by power mergers and merged into the world tree (because that initiates a chain of merges on the rest of the unsourced duplicate tree - each with the potential for a new set of tree conflicts.)
What I'm doing right now is first cutting that profile's relationship ties so it doesn't bring a whole new tree with it, and then merging it in. This only applies to the historical tree, where duplicate lines don't bring new information, and often disrupt the accurate info we have already have.
So, the short answer is: Locking would mean the entire Medieval Tree would have to be Curated by a couple of people dedicated to merging in the same old duplicates day in and out. We don't have enough people.
Geni is reluctant to stop new users adding profiles to the Historical (pre 1500) Tree, although that would keep it as something we and the managers could then perfect, instead of just swimming against the current of merging duplicates into it.
So, the solution we are trying here, is to get as many of the users who are interested in the Medieval tree - including the power mergers - to help maintain it.
It isn't obvious to everyday users how much work is created when you make a duplicate for an already existent historical tree. Someone has to merge it in, and research the discrepancies in your tree as they go. And there are many every day. So, the thought is that, if we spread the word and get those users to help us instead, we might have a chance of turning the tide.
(Just call me Moses :-))
Problem with this page?
Geni Pro
Geni member
Geni Pro
Geni Pro
Geni member
Geni member
Geni member