Tag Info

Hot answers tagged

4

Actually, I think I figured out a way to do this. If you specify the following: /users?filter=john&sort=name&min=john&max=JOHN That is, sort by name with "min" and "max" both set to "john" then it returns only those people whose name is exactly John. I wonder whether this efficient for the backend to process? It seems to respond pretty ...


3

The API allows you to get question data based on ID, so since all forms of question URLs for Stack Exchange sites have an ID in them, you can pull that value out and pass it to the /questions/{ids} route. Likewise, if you don't know the specific site in advance, you can pull out the hostname and pass that in dynamically. As an example, I parse out similar ...


3

In order to access the body of a post, you need to create a filter that includes this information. You create a filter using the /filters/create method: http://api.stackexchange.com/2.0/filters/create?include=question.body;answer.body The response from that URL will look something like this: { "items": [{ "filter":"!9Tk5izFWA", ... } As you ...


3

Yes, maybe. for post score and user rep, there are api methods that will give you the results you want. For data points that are not covered by the sort param, you would need to build a dataset of users and then filter that. Data points such as up_vote_count are definitely not going to be/cannot be indexed by a search engine. I have a service that will be ...


2

No, you can't do it because py-stackexchange is a library based on SE API that does not provide that kind of search. You should use Google API search instead.


2

The body of a post is optionally returned on all methods that return "posts." /questions, /questions/{id}/answers, /users/{id}/questions, /answers/{id}, etc. all return the same "post object" I guess you'd say. The same code can be used to parse the post subset of fields, anyway. Kind of complicated, unfortunately. However, since /search is so expensive ...


2

This is [by-design]. /search is already pretty resource intensive, and not returning answers is a conscious effort to reduce its runtime. The answers parameter does not appear in the documentation for /search accordingly.


2

Running a /search is quite expensive, so we do cap the returns at 2000. Note that this limit is not contractual, and subject to change (it has been pretty stable for a while, but we're seeing thousands of new posts a day... we may encounter a tipping point in the future). In this case, if you want all questions tagged matlab this is a better query. If ...


2

Instead of linking to a .tar.gz archive, don't you think it's more practical to link to the raw file instead so it can be installed immediately? Click here to install the script It seems more logical to me. Also, there is a small problem that you can add tags to your search query multiple times. If a tag is already in the search query, it should not be ...


2

migrated is equivalent to searching with migrated:1 or migrated:0 on the site itself. In other words, migrated=true returns questions that have migrated_to (questions that have been migrated away from the site they were originally asked on). migrated=false returns questions that don't have migrated_to, but may have migrated_from. There was a bug (fixed in ...


2

This has been fixed in the latest deploy (it also affected body turns out). We've got some changes to our search infrastructure in the pipeline, and API v2.1 is being used to test them out. You might have noticed it's had some... issues. Better to find them in an API beta than after the rollout to the Q&A sites though.


1

Looks like no data from May 2013 onwards: http://data.stackexchange.com/stackoverflow/query/154032/phonegap-posts-by-month When I search for the phonegap tag on SO: ...and click the button I get taken to questions tagged cordova: I suspect the tags have been merged?


1

fromdate and todate were being applied in the wrong part of the pipe for /search and /similar. This has been fixed. Do be aware that fromdate and todate always apply to creation_date. If you're looking to apply limits to other sorts, you need to use min and max.


1

This is more of a documentation bug. It'd be kind of crazy to return all questions not tagged say, test. It makes a great deal more sense to get questions tagged c# but not tagged something, for example. The documentation has been updated (as has the under constrained search error message, which was misleading/incorrect). Note that for backward's ...



Only top voted, non community-wiki answers of a minimum length are eligible