Feature Request: Logging Shortcut

[CoyoteRed]

I've posted elsewhere of a way to reduce server load and bandwidth by having a shortcut to the logging page on the nearest list.

 

For any cache that a user has not found you could put a link directly to the logging page. Place this under the last found date where a user's found date goes. Because they haven't found it yet that place is blank.

 

Suggested text for link "[Log this cache now]" should be explanatory enough to not get too many questions about it.

 

Thank you.

 

ADDED: Could make it a _BLANK target for people who don't know about the SHIFT-CLICK to open a new window thus saving the nearest page reload.

Edited July 23, 2004 by Jeremy

[CoyoteRed]

That "LOGGING" not "LOG IN"

 

Can't edit title. Maybe a forum moderator can do that for me?

[AJK]

I'd like this - it would be very useful when you've hit multilple caches in one area in a day.

[+TeamG]

About your title

[Jeremy]

I changed the title.

 

The nearest cache page is getting pretty busy, but I have run into similar issues in the past when logging more than 1 cache, so I see the merit. I'll look into adding a link without continuing to overwhelm the results page.

 

I doubt I'll use target=_blank. IMO it is easier for someone to shift-click on a link or right click the link and choose to open it in another window. That keeps the control in the user's hands.

[robertlipe]

I had this feature in my (now unceremoniously broken) rapid logging interface. It reduces the number of required page loads. Since a substantial number of page loads return errors these days - and even more of the "find by nearest" requests return database timeouts - a "log it" that shoots you directly to the "log this cache" interface would be a Good Thing.

 

