Ginny mentioned the idea of categorization.
Roughly, there's two techniques:
1. machine categorization
1a) keyword-based
1b) more sophisticated models
2. manual categorization (aka labels)
2a) fixed category names
2b) flexible category names
then for search:
- use these as the FPXML category names.
- index the category names for keyword search
- provide restricts by category (must-have, must-not-have) in the API
- expose to consumers in the UI (and gadget?)
for v1, I recommend 1a followed by 2a, since we don't have the staffing for
anything more sophisticated. For the consumer UI, keep it simple e.g. add
as a set of restrict-links for each listing.
for the actual categories, I recommend names that:
- users want to search on but which aren't simple keywords
- are reasonably non-subjective (ok to say: when in doubt, tag it)
- can be seeded (started) with keywords, e.g. not completely abstract
concepts.
e.g. "fun" could be a category meaning that you'll have fun doing this
activity (e.g. playground build or reading to a child, not a suicide
hotline or blood donation), and we seed it with a bunch of keyword searches
and hand-tagging.
e.g. "skill building" could be a category meaning that you'll learn a
valuable skill (e.g. habitat for humanity and not soup kitchen), and we can
easily seed them with keywords on various skills. (though could be tricky
if the skills are pre-requisites)
Original issue reported on code.google.com by adam.sah on 30 Jun 2009 at 11:13
Original issue reported on code.google.com by
adam.sah
on 30 Jun 2009 at 11:13