Quote:
Quoting Unicus69:

Quote:
Ken had decided to follow your compromise from page 7.  Help out the smaller regions, where there aren't a lot of contributors, while leaving the larger regions alone.  This is something I can certainly support and something everyone should be happy with.

Well said. And if certain users would stop voting on profiles they don't own, and instead, per Ken's comment, would "allow the voters who actually own the submitted locality to make the call", then there really is no problem whatsoever, IMHO, and we can all benefit from improving CLT results (as what we're talking about here is mostly replacing IMDb-mined junk with actual "as credited" data).

Quote:
For better or for worse, we have never blocked users from contributing to profiles they don't own, nor have we blocked users from voting on contributions for profiles they don't own.  In point of fact, the practice of voting on contributions for profiles users don't own has been going on for many years.

In these cases, no, it is not likely that the users' wishlist contents is an accurate protrayal of their intent to purchase.  However it is also the case that these users are some of the most careful and accurate voters. 

Similarly, the users who take it upon themselves to improve profiles that are not in their collection are some of the most accurate contributors.

For these reasons, we have chosen not to block contributions or voting in these cases.  I'm happy to reconsider this policy if the community feels it is necessary.  However, be advised that if a change is made, it will prevent both contributing and voting, not one or the other.  This is something I have considered in the past and have developed a decently secure method of preventing extra-collection contribution/voting.  I would prefer not to implement this change as I still feel it would be detrimental to the overall database.

To recap:
- We do not (currently) prevent users from contributing or voting on profiles they don't own.
- If you are contributing to a profile that you don't own, our only requirement is that the notes submitted accurately reflect the source of the data, and state the specific profile used as the source.

Clear as mud?

Quote:
Also for the record i do not favor blocking of users either. However, I will stand my ground against any user making wholesale changes, such as ALL 25 copies of Romancing the Stone across every Region, Locality and Version.

(***)

Quote:
Also for the record i do not favor blocking of users either. However, I will stand my ground against any user making wholesale changes, such as ALL 25 copies of Romancing the Stone across every Region, Locality and Version. As I explaioned, I tried this experiment over a year ago, and first got hammered by many of these same users for Contributing data to Profiles which I do not own, and further it took less than a week to uncover the first title which had variations in Cast or Crew data, LESS THAN A WEEK, at which time in the interest of the quality of the database and recognizing the ramifications I immediately terminated the experiment. While the intent is good, to try and straighten out the CLT, the FACT is it is not helpful as soon as one piece of errant data winds up in the database and skews the results.

It is not as rare as some would have us believe, there have been numerous findings in the last year and the fact that it took less than a week to find the first one belies the rarity, it may not be commonplace but even if it is 1% that is TOO MANY. I will also remind you all that I publicly announced what I was doing, and also included an explanation in m,y notes requesting users who vote to help by checking their ACTUAL cast and Crew lists and reporting any anomalies to me, nor did I EVER mask my Collection to hide what I was doing, and I never will.

I will always stand for I believe and know to be right.

Skip

Quote:
Quoting Dr Pavlov:

Quote:
Also for the record i do not favor blocking of users either. However, I will stand my ground against any user making wholesale changes, such as ALL 25 copies of Romancing the Stone across every Region, Locality and Version. As I explaioned, I tried this experiment over a year ago, and first got hammered by many of these same users for Contributing data to Profiles which I do not own, and further it took less than a week to uncover the first title which had variations in Cast or Crew data, LESS THAN A WEEK, at which time in the interest of the quality of the database and recognizing the ramifications I immediately terminated the experiment. While the intent is good, to try and straighten out the CLT, the FACT is it is not helpful as soon as one piece of errant data winds up in the database and skews the results.

It is not as rare as some would have us believe, there have been numerous findings in the last year and the fact that it took less than a week to find the first one belies the rarity, it may not be commonplace but even if it is 1% that is TOO MANY. I will also remind you all that I publicly announced what I was doing, and also included an explanation in m,y notes requesting users who vote to help by checking their ACTUAL cast and Crew lists and reporting any anomalies to me, nor did I EVER mask my Collection to hide what I was doing, and I never will.

I will always stand for I believe and know to be right.

Skip

The thing is: if while making such contributions you limit yourself to profiles with "blank or limited cast info" (quote from Ken Cole) - which I would also assume to include IMDb-mined data - the net effect of such contributions (if approved) would still be an overall increased quality of the database (and the CLT results), even if 1% is wrong like you say. This is typically a situation where "the best" can be the enemy of "something better". And whereas of course you are completely entitled to maintain your own standards for your database, the general interest of the Invelos userbase at large might be better served with the approach Ken has outlined.