interestingness - how to impliment it in a db

whats the best system for storing an items interestingness?

[proper_bo]

There is also a php discussion about this here:
[webmasterworld.com...]

Flickr use interestingness to rate images.
It could be used to rate pretty much anything.

What I am after is suggestions on how to impliment interestingness on the database side.

Do you just add it as a row to an item table or should it be seperated into its own table tables?

How would you go about organising those tables?

Thanks.

[aspdaddy]

First task is to define interestingness, what it means and how its calculated. Once you know this youcan design it.

[proper_bo]

I have defined what I think interestingness is in the other thread (php).

As for database design I think it could be done with just one extra column for each row called interestingness. All other changes and calculations could be made using php.

[aspdaddy]

Hi, Sorry I didnt see the other post.
That definition will be quite tough to implement unless you have a good understanding of discreet mathematics. It uses formal notation and set theory to define keyword distribution over time.

Personally I dont think it was meant to be taken too seriously. But if you are intent on doing it then simply log a row for each keyword along with the date /time it occurs. They are the only database requirements the rest is an algorithm to process those rows.

As for database design I think it could be done with just one extra column for each row called interestingness

I dont think so, the value changes over time and is relative to all data collected, so it has to be calculated for any specific interval of time, and requires analyssi of all the data.

[proper_bo]

"log a row for each keyword"

Could you explain more what you mean by this please?
Do you have any idea how flickr implement interestingness in terms of databases and code?

[mattur]

1. This thread conclusively demonstrates why starting duplicate threads is sub-optimal.

2. Just add a column to your table, do your calculations periodically and update the column. Experiment with the calculation and see what works best. Job done. :)