Yes you should include a comment like that in your notes, since we as voters have no way to know that.

Skip

Quoting skipnet50:

Quote:
Yes you should include a comment like that in your notes, since we as voters have no way to know that.

Skip

That's what I wanted to make sure.  It would start to get anonying to submitted changes that included "established" BY, state that there were established in other profiles, and have someone ask for other documentation

Quoting Unicus69:

Quote:
I had this exact conversation with Ken...well not this exact conversation, but one similar.  The rule Rick quoted was created sepcifically for these situations.

*cough* James *cough*

Now we know why he is m. cellophane.        

Skip

now this question.  since the BY of Jason Mewes has already been propgated to several profiles, do we leave it or try to correct it?  I say leave it since it is not hurting anything.  I ask because I recieved a PM I am sure I am going to ignore more or less telling me my vote is wrong because even though Jason Mewes is in the database with a BY (which I stated so the submitted knew why I was voting how I was) per the rules it needs to be removed.  I know what the rules state about adding BY and it does say "If the birth year change is due to an accepted change to another profile, indicate that."  Now I don't know what documantation was given for it to originally be there since I did not submit it and I know the new submitter should have stated that it was already there in whatever profile, but I don't feel it needs to be removed.

I've already pulled all my hair out...well maybe not quite all. OUCH


Skip

I fear it may have to become year of birth is accepted

Oh well, least we could then sort by person's birth year 

I recall seeing the BY for Jason Mewes last week on other contributions. I have it in my db and I didn't add it there myself.

Quoting RHFactor:

Quote:
(how can it be pre-existing if this entry is trying to add it and I can vote no?).

It's pre-existing to another profile. There's no master actor db, so the BY gets added one by one as profiles are uploaded and downloaded by various people. It will show as an addition to each new profile that it affects, but that doesn't mean that the user is adding it intentionally.

It goes like this:

User 1 uploaded BY for Actor 1A to Profile A.
It gets accepted.
User 2 downloads the update for Profile A.
The BY for Actor 1A populates the master db of User 2.
User 2 uploads Profile B which includes Actor 1A and the BY.
It gets accepted.
User 3 downloads the update for Profile B.
The BY for Actor 1A populates the master db of User 3.
User 3 uploads Profile C which includes Actor 1A and the BY.
It gets accepted.
...and so on...

The BY's spread each time they're accepted, downloaded, and re-uploaded to a different profile. Voting no on Profile C will only keep it from getting into Profile C for now. But the BY will still propagate as the other users upload and download.

Even if you succeed in deleting the BY from all existing online profiles now, it's already in the master db's of many users. As they continue to upload and download, this will continue to spread.

There's really no way to stop it, as far as I can tell. And that's why it's good to have the rule that says, basically, if it's already been accepted, indicate that.