Mozillians/Phonebook/Search: Difference between revisions

Mozillians/Phonebook/Search (view source)

Revision as of 15:56, 1 May 2012

78 bytes added , 1 May 2012

→‎Controlled Vocabulary Search

Adesai

Confirmed users

6,300

edits

@@ Line 10: / Line 10: @@
 == Controlled Vocabulary Search ==
-=== Scenario ===
+Mozillians as a phonebook app is awesome for searching names, but what will it do if other types of information are being put in?
-* You’re a user who had just been vouched
+Think of this scenario as a user: you've just been vouched; you do want to help make Mozilla's products better and just don't know where to start looking; you don't know the internal lingo used within Mozilla. So, the first thing you'll do is punch in "Firefox" into the search because its Mozilla's most well-known product, or use a generic term, like "websites". What would appear in the search result? Would it solve the user’s problem of knowing where to look? Would it make him use Mozillians effectively?
-* You ''do'' want to help make Firefox better, you just don’t know where to start looking
-* More specifically, you don’t know the internal lingo used within Mozilla (after all, you’re a volunteer rather than a staff!)
-* So you punch “Firefox” into the search bar because it’s Mozilla’s most well-known product, or use a generic term, like “websites”
-What would appear in the search result? Would it solve the user’s problem of knowing where to look? Would it make him use Mozillians effectively?
+To clarify, '''groups, skills, locations and other metadata''' are not people’s name and is a standard user need in regards to search and finding other Mozillians. They should be visually distinct. To do this, the will make group and metadata search easier to perform, and '''discourage “free-text” search''' on things that are not names. Everything we will do in search—all of the features described below—are designed to address this problem.
-Everything we will do in search—all of the features described below—are designed to address this problem.
+=== AutoComplete ===
-=== Design Principles ===
+Autocomplete will easily allow users to search for names, groups, skills, locations and other metadata. It reduces a lot of burden on the user to be smart about their choices on search and provide a large amount of information and value in return. [https://bug737484.bugzilla.mozilla.org/attachment.cgi?id=610454 Here’s a visual representation of how autocomplete will work to handle partial matches and metadata entries]. This is done in two ways:
-* Mozillians as a phonebook app is awesome for searching names, but what will it do if other types of informations are being put in?
+# A synonyms list for the same, so when people use common terms to search for things, we can direct them to groups that relate to that term. [https://docs.google.com/spreadsheet/ccc?key=0AkYz4ya3vpPfdGE3TjRGM3Bmb1BYZ21LcnlrREMyc3c Here’s the start of a synonyms list]
-* Clarify that '''groups, locations and other metadata''' are not people’s name by making it visually distinct in the search box
+# Correlating metadata for groups and people to these results. For example, if someone searches for "http://support.mozilla.org", they'll receive an autocomplete dropdown result for the "Support" group as that is listed in its "website" field.
-* Make group and metadata search easier to perform, and '''discourage “free-text” search''' on things that are not names. Why?
-** Search may come up empty or with results that are not useful
-** Users might think that our search engine is broken
-** And, by extension, if the search engine is broken, the site itself is broken
-There are two parts that we have to have for this to happen:
+=== Tag Tips ===
-# From the dev-side, we’ll need to build the autocomplete functionality itself. [https://bug737484.bugzilla.mozilla.org/attachment.cgi?id=610454 Here’s a visual representation of how autocomplete will work to handle partial matches and metadata entries]
-# From the content side, we’ll need to have:
+To increase discoverability of groups, skills and locations, and reduce the need for users to go through the search field for every query, the Mozillians Phonebook will offer "Tag Tips" on the hover of tags within search results. We're looking for simple metadata (i.e. description, steward and # of members) within these tips. [http://stackoverflow.com/questions/tagged/c%23 StackOverflow has a great example of how a tag and a definition appear next to each other].
-## A definition list for all most-used groups. It will populate the search result and appear below the group name. [http://stackoverflow.com/questions/tagged/c%23 StackOverflow has a great example of how a tag and a definition appear next to each other]
-## A synonyms list for the same, so when people use common terms to search for things, we can direct them to groups that relate to that term. [https://docs.google.com/spreadsheet/ccc?key=0AkYz4ya3vpPfdGE3TjRGM3Bmb1BYZ21LcnlrREMyc3c Here’s the start of a synonyms list]
-## Other meta information associated with that group: IRC channel, website, wiki and name of community stewards. For example, here are the info for SUMO:
-### IRC channel: #sumo
-### Website: http://support.mozilla.org
-### Community steward: Michelle Luna
-### Wiki: http://wiki.mozilla.org/support
 == States ==