As a locker owner, I want to be able to view useful results in my search output
Searching across types:
- When search results contain the following types, they should display summary information:
- Tweets: Tweet text, who tweeted it, when it was tweeted - click to see original tweet on twitter.com
- Contacts: Contact name, photo, email
- Photos: Photo thumbnail, caption, title - click to see large version of photo
- Search results are easily recognizable by type and by source
- http://busterbenson.com/home/search?sort=&q=kitty
- Apple's Spotlight (for category-based ranking)
- Determine HTTP endpoints to query in order to retrieve specific records based on _id. Determine this for the following types: the Twitter connector/synclet, the contacts collection, and the photos collection
- Write code that lives in the Search Collection, that groups and culls the search resultset into the sort order of CATEGORY->LUCENE SCORE
- Write code that lives in the Search Collection, that receives a search resultset (array) of _ids, and retrieves the JSON representation of that record from the HTTP endpoints determined in the step above.
- Write front-end code in the Apps/Search app, to display the resulting array of JSON text per the wireframe above.
- DECIDED NO: If we begin to go down the "viewlet" route for showing small representations of various types, should we settle on a particular templating framework?
Hard to define how we'll know what acceptance test or tests to use to confirm this story is done. The best I can come up with is that a locker owner can find it possible to find any piece of data within their locker, and to view the result in a simple, understandable manner. Admittedly, there are a ton of subjective concepts in the previous sentence, so what may be acceptable to one may not be to another. Not sure how to handle this.
- Drop the idea of viewlets for now
- On homepage, place search box at top, but leave other info on homepage
- Add "no results" page support
- Get design completed from Shawn/Tom before starting
- Photos aren't supported yet as there's a story in progress on them. (Jer is adding some field support). Happy to follow up to ensure photos are also included once that story is done.
- Upon brand new Me/ directory, indexing could potentially take a long time (as we shove thousands of records to index immediately). Querying will be blocked while indexing. We may want to make these two separate processes (but will have to watch for simultaneous Clucene Indexreader/writer).
- We changed up some indexing fields, so your historical data won't be indexed, only new stuff. (no longer an issue with clearing the world)
- No ability to click on the results yet to go anywhere. Viewers aren't ready?
- HTML matches Wireframes (very roughly)
- Browser support
- Chrome (latest stable)
- Firefox (latest stable)
- Safari (latest stable)
- Photos on hold
- CONDITIONAL: Tests completed by Eric
- Requires clucene 0.1.1
- How do we want to handle date? Timezones are different for everyone. "19 hours ago" doesn't make a lot of sense unless we're clever with browser-side timezones. Thoughts?
- Story to allow people to reindex their entire Me directory from the dashboard
- Inconsistent service type names make search fragile