annotations seen by badge but not sidebar at http://www.jneurosci.org/content/36/42/10908.long

### Steps to reproduce
1. http://www.jneurosci.org/content/36/42/10908.long

### Expected behaviour
41 annotations anchor, matching the 41 reported in the badge

### Actual behaviour
1 annotation anchors

### User report

"At http://www.jneurosci.org/content/36/42/10908.long it says there are 41 annotations, but I see 1. The orphan tab does not show up and any new scibot run does not read data. Also:
http://www.jneurosci.org/content/37/1/23.long
http://www.jneurosci.org/content/36/42/10853.long"

### Observations

#### client

https://hypothes.is/api/badge?uri=http%3A%2F%2Fwww.jneurosci.org%2Fcontent%2F36%2F42%2F10908.long -> 41 annotations

https://hypothes.is/api/search?_separate_replies=true&group=__world__&limit=200&offset=0&order=asc&sort=created&uri=http%3A%2F%2Fwww.jneurosci.org%2Fcontent%2F36%2F42%2F10908 -> 0 annotations

#### activity pages

https://hypothes.is/search?q=uri%3Ahttp%3A%2F%2Fwww.jneurosci.org%2Fcontent%2F36%2F42%2F10908.long -> two cards, one with 1 annotation, the other with 40 annotations

https://hypothes.is/search?q=uri%3Ahttp%3A%2F%2Fwww.jneurosci.org%2Fcontent%2F36%2F42%2F10908 -> 1 card, 1 annotation

I've been wondering about this split display, see it from time to time and haven't nailed an understanding of what it is. But it seems wrong. If the query unites equivalences the display should too. Otherwise it raises questions that the user -- or even I -- cannot answer.

#### http vs https ?

Not sure if relevant but discovered this which doesn't smell right.

https://hypothes.is/search?q=uri%3Ahttp%3A%2F%2Fwww.jneurosci.org%2Fcontent%2F36%2F42%2F10908 -> 1

https://hypothes.is/search?q=uri%3Ahttps%3A%2F%2Fwww.jneurosci.org%2Fcontent%2F36%2F42%2F10908 -> 41

### Other

Filing here vs `h` or `client` or even `extension` because it is a boundary-crosser.

Start by reproducing the listed jneurosci URLs and comparing the badge, sidebar, activity-page, and search API results for the .long and non-.long URIs. The issue is done when equivalent annotations are consistently represented in the sidebar and activity views, with matching counts and the orphan tab behaving consistently.

Written by the indexing model from the issue text.