In light of the problems that have appeared in the implementation of both the Birthyear field and the Common Name field, I am requesting that both be disabled pending a viable solution being found for each one that enables them to work properly.

Personally, I have absolutely no use for either one, and do not wish to have that data in my records.  However, as currently implemented, I have to either lock myself nearly completely out of the update process, or spend MY time chasing down and removing said data from my records.  It appears as well that I can't upload a profile update using just "as credited" data without breaking the common name thing for other users. 

As I suggested in the Contrib. Rules forum, these features should be run on a parallel installation until ALL the problems are worked out in such a way that those who want the data can have it, and those who don't can have that, without penalty on either side.  You went to a great deal of trouble to implement partial updates, and these new features will break that for many of us to a greater or lesser degree depending on preference.  I don't see it as a step forward at this point.

So, what it basically boils down to is this:

1. Each user should be able to "opt in" or "opt out" as s/he sees fit on Birthyear and Common Name on the download side.

2. The use of Birthyear and Common Name should not penalize anyone who wishes to upload "as credited" only profiles.

Serious question, John.  Do you really have no use for the common name field?  I like being able to click on an actor's name and seeing all films he/she has been in regardless of the name credited - especially with the ability to put an image onto the entry.

As I said in the other thread.. when it comes to both Birth Year and Common Names... they might not be the only way to do it... may not be the best way to do it... but it is the way Ken decided to implement it.

I understand what John is saying.... if you under no circumstances want Birth Year or Common Names in your database it is almost impossible to do without downloading a profile... then going over every cast and crew name... and then you have to keep all cast lists local only. That is about the only way to completely keep Birth Years and Common Names out.

That being said... I see no problem with Birth Years and Common Names being in the profiles... I don't see them as hurting anything by being in there... and they do have the capability to do what they are designed to do if they are implemented correctly. Both has already helped some of my profiles.

so when it comes right down to it... even though I can see John's side of it... I myself also can not support his moratorium... as I find both features helpful.

@Original Poster:
Why didn't you make this a poll?
Maybe because it would emphasize how ridiculous your request for a moratorium is?

and how would someone know how to vote if they only have one of the movies?

Quoting skipnet50:

Quote:
As I have said before, and i think the simple translation of what John said, a simple association system that does not involve changing the As Credited in any way

The current system does not change As Credited either.

Quote:
Lon Chaney=Lon Chaney Jr=Lon Chaney, Jr=Lon Chaney, Jr.

No matter how the user searches, he will get the same set of titles

This could be set up to allow users to get results based on the specific search for example just Lon Chaney.

While it is true that the 'as credited' data does not appear in the filter system, if you have linked all of those names to, for example, Lon Chaney, Jr. and you have deleted all of the other names and you search for Lon Chaney, you'll find Lon Chaney, Jr. and all of his films.

Quoting skipnet50:

Quote:
You missed a key phrase in my comment, "in any way"

We still have 'As Credited' data, but it's entered together with the common name. Are you saying you want the program to look like it did before and have a separate interface to get into the linking?

I am saying that with a simple association system, James, no interface would be required as such and it would be invisible to the users, it would affect searches and that is all. I am not saying anything about what I might want, I am speaking as another programmer who sees a different method, nothing more or less. But that is essentially irrelevant.

The single most important question right now, is without a standard for ALL of us to use, I don't see a way forward. That is where the energy needs to be spent.

Skip