Approval Question - Queue Position?

[+BillP3rd]

I have two related caches and need their GCxxxx numbers for their respective cache pages. I know that I can submit them and leave the "This cache is active" box unchecked and that this will get me the info I need. Now I've finished them and click on the link to activate them. They're in the queue. So far, so good.

 

Now the question.

 

If, prior to their approval, I notice an error on one of the cache pages and I make a change (edit) to the page does that push the cache back to the end of the line?

[Keystone]

Nope. In the review queue, the new caches show up in the order of their GC numbers. The order doesn't change if a cache is edited.

[+Yamar]

The other week I submitted 2 caches, lets say A and B. A was submitted a day before B and took about 3-4 days to get processed. B, on the other hand, was submitted second but got approved first within about 24 hours.

 

I suspect that queue order may not make a huge difference in the first place.

[Keystone]

yamar, there are lots of reasons why that might happen. If A was a complex multicache, and B was a single-stage tupperware in a park known to be cache-friendly, many reviewers will take the 30 seconds needed to review and list B right away, and put aside A to look at when more time is available.

 

Or, suppose that railroad tracks show up on the map for cache A. I have a database I check against to find out whether the tracks are active or abandoned. It is somewhat time consuming to do this, so I put this type of cache aside. Two days later, I find time to study the rail line data, and I confirm the tracks are abandoned, so the cache gets listed. The owner never hears anything from me because I solved the question on my own. All the owner sees is that cache A took longer to get listed.

 

That being said, we do our best to follow a first-come, first-served policy for similar caches. Two ammo cans in two different forests ought to be listed in the order they were submitted.

 

Another way I try to be fair is if one of my buddies submits a multicache. I won't review it until I go through the time-consuming process of checking the stages on all the other multicaches that have patiently waited in the queue for a day or two.

[+Coaster]

So that's the trick.

 

If you want your multi approved faster just coordinate with an approvers friend and palce a multi at the same time they do.

 

I'm just kidding. Keystone has always done a great job getting my caches approved quickly, even when I make the job less than easy for him.

[+Yamar]

yamar, there are lots of reasons why that might happen. If A was a complex multicache, and B was a single-stage tupperware in a park known to be cache-friendly, many reviewers will take the 30 seconds needed to review and list B right away, and put aside A to look at when more time is available.

...

I suspected that was probably the case (and I wasn't even complaining actually). Thanks for the explination though!

[+Team GeoDillo]

I have a related question.

 

Lets say I submit a cache but list it as "inactive" while I work on some of the details, upload a background picture, etc. Then, a day later another cacher submits a cache and marks it as "active", but it is within the 0.10 mile limit from the cache I previously submitted. Does my cache still show up on the approvers maps even though it is listed as inactive? ...and do I still get to place my cache?

[+Hemlock]

Lets say I submit a cache but list it as "inactive" ... Does my cache still show up on the approvers maps even though it is listed as inactive? 

We reviewers see all unapproved and/or archived caches when we do a "nearest" search. I'm not sure about the maps because I rarely use them for reviewing.

and do I still get to place my cache?

When I see this, I'll look at the description and notes on the disabled cache to see if there's an indication as to why its disabled. If something is obvious that the cache was long forgotten and never placed (i.e. a hide date of a year ago), I'll ignore the disabled cache. However in almost all the cases where I've seen this, the hide date was recent and there was no indication why it was disabled, so I emailed the owners to ask whats up. In general, and within reason, we go on a "first come, first served" basis.

 

So if you need to do disable your cache while working on it, leave a reviewer note to explain whats going on.