Why are all our YOSM's now showing up on our "Oldest Caches Found"

Question

We now have 9 YOSM's showing up on our "Oldest Caches Found" stats, all 9 are of YOSM Porthcurno which was the last YOSM before archive. We were used to a slight difference on our stats but this really messes a complete section up! Can we change this in any way to show the Oldest Caches we have really found?

Answer 1

GC45CC has a placed date of 26/03/2002. You have found only one cache with a placed date older than that, GC2BA5. Therefore, the list is correctly showing the ten logs where the caches' placed dates are oldest.

Whether these lists should be showing ten logs or ten unique caches is another question. Your scenario is only possible due to the fact that you've logged the same cache at least nine times. For most cachers, with each cache only logged once, there's no difference.

Comments

As of now, we don't limit to unique finds in other places (inflated find counts are shown in people's totals if there are multiple logs), so it seems reasonable that that is the case here as well, I think.

If it's not desired to have the same cache showing up multiple times, it's always possible to change all but the first log for it to notes.

Answer 2

YOSM was an anomaly in two ways: firstly because multiple finds of the same cache were allowed, and secondly because the d/t and placed date changed every time the cache moved. This led to odd statistics, like the latest month showing in my jasmer grid even if I hadn't been caching that month.

When the software changed to prevent multiple logging, YOSM and some other similar caches were archived. It would seem that the placed date was put back to the original date, which is why it now shows up like that in your oldest cache list.

Answer 3

What are YOSM's?

Answer 4

YOSM's were travelling Virtuals, standing for Ye Old Survey Monuments (Triangulation Points). They were recently archived by Groundspeak