I am sorry if I am being thick but how would Ken have named the fields if he just wanted them in order of credit? The reason in America Last Name = Family name is because that's the convention and the cultural norm. You are really saying for Asian Names
First Name = Last Name
Last Name = First Name
Middle Name = Middle Name
Incidentally I appreciate this is the UK not the US  and we do tend to go overboard on such things but for a few years  the guidelines for the public sector are that family and given names or surname must be used not first, last or christian to avoid offence. You may want to look at what the fields are called on an American Passport 

Quoting Graveworm:

Quote:
Well at the moment we are supposed to pick the most common according to the credit lookup tool. That leaves the problem that it may change over time.

[...]

Another problem is when the screen credits were entered incorrectly in the first place, for instance a Last Name in the First Name field. Then, if you go by the Look-up Tool to determine the "Common Parsing", so to speak, you will just end up going on and on in the same mistake.
I think the Credit Look-up tool should be used to determine the most frequently credited name on screen, not the most frequent decisions on parsing made by some DVDP users when they enter the data in the program.

Quoting surfeur51:

Quote:

As usual, as rules for some people are more important than common sense, we get 10 pages of useless discussions...

This is not a "rules vs. commons sense" debate, though.   
I think we should just enter the data exactly as it appears on screen and according to the name of each field in DVD Profiler, thus enter a Last Name in the Last Name field where it belongs.  I think that's absolutely per the Rules.
For instance, if screen credits show
Last Name // First Name
[...]
Wayne John
Gong Li
and so on

we should enter "Wayne" and "Gong", exactly as they appear on screen, in the Last Name field, because they are Last Names.

And when credits are listed as

First Name // Last Name
[...]
John Wayne
Li Gong
and so on

we should enter "Wayne" and "Gong", exactly as they appear on screen, in the Last Name field all the same.


This way,  we would avoid duplicate records for John Wayne and Wayne John.


BTW, the same goes for Roles and Names.

I don't care if credits are listed as

Name1 Role1
Name2 Role2
and so on

or as

Role1 Name1
Role2 Name2
and so on

In either case, I would enter the Name as a name and the Role as a role, and it seems to me that's what the program asks us to do.

Quoting skipnet50:

Quote:
Are you confusing Credied As with Alias system.

Once again: we have no "alias system", we only have "credited as". Ergo: confusing them isn't possible...

Quoting EnryWiki:

Quote:
Quoting Graveworm:

Quote:
Well at the moment we are supposed to pick the most common according to the credit lookup tool. That leaves the problem that it may change over time.

[...]

Another problem is when the screen credits were entered incorrectly in the first place, for instance a Last Name in the First Name field. Then, if you go by the Look-up Tool to determine the "Common Parsing", so to speak, you will just end up going on and on in the same mistake.
I think the Credit Look-up tool should be used to determine the most frequently credited name on screen, not the most frequent decisions on parsing made by some DVDP users when they enter the data in the program.

My understanding of the credit look-up tool is that it looks at the 'credited as' field.  If a name has been parsed as 'Chow/ /Yun Fat', it will show up in the look-up tool as 'Chow Yun Fat'.  That is why, if we start entering these names as 'Yun Fat/ /Chow, it is very important to use the 'credited as' to enter 'Chow Yun Fat'.  If we don't, the results will get skewed the wrong way.

Quoting EnryWiki:

Quote:

This is not a "rules vs. commons sense" debate, though.   
I think we should just enter the data exactly as it appears on screen and according to the name of each field in DVD Profiler, thus enter a Last Name in the Last Name field where it belongs.  I think that's absolutely per the Rules.
For instance, if screen credits show
Last Name // First Name
[...]
Wayne John
Gong Li
and so on

we should enter "Wayne" and "Gong", exactly as they appear on screen, in the Last Name field, because they are Last Names.

I agree with you...to a point.  Using your example, I would enter 'John Wayne' as 'John/ /Wayne (credited as Wayne John)' and 'Gong Li' as 'Li/ /Gong (credited as Gong Li)'.

It is the only way to be true to the name as well as the credits.

Schizzo:

With my expereience in dealing with the third paries as data sources...their reliability is questionable at best. By the same token the attitude that was taken by one member a few years back, "lave it to the exeperts" i completely unacceptable. Ithink the interests of the Community at large a far better served by ease of data entry as opposed to adherence to any cultural customs. So after thinking aboutit, I think the obvious answer is clear, the default is enter the data as you see it On Screen (Chow/Yun/Fat), that is easy for every user and requires no special knowledge on their part. Should the "experts" be able to provide documentation that it should be something other than the default, then they can provide that documentation in the ALIAS system and re-parse it accordingly.

This is basically the same position I have taken regarding double-barrelled last names. Without the hyphen, the name may or may not be double barrelled. So you start from the default and move from that point forward. This is easy to execute by each and every user anbd requires no specialized knowledge on their part.

Skip

Quoting skipnet50:

Quote:
Schizzo:

My alias is schizzzo 

Quote:
With my expereience in dealing with the third paries as data sources...their reliability is questionable at best.

Sad but true

Quote:
By the same token the attitude that was taken by one member a few years back, "lave it to the exeperts" i completely unacceptable. Ithink the interests of the Community at large a far better served by ease of data entry as opposed to adherence to any cultural customs.

I agree

Quote:
So after thinking aboutit, I think the obvious answer is clear, the default is enter the data as you see it On Screen (Chow/Yun/Fat), that is easy for every user and requires no special knowledge on their part. Should the "experts" be able to provide documentation that it should be something other than the default, then they can provide that documentation in the ALIAS system and re-parse it accordingly.

But there is one problem: We are building up a database of names with sorting, crosslinking and common names. That's more than a list of names that's on the screen. To get these functions work properly we need a correct online database. Dealing with names is more than dealing with data only.

Quote:
This is basically the same position I have taken regarding double-barrelled last names. Without the hyphen, the name may or may not be double barrelled. So you start from the default and move from that point forward. This is easy to execute by each and every user anbd requires no specialized knowledge on their part.

...and discussing and trying to find a common sense we can learn about names and parsing and can avoid some no votes.

You mean "Chow/Yun/Fat" is as correct as "Yun Fat/Chow (credit as Chow Yun Fat)". Using the CLT would end up in the common name Chow/Yun/Fat