Step 1: Go to Taraxacum Officinale taxon page
Step 2: Click on “Similar Species” (lower right)
Step 3: Wait forever and see the results never load :-)
Since I’ve started trying (about a week ago), I can’t get any results if I try globally or filter to include just the United States. Sometimes if I filter to just a specific state it will load, but not usually. It doesn’t seem to make any difference how many observations exist in the state, and sometimes a state that loaded earlier won’t later, or won’t load but upon a later attempt will. It also doesn’t seem to matter how long I sit and wait. I’ve tried many other species with more (and fewer) observations, across multiple geographic filters, and they all work great - just not Taraxacum officinale. I mentioned the issue here, and the issue seemed to be replicating with other folks.
I can replicate in Chrome and Firefox on Windows 10. I wonder if it is some kind of issue where most of the disagreed IDs are actually disagreements bumping it back to one of its own ancestors - like disagrees to Genus. And then it is getting confused or something similar?
Genus taraxacum and T. erythropspermum also are not working for me. T. ceratophorum is so it isn’t all of taraxacum.
May or may not be connected, but it looks like @jdmore created the taxon framework deviation for T. officinale this morning. I don’t see why that would cause this issue because I don’t think it would trigger a re-index?
Yes, this was done long after the problem was already being observed, and shouldn’t have any effect either way. More info in the current flag on the species.
Manually re-indexing the individual observations by checking and unchecking ‘cannot be improved’ seems to fix them. Section and Genus taraxacum are almost certainly the most common ‘mis-IDs’ for t. officinale, certainly more than any specific other species, so maybe trying to process those observations with their indices corrupted create some kind of paradox for the system? Or maybe the issue is just that the most common ‘mis-ID’ is the parent; can anyone think of another case of a large-ish taxa where that might be true?
The newest affected observation was added about 3-4 weeks before Section taraxacum was created in November 2019, so I’m guessing the indexing issues are some carry-over from that change.