+ All Categories
Home > Documents > Project Presentation. Traditional search engine flaws In many situations user only need the most...

Project Presentation. Traditional search engine flaws In many situations user only need the most...

Date post: 17-Jan-2016
Category:
Upload: donald-montgomery
View: 213 times
Download: 0 times
Share this document with a friend
14
Project Presentation
Transcript
Page 1: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Project Presentation

Page 2: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Traditional search engine flaws•In

many situations user only need the most popular or authoritative result

Too much informatio

n

•User has to go through dozens of links to get what he/she needs

No direct result

•The responsibility of determine if the information is “Good” or “Bad” is left to the user

Sometimes confusing

Page 3: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

SmartSearch system features•Dire

ct interaction with search results in the result page

Immediate result

•Try to decide what kind of information the user is pursuing

In best possible

order

•Page appearance varies according to query string and user preference(to be implemented)

Personalized interface

Page 4: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

System Interface - home

Page 5: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

System Interface – result page

Ebay results

Google map result

Youtube result

Indeed results

Page 6: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Search results comparision

Page 7: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Results ordering and parsing

Search results for “modern warfare 2”

Search results for “baby panda”

Page 8: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Search results for “Java developer”

Search results for “West 114 Street,NY”

Page 9: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

System architecture

Query Page Processi ng Servl et Resul t Page

Youtube API Ebay API Googl e API I ndeed API

Page 10: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

GoogleMap API1.Query google map api

with url containing query

2.Check if status field in responding XML feed is “OK”

3.If true, create Geocoder in result page using javascript and translate address into coordinates, center map and open info window

http://maps.google.com/maps/api/geocode/xml?address=address&sensor=true

Page 11: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Youtube API1. Import Gdata java

client API library2.Create

YoutubeService and YoutubeQuery, set query keyword

3.Get videofeed and total results using methods provided by the library

Page 12: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Ebay and Indeed API

Query URL XML feed XML arraylist

http://api.indeed.com/ads/apisearch?publisher=8663439946059063&q=java+developer&sort=&radius=&st=&jt=&start=&limit=&fromage=&filter=&latlong=1&co=us&chnl=

Page 13: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Results ordering scheme1.Collect total hits of

query string from each search API

2.Sort these hits, and parse the rank to result page

3.The result order is then determined by the total hit number of each search API

Page 14: Project Presentation. Traditional search engine flaws In many situations user only need the most popular or authoritative result Too much information.

Thank you!


Recommended