Please DON'T merge in unsourced duplicate profiles on the Medieval tree.

Remove as in "delete profiles"? Do you do this before or after telling the offending duplicator that you'll do it?

Should we adopt this for Scandinavian Sagas too, Alex Moes?

I do not feel responsibility for duplicators this high up in the established historical tree. If the profile is sourced, I will spend time with the manager. If it's unsourced, and created this year - I won't put more time into it that it took to create it.

I tend not to delete because they will just get added back. I cut all its relationship ties, so it floats away from the world tree. This way, if it gets merged in, it doesn't create Tree Conflicts.

Harald, I am not sure at this point how i feel.

If the duplicate is an obvious match for an existing profile then how is disconnecting it easier/faster/neater than just merging it in?

Conversely if it is not a match for an existing profile surely it needs some consideration before either deleting or merging, again i am not sure where the benefit of creating a floater comes from.

Having said that the last time I got on a camel it gave me a dirty look, i am pretty sure it was thinking "how come everyone else gets to carry a little kid around and i get this big lump sitting on my back!".

I don't really like deleting profiles, i'd rather smerge than delete unless the manager is a fake profile. I think When we get relationship locking this issue with duplicates will need more focus on why the duplicates get made rather than how to get rid of them. Especially frustrating when cleaning particular section is to discover dupes being made at the very same time! Obviously i should just work faster :)

I suppose I did a similar thing with Odin's family when i was disconnecting odd profiles or wrong ones and tagging them in a Discussion so that I could come back to them later.

I think it was Arnfred at the time who said i should have used a Project to link the profiles?

A very interesting discussion.

I have posted in the curator site, on the subject.

Well worth working through.

Thanks Anne. Better there. I've answered.

Request management is there for a reason, and the tree has a warning device to alert you when you're making duplicates. If you nevertheless continue to do it, surely you are responsible at some stage?

Cutting relationship connections means that the profile can be merged in without creating Tree Conflicts. As Alex points out, this is more work than deleting it, & more work than it took it create the duplicate to start with, but I am a believer in putting in the effort, if it reduces the overall work input. Which it does, if we get enough people aware and watching to catch and isolate the first profile merge in before the line gets merged in - causing exponentially increasing merge in and tree conflict fixes this high up in the tree.

Exactly what you did when cleaning Odin's tree, Alex, is what this project is about.

France 1000
Someone who has forsaken, had written in 2011:
[dirty clone 2007] Grimolt( Grimould) de Plessis (not listed in that family, in fact there is a son in more)
[line MP 2008] Grimoult du Plessis

This is an old dead Discussion - Please post Duplicates to this active Discussion tohttps://www.geni.com/discussions/158450?msg=1282337 to avoid running duplicated Duplicate discussions.