Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Tweets when specify and not specify "type" in search query #19

Open
GoogleCodeExporter opened this issue Nov 22, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Search for query 
"http://otter.topsy.com/search.json?q=vodafone&mintime=1324385400&maxtime=132438
7203&order=date&perpage=100" and 
http://otter.topsy.com/search.json?q=vodafone&type=tweet&mintime=1324385400&maxt
ime=1324387203&order=date&perpage=100
2. In the second query &type=tweet is added
3.

What is the expected output? What do you see instead?
By specifying "type" we are getting more results and also there are tweets 
which are present in first and not in second as well as tweets present in 
second and not in first (and count of such tweets are high)

What version of the product are you using? On what operating system?


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 21 Dec 2011 at 6:09

@GoogleCodeExporter
Copy link
Author

This is the confusing part of the api. "search.json" always retrieves search 
results in quality ranked order. What "order=date" does is to re-sort top N 
results in reverse chronology order. 

When you modified search criterion "type" parameter, the top N result set 
changed. 

For details, please reference 
http://code.google.com/p/otterapi/wiki/Resources#/searchdate

Original comment by [email protected] on 21 Dec 2011 at 5:37

@GoogleCodeExporter
Copy link
Author

Thanks for the reply.

Two things which i want to ask is that : 
1. I asked for search.json not searchdate.json
2. What is N, if it is some page size , how come total no. of results change

Original comment by [email protected] on 22 Dec 2011 at 4:53

@GoogleCodeExporter
Copy link
Author

1) search.json?order=date is the same as searchdate.json
2) N is the depth of the quality rank pass, by default it is 100.  For example, 
for a search that can return 2000 results, when order=date or searchdate.json 
is specified, it will compute the top 100 best results then return them in 
revers chronology order. It will only return upto 100 results. N can be 
controlled by "zoom" parameter, which has been described in 'searchdate' 
section. 

"order=date" and searchdate.json are for use cases such as "give me recent good 
results for 'ipod'". It is NOT the appropriate tool for downloading all tweets 
that contain term 'ipod'. 

Original comment by [email protected] on 22 Dec 2011 at 5:20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant