ATTENTION Curators, please assist

Resolved. It doesn't appear that they were locked, but perhaps only curators can resolve conflicts on master profiles?

There are some locked fields on those two profiles.

re: locked fields on MP & "resolving data conflicts"

It depends on what is locked. If there are things to resolve with one (or more) of the locked fields, then (evidently) only a curator can resolve it. I know I have resolved data conflicts on MP's, as long as there were none that involved a locked field.

Should have said I have one profile in my merge center that has all the fields locked except one and I can't resolve it.

Eldon I have the same problem with this profile and another one in my merge-center, it is all locked but one option the birth surname but itwont take it
http://www.geni.com/merge/resolve/6000000001045491041

Also
http://www.geni.com/merge/resolve/6000000000769899965
and
http://www.geni.com/merge/resolve/6000000000160866853

That's the way mine are, I just hit another one. I guess some curators don't follow through on them.

Yes, all that is left in my merge center on data issues are the ones that I can not solve myself, pity because I would like to keep the merge-center clear. :(
http://www.geni.com/people/Bj%C3%B8rn-P-Brox/285725352490006131 what are your thoughts on the issue above?

Private User Maybe we need to bring this discussion back to life http://www.geni.com/discussions/86459

Private User, personally I dislike locking, first of all because it creates more work than less for the the curators, secondly because locking of field should only be allowed if the field are attached to a source confirming the value or that there is a curator note stating that the value in the field is a result of making a decision on what to use as the field value when we have conflicting sources, - mostly to stop edit wars.

If these conditions are met we can start talking about automatic removal of data-conflicts for locked fields.

Bjorn I agree, I also dislike the locking system, in particular when you spot a massive error and this can not be changed, like you said it should be attached to a source confirming the value.
Suppose we just have to leave it for now till a solution will be found

Annemarie, when you run into situations like that, do you ever contact the curator to ask them why it's locked or if they would please edit it? We've had some discussions about how likely users are to contact curators about certain issues. Your feedback would be helpful.

I do agree that unsourced fields should never be locked. That's something we can bring up among curators to see if we can make that a more observes guideline.

I should add: I do believe in the locking system, but only in certain cases and with a preference for field-locking instead of full profile. I believe most curators feel the same, based on past discussions.

If the reason for locking a profile is properly marked there should not be a reason asking the curator why.
It is not a question about a guideline either, it is a question about following a guideline, - we have had a similar discussion about MP'ing empty or low quality profiles.

It is obvious why a field or profile is locked, but the problem that I see might be more SW related then anything else.
The profiles can not be removed from the merge centers as there is a data conflict that can not be resolved, all fields exept one 'the birth surname'' are locked, no matter what you do with the birth surname field it will not change and remain in the merge-center as a data conflict
I understand there are different views on whether fields should be locked or not and I can see both sides of the argument but I think the problem that Eldon and I are experiencing is not related to this

This two profiles will show what I am talking about, just try saving them or select the given birth surname and then save, they will still be in the merge-center after

http://www.geni.com/merge/resolve/6000000000769899965
and
http://www.geni.com/merge/resolve/6000000000160866853

Annemarie, Can you check now? I resolved the conflicts, and cannot now see them in my merge center. Are they still in yours?

Justin, two have disappeared from my merge center, one remains and can not be fixed http://www.geni.com/merge/resolve/6000000001045491041, something is happening anyway, thanks a million, how did you resolve this if I may ask?

It's as Bjorn said. On those two profiles some of the fields were locked, so only a curator can resolve the data conflicts for those fields. Curators will generally resolve any conflicts quickly, but sometimes someone might be away for awhile. In those cases, any of us are happy to help.

I also resolved Ragnvald for you. You should take a look at all three profiles and make sure the data is correct. I only did a cursory check. For all the old Norse profiles Bjorn is the guy I go to with problems.

Great thanks for fixing that but it still does not explain that one field does come up as being editable and it is impossible to do anything with it.
I am clearing up Driftwood and that is why I have no solve all these conflicts but then they hang around in my merge-center, not fair LOL

Bjorn always knows these things, so I'll let him answer. My guess would be that it has to do with field locking.

On Ragnvald many of the fields are locked: the name, place of birth, date and place of death, and date of burial. Curiously, the date of burial is two years before the date of death. That seems an odd choice for locking ;)

Which field looks like it is editable?

That is what I mean with maybe only sourced profiles should have a lock function, but contacted the profile manager about this.
The birth surname field is not locked but selecting this makes no difference

Thanks for all you help Justin, you're a star :)

Umn.. I cannot check my records because I am away from home.... but I could swear that this samuel Baker, Samuel Baker had a father named Samuel Baker who I added to Geeni quite some time ago. There are several Baker lines, mine is from the Francis Baker and Twining line, who settled in MA, not CT. Is it possible to somehow recreate what I had in geni originally?

@Sally Thomas

I could not get Geni to "tag" Sally, even though I chose to "Follow" her.

I had entered a Profile for Ruth Holton wife of Thomas Lyman. I see by references she was married 1st to Joseph Baker (of whom I had no Profile), there is referenced that Joseph and Ruth had six children, the eldest Joseph died with his father in 1675, a dau. Ruth who married Ebenezer Alvord, the rest I have seen no names in references, yet.

There are 11 Baker children attached to Joseph, two being Samuel's, both you are main manager of, one is connected to Ruth Holton as his mother and the Sam. you tagged is only connected to Joseph.

I could not tell by the revisions if Joseph had been merged with a Samuel. I don't think it is possible for Geni to recreate what you originally had. Joseph & his father Edward were from Lynn, Mass. & Northhampton, Mass. There was listed in the revisions a Rebecca attached as mother at one time to Samuel (the one tagged) which when I selected to view it listed that you had Deleted her.
Was Samuel's father Samuel married to a Rebecca?

Please contact me when you have the information about Samuel and we then can possibly enter another father for which ever Samuel you think is wrongly connected to Joseph.

ok, Carole... as soon as I get home that is another chore, I have to look up. I have a really good source for the Baker line, at home. Another good thing is that I finally will have a connection to internet, a whopping 6 gigs allowed, so I will be able to do more on here, both Tallman and Baker.

Trying to merge parents of
Astrid Eleonora Ehrenborg
I find the 'other' pair is private and the manager starting that tree was born in 1621 !!? (http://www.geni.com/people/J%C3%B6ns-Ehrenborg/6000000000649288133)

I assume he will not answer any requests?

LOL Bo-Arne, I doubt it if he was born in 1621, did not know Geni already existed then :)

Hi Bo, it is claimed historical profile.
Should be reported to help@geni.com

Bo, I have sorted out this merge, but profile should still be reported.