owen2 / date2knight Goto Github PK

A dating service fundrasiser created for the Wartburg Computer Club.

PHP 70.39% JavaScript 29.61%

date2knight's Introduction

# Date 2 Knight

Date2Knight is an open-source matchmaking web application. It was originally created for the Wartburg Computer Club's fundraising activities. It works by comparing similarities between people based on a survey. If you are the curious math type, the algorithm is a n-dimension euclidean distance, the very same used by commercial dating sites. 

Feel free to fork, but please attribute.  :]

Original Version by: Owen Johnson in 2011

Math Parts by: Josh Osbeck

Idea to do a dating service: Dr. Zelle

Analysis of eHarmony Questions: Dr. Letsche

Contributors:
Owen Johnson
Heath Rost
Matt Phillips
Andrew Reisner
Jacob Hinrichsen
Nathan Stumme

(add your name if you contributed)

date2knight's People

Contributors

Stargazers

Watchers

Forkers

wartburgcomputerclub

date2knight's Issues

Participant Bio

It would be pretty cool if people could say nice things about themselves. That might make the results a lot more valuable... and a lot more fun.

Database Stuff

Hey so...the date2knight.sql has a bunch of differences between the actual queries. Is the live site using a different structure?

Add a config file to set the application title, polling dates, mysql database, and text fields like how to buy results, the results limit, the heart strata limits (currently local variables), and perhaps a static admin password (see auth issue)

Also any other things that should be customizable that you can think of.

The idea here is that people should only have to touch 1 file to make useful changes.

We can't close the poll

We should add a feature to automatically close the poll so that people who answer late don't change already printed results. Also, the dates the poll is open from should be configurable from the web.

Optional phone numbers

People provide garbage phone numbers, we either need to validate them or make them optional

report-all.php optimizatoin

It's kind of inefficient. Currently the page is generated by looping over all paid responders and generating the report for each.

Maybe convert this to a dp table so that the loop doesn't compare the same people multiple times.

Low priority. This is only important if the database gets significantly bigger.