Quoting Lopek:

Quote:
You do have the option - you get to preview all updates before deciding whether to accept them. 

And you win the Booby Prize for not reading what I said.  I can't accept an otherwise good cast list if it has a birth year in it, so I'm prevented from getting good updates, nor can I make a contribution that is otherwise perfectly good if it zaps the birth year that is already there.  In other words, I'm being forced to accept changes to my local database I don't want in order to be able to utilize the full function of the program.  That is WRONG!  It's just as wrong as it would be of me telling all of you that you can't have birth years at all for some reason.

BY and common name MUST BE made opt in/opt out to be fair to everybody across the board.

Quoting Lopek:

Quote:
Erm, hang on to your booby prize, you did not say that. I fully understand what you are saying, but you can opt out of accepting BYs into your database which you impied you could not:

Quote:
Anything that changes data already in my database without giving me the option to say no is wrong.

You do have the option to say No - it has consequences, but it is there.

I agree it is not ideal, or easy to deal with, but that is life sometimes.

There is no reason it can't be made opt in/opt out.

I don't see why they would.  The program seems to (correctly) treat actors with different BY as two entirely different people.  It's only a problem when it automatically propogates that BY to someone who doesn't have one....sometimes it guesses wrong.  The best solution would probably be a dialogue box that asks if you want to change the no-BY person to have the new BY.

Quoting Unicus69:

Quote:
Quoting gardibolt:

Quote:
I don't think so....if you have the BY in one, it will propagate into all the profiles of the actor without a BY (though not if there is a BY).  Maybe I don't understand how this is working, but I think that's right.

You have it correct.

Yes, sadly correct 
My cast are a mess with BY propogating from using the headshot database

Looking forward to seeing Ken's solution....soon hopefully 

Sod the CDC - someone call Jack Bauer! 

Quoting tas314:

Quote:

I download a profile for a new DVD (A). Later I download a profile for DVD (B), it has a BY and it infects DVD (A) without me knowing.

I make a cast change, I might see the date but I know I didn't add it. Unless it's way off I may not know it's wrong and if I'm not doing a full audit I'm not going to check every detail.  Submit, if it's a long cast list I may not notice the change in the date year. I'm only expecting to see the change I made after all.

Please use birth years only to distinguish between otherwise identical cast and crew. New birth year submissions must be documented.

What birth year? I didn't add one? WTH

This is covered in the rules: "If the birth year change is due to an accepted change to another profile, indicate that."

Quoting Rifter:

Quote:
There is no reason it can't be made opt in/opt out.

Yes, there is a reason. Ken would have to change the program. Maybe he will sometimes in the future. To help this, you could write a feature request in the appropriate forum. Until then we don't have this option. But we do have the birth year feature and rules how to deal with it.

Quoting Unicus69:

Quote:
Quoting lyonsden5:

Quote:
Quoting Unicus69:

Quote:
This is covered in the rules: "If the birth year change is due to an accepted change to another profile, indicate that."

Except that is not the case anymore. There have been profiles where this note has been added yet they are still declined because of the birth year.

I am wondering if that is being caused by the popularity of the headshot db?  I know a lot of people are getting BYs from there and not from previously accepted contributions. 

Probably.  I know I've had to cull a ton of them out after using those headshots.