Unarchiving caches.

[+Corp Of Discovery]

Is there, or should there be, a time limit after which a cache can't be unarchived? No particular instance in mind, just something I've seen done in a few different ways recently and was wondering about it.

[+Bud]

Last I've heard is that a cache can be unarchived for three months after archival. After that you'd have to submit a new cache.

[+TotemLake]

Last I've heard is that a cache can be unarchived for three months after archival. After that you'd have to submit a new cache.

The unarchival also means it will need to meet current guidelines. The cache loses its grandfathered status once archived.

[+tozainamboku]

Last I've heard is that a cache can be unarchived for three months after archival. After that you'd have to submit a new cache.

Following situations can happen

1. A new cache is place within .1 miles of the archived cache. The archived cache can no longer be unarchived because of the saturation guideline.
   
2. Cacher fixes problems before another cache has been placed. The archived cache otherwise meet the current guidelines. The reviewer unarchives the cachet
   
3. Cacher fixes problems before another cache has been placed. The archived cache otherwise meet the current guidelines. The reviewer says too late you must submit it as a new cache.
   
4. Cacher fixes problems before another cache has been placed. The archived cache otherwise meet the current guidelines. Cacher choose to submit this as a new cache.
   

Why even have option #3? Perhaps it is easier for the reviewer to see and review caches that come through the normal process of submitting a new cache than to respond to an email from a cache owner who had finally maintained an archive cache. More likely it that Groundspeak wants to emphasize that caches are not permanent. They get archived and except in exceptional situations once they are archived they stay archived. Reviewers are allowed to unarchive cache so they can use the archive as an immediate solution to some problem with the cache. For example, when someone emails Groundspeak claiming to be from the NPS and says to archive and remove the caches along the AT, Groundspeak immediately archives the caches. After some investigation it turns out the person was note actually authorized to ask Groundspeak to remove some of the caches or an agreement is reached so that cache placed some minimum distance from the trail right-of-way on NFS, state, or private land with permission are allowed, these could be unarchived. Some reviewers may also have found that an owner who has been lax about maintaining a cache will take immediate action when that cache gets archived. They are using the archive as a final warning. The cache owner knows that if they don't fix the cache quickly someone else may place one and their cache can't be unarchived. I doubt there is a three month rule. Perhaps it is more of a rule-of-thumb, so that reviewers don't abuse their ability to archive/unarchive.

[+sbell111]

Agreed. I see no point in having option #3.

[+Renegade Knight]

Is there, or should there be, a time limit after which a cache can't be unarchived? No particular instance in mind, just something I've seen done in a few different ways recently and was wondering about it.

 

I can't see a need for a time limit.

 

Just that you be the owner, and that the cache meets current requirments when it's unarchived.

 

Plan B is perhaps even simpler.

 

Archives are permanent.

Edited September 18, 2008 by Renegade Knight