Cleaning up a trackables logs

[Andronicus]

A couple of weeks ago, I decided to delete a bunch of logs from one of my trackables. These logs were just "Visited" logs when one cacher had it "visiting" 50ish random caches around his home town. I was trying to clean up the list of logs so that I could actualy see its progress at getting to its goal.

 

What I didn't expect was that the cacher who had made all of those logs got 1 email notification per deleted log. That must have been annoying for him. He contacted me, wondering why I was deleting all of the logs. I explained in as nice of way as I could what I was doing, but I think that he still felt a little insulted.

 

Anyway, I guess the point is that I wish there was a way to delete TB logs where the notifications wouldn't be sent out.

[+Harry Dolphin]

Ah... Hmmm... My TBs/GCs do not want to visit caches. It says so on their pages. So I go through and delete 'Visits'. I think that finally convinced a few cachers to put my trackables in caches (after 8 to 18 months of wandering about doing nothing). (Or maybe, they just stopped 'visiting' them?) So, the notifications are good for that. I've only had one cacher complain. Without the notification, they would not have known... Since, obviously, they did not read the page.

So, I'm all for keeping the deletion notifications!

[+Twentse Mug]

In the listing of each trackable I ask not to use the visit option. If cachers stil do so, I just delete every took it to log. Now and then I get an angry e-mail but that gives also an opportunity to explain why I do that.

[+Lieblweb]

If you delete logs, doesn't that screw up the mileage?

 

(if the mileage is important to you)

[+kunarion]

If you delete logs, doesn't that screw up the mileage?

 

(if the mileage is important to you)

Yes and no. The mileage remains, but it's not obvious how the mileage occurred.

 

If the logs are only blank "took it to", and there are hundreds, they are just taking up space, and not particularly useful. But if they had stories and photos, I'd understand the holders being upset about deletions. If they'd ever had any actual log to the log.

[+Gitchee-Gummee]

If you delete logs, doesn't that screw up the mileage?

 

(if the mileage is important to you)

Yes and no. The mileage remains, but it's not obvious how the mileage occurred.

 

If the logs are only blank "took it to", and there are hundreds, they are just taking up space, and not particularly useful. But if they had stories and photos, I'd understand the holders being upset about deletions. If they'd ever had any actual log to the log.

Interesting thing there, of sorts...

 

Trackable "X" logged as visited to 30 caches;

Those 30 visit logs are deleted;

The logs no longer exist;

Deleting a log removes same -- it doesn't however, remove or delete the action (placing or visiting a trackable) in the cache.

Trackable "X" is yet in the cache(s) history(ies) as having been there -- so the mileage is correct.

 

Logs and "action" maneuvers are two different things. Related yes, but separate.

[Andronicus]

Ah... Hmmm... My TBs/GCs do not want to visit caches. It says so on their pages. So I go through and delete 'Visits'. I think that finally convinced a few cachers to put my trackables in caches (after 8 to 18 months of wandering about doing nothing). (Or maybe, they just stopped 'visiting' them?) So, the notifications are good for that. I've only had one cacher complain. Without the notification, they would not have known... Since, obviously, they did not read the page.

So, I'm all for keeping the deletion notifications!

Maybe I will add that to the pages of the trackabels that have specific missions. I don't mind a dip or 2 when it is a significant move progressing toward the mission, but 50 or 100 is annoying. Also, vacation dipping! One of my trackables is trying to get to Belgium. A cacher dipped it in Spain, then brought it back to Canada. It is not farther away from it's goal than when it started! Of course, it was likely never in Spain.

[Andronicus]

Here is a classic example of what annoyes me:

http://coord.info/TB4WVZG

One cacher had the TB for several months, and logged 927 times (925 visit logs), plus, most of the others who had it for a bit also dipped it several times. After 987 total logs, only 12 users, including me and 5 discovered logs, so only 6 'holders'. 981 logs by 6 users. So anoying.

[Andronicus]

Here is a classic example of what annoyes me:

http://coord.info/TB4WVZG

One cacher had the TB for several months, and logged 927 times (925 visit logs), plus, most of the others who had it for a bit also dipped it several times. After 987 total logs, only 12 users, including me and 5 discovered logs, so only 6 'holders'. 981 logs by 6 users. So anoying.

I just changed the mission. Previously it said "To visit many caches"

 

I guess the TB holders interpreted that too literaly. I was not wanting it to be dipped, but to actualy go to and be dropped into many caches. Oh well, maybe it was all my fault.

[+fuzziebear3]

Actually, if you delete a visit log, and then do recalculate distance, the distance is corrected as if the bug never visited that cache.

[+DanOCan]

I used to do a lot of "Visits" with trackables I picked up. I then realized that those likely did get boring for the owner so I expanded my personal rules a little bit:

 

- I only log a Visit if I actually have the bug with me when I find the cache. (This has always been the case.)

 

- I'll only log a Visit for the cache that represents the furthest point I go on that journey. As an example, I'll only log the cache at the summit of a mountain and not the ten caches along the way up.

 

- I'll log a Visit if it shows the trackable reaching a new state. As an example, on my last visit to Chicago we did a weekend run to Michigan. I made sure to visit the trackables I had to a cache in MI before we came back to IL where I eventually left them. (For the trackables I actually left in MI I just dropped them and didn't bother with the visit.)

 

- I do try and post pictures of the trackables at the cache they are visiting. I like to try and prove I actually took the trackable to the cache that I said I did.

 

I think logging a Visit for a trackable when it wasn't actually at the cache is about as lame as logging a Discovered It because you saw the number of the trackable printed on a sheet at an event.