Quote:
Quoting hal9g:

Quote:
Quoting Scooter1836:

Quote:

There is nothing to really resolve here.  The rules cover the matter.

Au contraire. Your solution violates the Rules because you are entering incorrect data into both the FIRSTNAME field and the MIDDLENAME field. Although you have carefully avoided this issue in all of your responses it doesn't change the fact that the Rules specifically state that you are not to enter incorrect data.

Today for the screen credit "A.A. Smith" we enter in "A.A//Smith" because that is the correct data because there are no spaces between the initials and in two fields in the credits.

For the screen credit "A.A.A. Smith" we should also enter "A.A.A.//Smith" becuse that is the credit for the same reason.

In one case the filter makes alterations to one of then and one does not. 
You just want permission to second guess the design and implimentation of the filter and say we should enter it in differently.

It should be entered as on the screen in two fields and only set the common name based on the rules for a common name.

Quote:

Quote:

Right now your position is personal preference, which you are allowed to have in your local database.

Wrong again. Entering the correct data into the corresponding fields in the program is anything but a personal preference. It is required by the Rules.

Your personal preference is to break up the data into three fields, set the common name in a way not defined by the rules and call it a correct representation.

Quote:

Quote:

The true fact of the matter is that based on the current filter behavior and rules, the screen credit of "J.R.R. Tolkien" cannot be entered as "J./R.R./Tolkien [J.R.R. Tolkien]" because the common name is not "J. R.R. Tolkien" based on the CLT or any common name thread.  Since this your proposed manipulation is not backed up by the filter, the rules, or any clarification there is no validity to it as far as a contribution to the online database is concerned.

Oh, I see. So your argument is that since it is wrong in all of the existing profiles in the database, it musn't be corrected. Just another example of why the CLT is a disastrous solution to name linking and why we need to go to a single name field.

Like I said, the solution I proposed gives everyone exactly what they want and preserves the integrity of the data. Obviously that's not your goal.

You and I have different definitions of data integrity.  Your vision of data integrity is "what you want to see" or "What you believe the data should be", mine is based on the rule set defined for that data element in the database by the database owner.  You think the integrity falls into something outside those definitions. 

The solution you propose is not allowed by the rules and allows the propogation of inconsistent data because there is no clear no clear definition on how to consistantly arrive at what you see as correct value. The "real" name as opposed to the "common" name.

Data consistency is important to data integrity.


Again a simple fact of what we have today:

Quote:

The online database captures the name "As Credited", not the person's real name.  The common name is based on the most common credited name for the person within the Invelos database.  Not what you or I may consider the persons "real" name to be.

What we have today is the CLT.  If you wish to propose something different you should take it to the rules forum or propose it as an enhancement.  But in this case a single name field is not going to help you much.

The whole issue of linking and whether to have a single name field or not is a completely different subject any solution is a huge change that will need to involve the database owner.

I think all of us would like to see a different solution for linking, but until we have one we need to work with what we have.

Quote:
When it CHANGES an entry from one thing to another, it is making a correction to ensure data ci
consistency. If I enter it as A./A./ Smith it makes no change. That means it was entered correctly.

Quote:
Can someone post a picture of the actual screen credits - I want to see if they actually show how this name is parsed.

Quote:
Can someone post a picture of the actual screen credits - I want to see if they actually show how this name is parsed.

Edit: I don't recall seeing credits list how the names should be parsed. We make that judgment every time we credit that data.

Quote:
Quoting Kathy:

Quote:
Not only that - who is to say that a space indicates the next letter/word belongs in a different field.

Quote:
Unless you know me, who the hell knows which field any of the letters belong? 

That's kinda my point.  Without actually knowing the person, there is no real way to know so how do we decide how to parse the name?  Rather than guess, I use the fact that the data was presented in multiple parts separated by a space.  If you, the general you not you specifically, can find a better way that doesn't require research by the contributor, I am happy to do it differently