I don’t have a location filter, but I think I must be overlooking something because there is one RG observation of C. g. percivali, but the taxon page for C. guereza shows 0.
Does anyone see something I’m missing?
looks like a taxon change on C. guereza just happened?
1 Like
Yeah, sorry I’m futzing with it right now – not related to the number issue, it was a change that was planned already. I’ll get back to you if it fixes itself when I’m done, but I doubt it.
1 Like
There are some remaining issues with the taxon change I just did – should have those fixed soon. But the observation count is still 0 for percivali…
1 Like
the observation is now Needs ID. that’s strange, considering there are 2 IDs.
1 Like
Yeah, sorry again, that was one of the lingering issues of the taxon change. I’ve asked loarie about it already. Clearly I shouldn’t have posted this forum question while making a big taxon change, I just wasn’t thinking :/
Anyway, I added another ID to bring it back to RG, which in theory shouldn’t matter because the observation count on the taxon page isn’t restricted to RG. I’m still seeing 0 for that subspecies.
1 Like
ok… i guess the best i can do here is confirm that what you’re seeing is what i’m seeing.
for some reason, if you ask the API taxa endpoint for observation_count for 147637, it returns 0. it looks like that value may be stored in a table on the back end. i thought maybe the observation is so old that the record in that table may simply not have been updated with recent processes. so i created a dummy casual record on that taxon, hoping that might trigger a new count, but no luck…
2 Likes
i checked on this one more time just now, and the count now reflects 2 records. i’m not sure if anyone else did anything to help this along, but if not, maybe it just took a little bit for the count to get updated? anyway, i went ahead and deleted my dummy record, and hopefully the count will be set correctly to 1 at some point.
1 Like
I see it as 1 now.
2 Likes
Thanks guys!
I’m going to close this, but I’m still not sure what caused the issue in the first place. I’ll keep a lookout for similar problems in the future.
1 Like