Quoting Merrik:

Quote:

This is all we have. We have to work with it.

Nobody is obliged to correct a profile that had been entered per the rules. You want an easier way to replace good data by fictitious data, and I think it is a bad thing. The more complicated it will be to ruin the database, the best it will be for final users (people that download data and want correct one).

I agree with the need to correct common names for parsing problems. Unfortunately, a lot of common names threads are about accentuation, and this fact justifies not to make them easier.

I got derailed again. So I'll ask again so it's fresh and keeping the thread on track. Ken, since you poked your head in here, is there actually any chance that a forum like this could see the light of day? Maybe a timeline? Any forum names suggestions jump out at you?

Quoting surfeur51:

Quote:
... But if I' had not locked that profile, that I own, you would have destroyed all the linking for that actor in my local.
...

Sorry for disturbing, but...

For other users that use a common name, how we have it now and how it is clarified, this would improve their database in linkin issue!

So the question is how much do the linkin after the current clarifications? And how much do it similar to you? So we could find the way which is for the most users better.

Quoting VirusPil:

Quote:

So the question is how much do the linkin after the current clarifications?

I think it depends of the structure of collections. For people who have many latin languages movies, or scandinavian ones, with actors with accented names, the problem of linking is much more important than for people who have mainly English language movies, with actors where accents are more rare.

Quoting Taro:

Quote:
A brainstorming session to find a solution for this issue would be ini order, I think

To add a little more to the common name discussion, I shall try to explain the most clearly possible why accented names are so  problematic :

In the following theorical (and fictitious) examples, we suppose everything is perfect : contributors contribute with Invelos rules, no IMDb mined data:

Example 1

BRIAN T FORD on screen in movie A introduced in the database in 2002 as Brian/T/Ford
BRIAN T FORD on screen in movie B introduced in the database in 2007 as Brian/T/Ford
BRIAN FORD on screen in movie C introduced in the database in 2009 as Brian/T/Ford (credited as Brian Ford)

Common name concept works, and Brian T Ford wins as most credited form.

Example 2
ANDRE FRANCOIS on screen in movie A introduced in the database in 2002 as André François (correct before Ken's "Clarification")
ANDRE FRANCOIS on screen in movie B introduced in the database in 2007 as André François (correct before Ken's "Clarification")
ANDRE FRANCOIS on screen in movie C introduced in the database in 2009 as Andre Francois (correct after Ken's "Clarification"), without any "credited as" name, so without any linking with previous titles.

Common name concept no more works, since data that was correct for Intervocative in 2002, correct for Invelos in 2007, is no more correct for Invelos after March 2008. Unfortunately, this change affects  most of titles since the majority of profiles were contributed before Ken's clarification, not speaking of Blu-ray profiles that were based on old DVD accepted data. So linking of local databases, specially for people who own many no hollywood movies, is ruined by people who correct old profiles. This is a very bad thing for everybody..

My contradictors twist my position saying that I am against rules. I'm not against rules in general, I am against rules that do not allow to build a database which works as a database, with linking, sorting, filtering functions.

The OP's request will allow to treat a little better example 1 when we got IMDb data, but will increase the mess in accented names, which are most of linking problems for some collections (mine is an example...). That is why I'm totally against it.

Quoting Addicted2DVD:

Quote:
In my eyes it is a problem that said older profiles and such were not corrected per his clarification.

This is simply due to the fact that most people prefer to put in their new profiles for their local the real form of the name, instead of :

1/ change in their local good data with fictitious data
2/ contribute a change of the profile per new clarification,
3/ change back in local to restore old correct data
4/ lock their profile to avoid to be polluted by their own contribution.

I assume that most people want to have in their local data about actors that really played in the movie, and not about actors who never existed.

But that is not a problem of the linking system or Ken's decisions. In my eyes that is a problem of personal decisions. And they are welcome to them... but when it comes to the online it must be per Ken's decisions. Just like I don't personally agree with Ken's decision to allow people to update profiles for discs they do not own. But it is what it is. If that is what he wants... so be it. I personally will go with making things be done the easiest way possible to give Ken what he stated he wants any time. Just like I would for any decision for change he decides to make.

But either way... as long as this is what Ken wants (most commonly credited version of the name) I will fully support a new forum to make it easier to give him what he stated he wants.

You paid for a license to use the program. As for the online database... that belongs to invelos... and as such it should be as they want it to be. As it even says in the rules...

Quote:
If you wish to save different information in your local profiles, you are free to do so in your local database, but do not contribute your information. The main database is standardized so that all profiles follow these rules. DVD Profiler allows you to lock your data so that it is not overwritten by updates from the main database.

As I said... whether I agree with his decisions for the main database don't matter. But it definitely is his as he sees fit.

You expect to have what you want.
I expect to have what I want.
Every other user expects to have what they want.

Guess what... it is impossible to give everyone what they want! So Ken, as the developer, has to make a decision on how to make it. Sometimes we will agree... sometimes we will not agree. Such is life.