I was about to make a minor change in the profile of the UK release of Undercover (5050725901026) when the following screen had appeared:



I decided to proceed and contribute the crew changes as well.
Needles to say that my initial intension was to contribute just the correct SRP and nothing else to begin with.
The original contributer claimed, and I quote:

Quote:
why was the crew names changed? Do you have them locally this way (only sure names)?
I don't know of any autofilter which does this changes.

When I replied and said that I haven't done any other changes her said:

Quote:
Hm, very strange indeed. Since in my opinion the crew changes are wrong - I mean, it should be 1stName/LastName

To be honest? I agree with him completely.
Any thoughts?

The only thing that crossed my mind is that I also own the US release.

Quoting m.cellophane:

Quote:
Quoting liorb22:

Quote:
I decided to proceed and contribute the crew changes as well.

What do you believe you are contributing for crew?

What it appears to be is that the names in your local database for Oola Bloom, Walter Gernert and Kent Smith are all using the first name field rather than being properly parsed to Oola//Bloom, Walter//Gernert and Kent//Smith.

Rather than contributing them, I would recommend that you adjust the names in your local database to match the parsing shown in the existing contribution. At the very least, do not contribute the crew if you choose to leave your local as-is.

That's the thing - I want to correct my local DB. I've tried to update the profile but to no avail.
Eventually, I contributed just the SRP of course.

Quoting liorb22:

Quote:
That the thing - I want to correct my local DB. I've tried to update the profile but to no avail.
Eventually, I contributed just the SRP of course.

Ah, ok. There was a change recently with the update system so that if you have a name in your local db that differs from the online db only in the way it's parsed, the system will not overwrite your local parsing.

Good = If you want to control your local parsing so that updates don't mess with your choices.

Bad = If you have parsing errors in your local, an update won't automatically fix them to match the online db.

Quoting liorb22:

Quote:
Quoting m.cellophane:

Quote:
Quoting liorb22:

Quote:
That the thing - I want to correct my local DB. I've tried to update the profile but to no avail.
Eventually, I contributed just the SRP of course.

Ah, ok. There was a change recently with the update system so that if you have a name in your local db that differs from the online db only in the way it's parsed, the system will not overwrite your local parsing.

Good = If you want to control your local parsing so that updates don't mess with your choices.

Bad = If you have parsing errors in your local, an update won't automatically fix them to match the online db.

They should let us choose which function is preferred.
Who wants faulty info anyway?

Depends on the sight.
Sometimes there are many different parsings (and yes, also sometimes wrong parsings) in online database. If the download would change your local parsing, with every downloaded different parsing your cast member would change. As it is now you can stay on the parsing you think is correct.
Of course at contribution such thing as in your example can happen.

To choose which function should be done, would be great, but imho for some users more work they won't do. (So if optional: Yes, please add)