Originally posted by: Traden4Alpha
QuoteI want a real-time PCA of the covariance of likes/dislikes for all Wilmott members!
Originally posted by: edouard
Originally posted by: Cuchulainn
QuoteT4A likes/dislikes the like/dislike?
Originally posted by: quartz
Originally posted by: rmax
Like and dislike button.
I like the like/dislike suggestion. And T4A does too, afair.
What about a fuzzy like in the range [0,1], e.g. I like the post 0.0001 or 0.999999?
Then use this as a basis for a MIS popularity system. Instead of saying poster XXY ...
The statistics concerning who likes/dislikes which message can be interesting
Quartz knows me well and Cuchulainn knows me better. I like/semi-dislike the like/dislike button concept. Like buttons are great but I've seen at least two social media systems polluted by troll-floods on the dislike system. A dislike button needs some tempering counterforce (e.g., limit one dislike per person per day, require N likes per dislike, dilute a person's dislikes so that their dislikes lose strength if they post too many)
This MIS is similar to a ManPower Control (MPC) for estimating, scheduling and monitoring the hours used in engineering projects, per project, department and divisions. Each worker is allocated so may hours per month per project. Ovverruns lead to escalation procedures. A similar system is disk allocation on expensive DEC disks.
So, here it's the same real-time Resource Allocation System where the resources the number of likes/dislikes. For reporting, a hot link to SAS or R is useful.
There are 6 main subsystems:
1. Data acquisition from Wilmott forum
2. Customer DB
3. Registration (cust + allocated stuff)
4. Monitoring and aggregation
5. WatchDog escalation system
Have written this twice (1) engineering companies (first on Apple II then miniKomputer; product survived 17 years LOL) and (2) disk allocation in big oil company.
It's all about resources.
I'm sure T4A and others would know all the requiremnents/use cases.