[atlas] API (v1) querying probes--does stats_name field count and possibility of negative selection

Dear list,

I encountered some unexpected results when selecting probes with status_name filed. An example is given below:
https://atlas.ripe.net/api/v1/probe/?country_code=BG&tags=system-v3,datacentre&is_public=true&status_name=Abandoned <https://atlas.ripe.net/api/v1/probe/?country_code=BG&tags=system-v3,datacentre&is_public=true&status_name=Abandoned>

8 results were returned containing probes that are abandoned, as well disconnected and connected.

To nail down the problematic field, I tried following queries:
https://atlas.ripe.net/api/v1/probe/?status_name=Connected
https://atlas.ripe.net/api/v1/probe/?status_name=Abandoned
https://atlas.ripe.net/api/v1/probe/?status_name=Disconnected
https://atlas.ripe.net/api/v1/probe/?status_name=Haha

Exactly same number of probes, 16889, are return with each of these quests, which makes me wonder whether the status_name filed is actually taken into consideration?

One other issue, is to negatively select probes according to some fields, especially tags filed, for example, probes do not contain home tag.
I’d like to know if such selection logic is supported by v1 API? If yes, how to compose the query? If not, would it be considered in v2 API?

A bunch of thanks in advance.

Regards,
Wenqin
Telecom ParisTech


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20160128/79469951/attachment.html>