+J Grouchy Posted March 30, 2017 Share Posted March 30, 2017 The way I see it, there are four reasons why a cache would get duplicate logs. 1. The finder doesn't know any better. Some newbie caches just don't yet understand the difference between a found it, note, or other logs. 2. A duplicate log was "accidentally" posted. This often due to a system glitch where the logger doesn't know if the Found It/Attended log took, so they post another one. Sometimes what happens is that user submits the log, the database is updated, but something goes wrong in constructing and returning the response that the log was posted. 3. The very few exceptions (Brass Cap, YOSM, or recurring events which re-use a GC code) where posting multiple found it/attended logs are legitimate. 4. The finder intentionally posts multiple found it/attended logs knowing full well that it's not considered to be an acceptable practice. This topic has come up quite frequently in the past and my suggestion has been to just create a pop-up alert when the system detects that a previous Found It/Attended log has been posted. It would have some text something like: You have already submitted a "Found It" log for this cache. Submitting another Found It log may impact your geocaching statistics and is not generally an accepted practice [Link to Help Center Page]. Are you sure you want to submit another "Found It" log? [Accept] [Cancel] That would likely eliminate almost all of the duplicate logs in the first two scenarios, would allow duplicates in the third scenario, and become an annoyance to finders in scenario #4. I just happen to consider number 3 as not a valid reason. The first two examples are locationless caches and the third example should just receive a new GC number for each event. Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.