The matching algorithm initially wrote for this Hackathon is a bit rough. This task is blocked on the addition of organization_needs, but once that is done we should query not using LIKE rather some smarter logic, along with (maybe) built in Postgres geolocation logic.
Also we should probably come back with something as a default. No match isn't helpful, even if there's no perfect match
jbyman
commented
4 years ago
The matching algorithm initially wrote for this Hackathon is a bit rough. This task is blocked on the addition of
organization_needs, but once that is done we should query not usingLIKErather some smarter logic, along with (maybe) built in Postgres geolocation logic.Also we should probably come back with something as a default. No match isn't helpful, even if there's no perfect match