Comment 2 for bug 1568035

> 500px web api and our 500px scope is like this. 500px has "streams" like "Editors", "Fresh today" etc. The scope displays these as departments. However, the 500px web api has no api to provide search results limited to a stream. Therefore when a user is in a department, for example "Fresh Today" and they enter a search string, the results are in fact not limited to Fresh Today but they are displayed in the Fresh Today department, which is not correct.

It sounds like the scope should be post-filtering the results then. Either that, or not use departments. I'm not sure the problem is with the scopes API as such here, but with the semantic conflict between the use of departments and query results?

I understand that post-filtering is sub-optimal, but I'm also not sure that adding another feature to the API is the correct answer.