Quote:
... Most DVDP users just read the credits on screen and write them down.  That's our weakness, but also our strength.

Quote:
...
If I understand correctly what you explained, that means that we couldn't just contribute credits any more without determining the person (unique identifier) they actually  belong to. That's what IMDb does.....

Quote:
Quoting madacid:

Quote:

first of all, you just contribute the "credited as". in your case "Johnny Smith". If you also know/idintify the person say in addition: this entry belongs to a person in the database (e.g. linked to [ID:John Smith]. That's all.
The users now can check your contribution and vote. If the "majority" agree the link will be set to the online-profile.

Let's say user Mary Doe likes a movie very much and she wants to contribute the credits to the main database of DVD Profiler.
Now she can, can't he? She writes down the names she sees on screen and that's it. Maybe it's not 100% Rules-complaint (because she didn't check all common names) but I bet her contribution gets approved most times.
With your IMDb-like system, she should have to find out if that "Johnny Smith" credit on screen is actually for actor 1, 2 or 3, and document each choice of hers. Maybe she will, or maybe she won't and make random choices, or maybe she will just stop contributing.

Quote:

if we would have the ability just contribution "as credited" data, this would make you argument to a strength. but this isn't so, so it's just a weakness

Quote:
Quoting madacid:

Quote:
a simple relation-connetion in a database as content of a lawsuit...LOL
There are just a few steps from caution to paranoia, skip.
Amazon will not lift a finger for how invelos build it's own database, apart from copying their data.

Ever hear of the concept of intellectual property, mad. You might be right and so might I. I am conservative, I'll take the clearly safest approach...everytime.

Oh, I see the Profiler Nazis are working overtime.

Skip

Quote:
Better safe than sorry, midnit. I would not be willing to risk it. I would find another answer, or a modified version of the technique. And from waht I see that is the approach that Ken appears to be taking, wisely so. There are many different ways to achieve the same exact objective without risk.


You and others are basically saying oh it's perfectly Ok. I am taking a very conservative and safe approach. The other Db's parent will file a suit if you loo at them cross-eyed, there is only one other company that I know of that is as litigious but that companies approach is not predatory, it is to protect their intellectual property ONLY. They don't want to put you out of business or take you over, they simply want you to stop using their intellectual property without their permission.

The conservative approach is far and away the BEST approach.

Skip

Quote:
Yeah right, James. You can set up your keys any number of different way, Numeric, Alpha, Alpha numeric, etc.etc. etc. All you are doing is convincing me that you have little or no experience in the world of BUSINESS, let alone relational databases. There si not one SINGLE method that will do the job, that is what you don't GET. IF there was only ONE way to do this, James you would be right but you aren't.

Now would you care to explain why I am not allowed to comment without being put down by a bunch of amateurs. You egg me on and egg me on and finally when i have had enough i will bite.

Skip