Actually, my stuff included the nearest caches (with link) and a link straight to log it (as well as a link to 'mail cache owner' if type == virt || type == locationless straight on the cache page itself to even further reduce the number of required page loads, but that involves extra work at page generation time which I'm guessing (hoping) you're trying to avoid like the plague right now...

 

I could log a day's worth of finds and never have to wait for a page load other than the ack on the log...The MOC owners sometimes asked me how I could log a find without ever viewing the actual cache page. :-)

 

And I agree that target=_BLANK should be avoided. Folks can middle click if they want it in a new browser tab. (Shame that doesn't work for so many of the links on the site now that it's laden with javascript postbacks...)

Edited July 23, 2004 by robertlipe

[+Marky]

boulter's GQS page does this. Very handy for when I am logging from my Sidekick. Just enter the waypoint and select 'log' and click 'go'. Couldn't be easier. This is a very useful page, especially if you are using a phone browser.

 

--Marky

[+CompuCash]

Good idea Coyote -

---->> side note - I am a Windows professional - never knew about shift click -

-------- thanks! - been righ clicking for the menu for years. Learnt sumpin new!

 

A hint that my be helpful - I started this because of the time moving around in GC.com - tho I do keep 3-4 windows open and do a lot of dragging -

 

I use GSAK and love it - if you use the split screen (even a small one) when you select one of the records from the loc or gpx files you downloaded you get a link directly to the gc.com cache page - I just drag that to a window and I'm there can do my log, move to the next record in GSAK (down arrow to next if you sorted on not found) and do it again.

[robertlipe]

 

A hint that my be helpful - I started this because of the time moving around in GC.com - tho I do keep 3-4 windows open and do a lot of dragging -

Find a browser that supports tabbed browsing. It will change your life.

 

Mozilla and Firefox (or whatever it's called this week) as well as many others support this. You can load a bazillion web pages independently and not be needlessly tortured by your window manager.

 

(Follow-ups in a different thread, please.)

[+Marky]

I use GSAK and love it - if you use the split screen (even a small one) when you select one of the records from the loc or gpx files you downloaded you get a link directly to the gc.com cache page - I just drag that to a window and I'm there can do my log, move to the next record in GSAK (down arrow to next if you sorted on not found) and do it again.

You could also create an HTML link directly to the Log A Find page and save a click or two.

 

--Marky

[+ClydeE]

I use GSAK and love it - if you use the split screen (even a small one) when you select one of the records from the loc or gpx files you downloaded you get a link directly to the gc.com cache page - I just drag that to a window and I'm there can do my log, move to the next record in GSAK (down arrow to next if you sorted on not found) and do it again.

You could also create an HTML link directly to the Log A Find page and save a click or two.

 

--Marky

Yes, just add a custom URL to do this.

 

A couple that might in handy here:

 

Add cache to watch list=http://www.geocaching.com/my/watchlist.aspx?w=%gcid

Log cache=http://www.geocaching.com/seek/log.aspx?ID=%gcid

 

To add a custom URL, Tools=>Options=Html

 

And don't forget if you prefix any custom URL name with ! (Exclamation mark) a link will be generated in any HTML pages that GSAK generates.

Edited July 24, 2004 by ClydeE

[CoyoteRed]

~BUMP~

 

While you're into the Nearest Cache Page--which is looking good, BTW.

 

That's a neat trick with GSAK, but if you can get more and more people to skip directly to the logging page it might help on the weekends.

 

Thanks!

[+Prime Suspect]

~BUMP~

 

While you're into the Nearest Cache Page--which is looking good, BTW.

 

That's a neat trick with GSAK, but if you can get more and more people to skip directly to the logging page it might help on the weekends.

 

Thanks!

Cache names aren't required to be unique. Forcing people to view the actual cache page before logging helps ensure they're logging the cache they intend to log.

[+Markwell]

The problem is that the ID number of a cache isn't readily displayed anywhere anymore. Not since the advent of the GUID. Now the ONLY place you can retrieve the actual ID number is through the actual cache page by hovering over the log link. You'll see the ID number in the status bar (at least in IE). You can't get the ID through the nearest cache page.

 

That being said, if you HAVE the ID number, you can get to the log page as ClydeE mentioned. For Prime Suspect's concerns, the page that you are making a log on does list the name of the cache that you are logging as a verification.

 

While it's true cache names aren't unique, I'd be hard pressed to come up with a situation where the ID number and the cache name are similar, unless they're part of a series. If that's the case, you'd be just as likely to log the wrong cache from the cache page as you would from a directly linked log.

[+CompuCash]

I use GSAK and love it - if you use the split screen (even a small one) when you select one of the records from the loc or gpx files you downloaded you get a link directly to the gc.com cache page - I just drag that to a window and I'm there can do my log, move to the next record in GSAK (down arrow to next if you sorted on not found) and do it again.

You could also create an HTML link directly to the Log A Find page and save a click or two.

 

--Marky

Yes, just add a custom URL to do this.

 

A couple that might in handy here:

 

Add cache to watch list=http://www.geocaching.com/my/watchlist.aspx?w=%gcid

Log cache=http://www.geocaching.com/seek/log.aspx?ID=%gcid

 

To add a custom URL, Tools=>Options=Html

 

And don't forget if you prefix any custom URL name with ! (Exclamation mark) a link will be generated in any HTML pages that GSAK generates.

AWSOME!!

 

Thanks Clyde -

[+CompuCash]

The problem is that the ID number of a cache isn't readily displayed anywhere anymore. Not since the advent of the GUID. Now the ONLY place you can retrieve the actual ID number is through the actual cache page by hovering over the log link. You'll see the ID number in the status bar (at least in IE). You can't get the ID through the nearest cache page.

 

That being said, if you HAVE the ID number, you can get to the log page as ClydeE mentioned. For Prime Suspect's concerns, the page that you are making a log on does list the name of the cache that you are logging as a verification.

 

While it's true cache names aren't unique, I'd be hard pressed to come up with a situation where the ID number and the cache name are similar, unless they're part of a series. If that's the case, you'd be just as likely to log the wrong cache from the cache page as you would from a directly linked log.

not sure if I fully understand your post Markwell.

 

In GSAK you don't need to know the ID number. I had to do a little playing and read the help file on Custom HTML to do it, but when I copied and pasted (from his post) to the dialog box they popped right up where they were supposed to -

 

You only have to right click the Waypoint Name - selct Custom URL and both log and watch show up click and bingo you are on the log page

[CoyoteRed]

The idea is to jump directly from the Nearest Cache Page (or search results, whatever you want to call it) and go directly to log page skipping the cache page.

 

The reason I'm proposing this change is because it would get in front of many times more people than any other solution, thus maybe helping with site load on the heavy days.

 

While the GSAK solution is great I think only a tiny number of users would know about it, only benefit a very few, and not do much to reduce the hits to the servers and SQL engine.

 

The CID is already generated on the Nearest Cache page to be used with the download function. It would be simple to place it somewhere on the list because the info is already being used, thus no extra load on the database.

 

Like mentioned before, place a short link in the same position where the date of your find for a cache is now as the vast majority of the time either you've logged the cache or you have the opportunity to log the cache, i.e. you're not using space that wouldn't be used after you log it and you don't need the link then, anyway.

 

Please, let's focus on adding this functionality to the site and leave the GSAK tips in the GSAK thread.

 

Thanks!

[+CompuCash]

then (staying on topic) -

 

if you put your link on the search page (nice idea) then why does anyone need to worry about the ID number?

[CoyoteRed]

if you put your link on the search page (nice idea) then why does anyone need to worry about the ID number?

Not to put words in his mouth, but I think Markwell was mentioning it because that is the number to manually plug into "http://www.geocaching.com/seek/log.aspx?ID=xxxxxx" to go directly to the log page.

 

I was mentioning it to point out to Jeremy (not that he doesn't already know) that the varible is already being used to build the page. If it wasn't aleady there, he might have had to change the query to return the value. I was pointing out that it might not be too much work to include it. That's all.

[+CompuCash]

Is see - thanks - maybe it worked -

 

I rather like your idea of the button or link where the date would go on the search page.

 

Since I have been using PQ's and GSAK I have not been using the search page that much lately. The little trick that Clyde gave us is nice - skips right to the log page and saves a lot of time waiting for the cache page to open - and as is your design here, saves a lot of bandwidth too.

 

Not everyone uses GSAK so your link should hopefully (if installed) make the same gains.

Edited September 21, 2004 by CompuCash

[+Markwell]

Not to put words in his mouth, but I think Markwell was mentioning it because that is the number to manually plug into "http://www.geocaching.com/seek/log.aspx?ID=xxxxxx" to go directly to the log page.

Of course, the other alternative (if we're talking manual) is to allow the log.aspx? to accept the "WP=GC1234" format as well as the ID=.

 

If that's the case then all I need to know to go DIRECTLY to the log page is the waypoint.