It's quite easy really: if some users don't like my contribution I try to adjust my notes or contribution to fulfill their wishes if possible, if not I withdraw my contribution and I'll keep the changes to myself. After all I'm trying to help others not to please myself.

Quoting Dr Pavlov:

Quote:
If that was the intended question, it may not e implemented because i suspect we have to start from scratch. I can't think of anyway it could be implemented from where we are right noiw.

Skip

If that can't be implemented, then let's think of something else 

Now we have the Credited As system, so we have to live with it, like it or not.

The problem is, the system doesn't work very well. Why? Because it's too complex too handle, especially for names with many slightly different variants.


What could be done, IMHO, is make the system somehow easier, like Ken did with the ", Jr." filter.

That filter returns a standardized name, but not necessarily the "most frequently credited" name.
Even if a "John Smith jr" was credited this way in ALL his movies and even if he was NEVER credited as "John Smith, Jr.", still we would use "John Smith, Jr." as his Common Name, because of the filter.
It wouldn't be "correct" according to RHo's definition ("a correct name would be one which is used in at least one credit. ..."), still it is very useful, because it LINKS, while the Credited Name stays as it is in the Credited As field. So, we have both accurate credits AND linking.
That's the reason why I say to filter "Penélope Cruz" to a standardized "Penelope Cruz" as Common Name (while the Credited name stays as it is on screen). It's not "correct", but it works, and it is still accurate in the Credited As field.
That way, all her credits would link (and still be accurate). Now they don't.

Quoting Dr Pavlov:

Quote:
I didn't say it couldn't be, Enry. I would implement it anyway and just start over, but whether Ken will or not, I don't know.

Skip

I hear you. But starting over would be a big deal! 

Agreed, but the end result would be far superior, which is why I would implement it.

Skip

Quoting EnryWiki:

Quote:
It wouldn't be "correct" according to RHo's definition ("a correct name would be one which is used in at least one credit. ..."), still it is very useful, because it LINKS, while the Credited Name stays as it is in the Credited As field. So, we have both accurate credits AND linking.

If Invelos goes that route and doesn't use the common name for a "correct name variant" but emphasises on the linking part, I'd like them to change the three name fields, which have another meaning than linking only, to a single linking name field. In that case I would not mind to loose any accents, cripple umlauts to single letter ASCII, and order the family name part and given name part in any arbitrary order.

Until then the three fields (first name, middle name, last name) have their own meaning other than linking only.

Quoting EnryWiki:

Quote:
Quoting Unicus69:

Quote:

[...cut...]
The problem with our current system is that it relies on someone knowing that there is a different name floating around out there.  If, by whatever miracle, that person finds out there is a different version out there, they have to...

document that the names do, in fact, refer to the same person.

check the CLT results to find the most commonly credited form.

check to make sure that the CLT results are correct.

I am sorry, but the average user isn't going to jump through those hoops.

Exactly. But I daresay that even the "above average" user will not do that for each and every cast or crew member. If they don't check glamorous Penelope, whether there is a "Penélope" floating around out there or there is not..., will they be keener when it comes to some more obscure actor? Hmmm...

I agree, if i do work on a DVD i check the credits and match them with the profile. The only time i can come up with a common name is if i either have both variants in my local DB, if it's a new profile, i type in the name and see multiple version, leading me to do the needed researched to find a common name or i use the CLT. Or if the incorrect name is used in the profile and i check if i need to use a common name.

You can't expect people to check every name to see if there a multiple versions, espacially for a old profile you're just correcting, plus if you don't own different movies with multiple names for the same person you can't even discover the need for a common name using your local DB.

I now using the CLT i still have about 2500 name variant which may or may not need o be linked, if i do a profile i use the clt and sometimes find common names, also seeing other updates comming through using common names i try to link them locally but some people need to work as well (5 days a week, up at 6 back home at 20.30 (including travel) so i only check profiles on my day off and i also like to WATCH an occasional movie and play on my PS3, wher do i get the time,

Paul

Quoting EnryWiki:

Quote:
Quoting Dr Pavlov:

Quote:
Agreed, but the end result would be far superior, which is why I would implement it.

Skip

I would be cool with that, but still I don't get how you would implement it, even after starting over.
How would the program know that NameA=NameB=NameC-NameD ?

That's a technical database issue that poses absolutely no problem whatsoever in a relational database like the one used in DVDprofiler.

This is done by implementing:
-  table, alias_master with a field "master name code" (also the unique primary key for this table).
- table alias_name with the fields "master name code" and field "alias_name". Primary unique key would be the combinations of these two fields.

One record in the alias_master tabel  links to any number (>= 1) of alias records.

Only thing that needs to be addressed at that point is which alias_name record is to be displayed. For this, the most credited variant would be the obvious choice. A field would need to be added to the alias_name tabel to store if that record is the variant to be displayed. An easier option would be to always display the first recorded alias name or first in alpnhabetic order.

We don't have to start from scratch: for a lot of actors and crew we already have this information. all we need to do is define a record in the alias_master table for these actors and all their credited variants in the alias_name table. This can be automated without too much trouble.