Explore page - Mysteriously Search produces erroneous number of hits - far fewer

[Andrew-Clement]

A search on KronK produces only 2 hits, when according to COlins data, KronK submitted 1949 routes,

The most recent of these is TR 253902. But a search on presumably the previous route, 253900, gives a null result:

[agamba]

Keep in mind that when searching by a specific TRid you need to use the option "does contain"

[colinmccann]

Semi-duplicate of https://github.com/ixmaps/website/issues/8

Suggest we are also flexible on Traceroute Id (eg allow Originate in). Less important, since tr id is mostly an internal thing, non-ixmaps users won't be using it...

[Andrew-Clement]

Thanks, But the original problem persists. As I suspect, TR 253900 was contributed by KronK, but it doesn't show up with a search on KronK, which produces only 2 hits neither TR 253900

Traceroute details: ID 253900 created on 2016-03-10 06:07:50-05
Origin: Submitted by KronK from S6H 6J5 Destination: galleriadallas.com [146.20.39.10]

PS Aside: Perhaps for queries when Originated, Terminated, Goes Via.. are not relevant, it shouldn't matter what which is mentioned??

[colinmccann]

Screenshots for both Kronk issues:

I get both to work on my end...

[agamba]

Remind that when we are not showing all the TRs when a search is done, but only a sample, so that is the reason why some TR will never be found. This brings the an old idea we had at some point and is to add a functionality that allows the use to browse though TRs.

[Andrew-Clement]

Yes, I realize that only a sample is shown.

Using Does Contain instead of Originate in, I get the same result as you both just report - 1949 routes.

However, Why do I get just 2 routes when using 'Originate in'?? This seems quite odd.

Also, 'Originate in' seems intuitively clearer than 'Does Contain'.