Jump to content

Notification Service (beta)


WildGooseChase

Recommended Posts

So I was poking around and saw something I haven't seen before: :laughing:

 

Notification Service (beta)

The Notification system is currently active .

 

The Geocaching Insta-Notify service is a Groundspeak Premium Member feature. As new logs are posted to Geocaching.com you can get an instant email sent to you with the contents of that log entry. the Insta-Notify feature is experimental and is not yet approved by the Food and Drug Administration.

 

Create a new notification

 

I can't get it to work though. I keep getting this error.

Cannot insert the value NULL into column 'IsArchived', table 'GEO.dbo.WptLogNotifications'; column does not allow nulls. INSERT fails. The statement has been terminated.

 

Anybody had any luck with it? :)

Link to comment

:) Of course. I just tried it and found a couple small of issues of my own specifically:

 

1) The name field, when you create a new notification the 'name' field does not get saved and always gets stored as "New Notification". But when you edit it, it will save your name.

 

2) When you select "earthcache" you can only choose "temporary disabled" and "enabled" but not "publish" or "retract". This may have been intentional but it seamed odd that only this cache would not have those options.

 

I can think of several of new features to add to this but I will withhold them and just enjoy the bounty that has been provided.

 

Thanks.

Link to comment

Maybe it can't be helped...

 

But it doesn't seem that we should have to have a separate notification for each cache type.

 

Now there are probably only 4 cache types I want a notification for, but why set up 4 separate entries to do that?

 

(Yes, Jeremy, just as you suspected...as soon as you add something nice people complain it's not nice enough. Sorry. :) )

Edited by beejay&esskay
Link to comment
But it doesn't seem that we should have to have a separate notification for each cache type.

I'm not trying to be smarmy, but you seem to be complaining that you have too many options in how you wish to be notifed of new log entries. The granularity at which you can request notifications can be filtered right down to the type and log type (and area) you desire. And you want to just clicky on a list of cache types and get notified of everything? Yikes, that's a lot of logs and not a whole lot of options.

 

Instead the functionality is set up so you can decide on which log types you want that relate directly to the cache types you select. So with cache events you could, for instance, select the "attended" log type. These Insta-Notify options do not exist now but once the beta testing is over we will start opening them to more log types. If we went your way there would be no way to choose what log types you can have based on those cache listing types.

 

So yes, I agree that you may have to create a couple of notifications if you wish to watch a different type in the same area. It only takes a few minutes of your time and it sorta does its thing without any care and feeding.

Link to comment

Cool!!!

 

:)

 

Now I can be instantly notified about the 4 caches I will place in the next year and the other 2 that will be planted within 50 miles of me.......

 

Cool!!!!!

 

(Note: Sarcasm directed at the lack of new caches in my area and lack of cachers to fill the void....sigh)

Link to comment
Now I can be instantly notified about the 4 caches I will place in the next year and the other 2 that will be planted within 50 miles of me.......

Well, you could live vicariously through others by setting a subscription in more popular areas and curse their foul luck :)

Link to comment
Cool!!!

 

:)

 

Now I can be instantly notified about the 4 caches I will place in the next year and the other 2 that will be planted within 50 miles of me.......

 

Cool!!!!!

 

(Note: Sarcasm directed at the lack of new caches in my area and lack of cachers to fill the void....sigh)

Set your notification service around the 82601 zip code and take more day trips!

Link to comment

the Insta-Notify feature is experimental and is not yet approved by the Food and Drug Administration.

 

Please work on the FDA approval so we can get this out of beta.

 

/wonders if Google Maps is waiting on FDA red tape.

 

[Edit to add quote.]

Edited by Tharagleb
Link to comment
Doesn't seem to let you have miles over 50. For an Event cache I would like to by able to get them farther away..

 

Cool feature, WTG TPTB!

Do you really need to rush over to the site of an event the minute it been approved? They ususally give you some time before the event takes place.

Link to comment
Doesn't seem to let you have miles over 50. For an Event cache I would like to by able to get them farther away..

 

Cool feature, WTG TPTB!

Do you really need to rush over to the site of an event the minute it been approved? They ususally give you some time before the event takes place.

No, but if it's an option I want to use it. Not many events within 50 miles for me.

 

/does every innocent comment get flamed around here????

Link to comment

Tharagleb,

 

I think the point was you don't need instant notice of an event being published since events are not supposed to be published the day they are to occur. If you set up an event Pocket Query, you'll be fine, with plenty of time to attend the event even if the PQ only runs weekly.

 

This is how I do it and it works well.

 

:)

Link to comment
Tharagleb,

 

I think the point was you don't need instant notice of an event being published since events are not supposed to be published the day they are to occur. If you set up an event Pocket Query, you'll be fine, with plenty of time to attend the event even if the PQ only runs weekly.

 

This is how I do it and it works well.

 

:)

Thanks Robert.

 

Not to beat a dead horse. Because I am *not at all* concerned about this but....

 

1) Event gets published a few weeks before event.

2) I get new instant email notification via new service

3) I go to event(?)

 

The way it works now:

 

1) I get weekly notification

2) I *might* read the whole thing and find out about event

3) I go to event(?)

 

Your PQ thingy is the answer though.

 

/just tryin to explain my original post

Link to comment

Tharagleb:

 

Yup, just do a separate PQ for events only, set your distance from your home coords and put in the states you want.

 

I have mine set within 250 miles for all events, and I get it weekly which gives me plenty of time to attend.

 

Glad to be of some help!

 

:)

Link to comment
/does every innocent comment get flamed around here????

I am sorry, I did not mean to flame you.

 

I thought the purpose of the notifier was to let you know as soon as possible that there is a new cache close to you so you can decide of you want to rush out and find it. Since events can not be found (attended) for several weeks at least it seamed an email notification for it would be of little use.

 

Currently I have a PQ setup to show all unfound caches within 100 miles of my home and the events show up in it giving me enough notice, but then if this notifier is as good as I hope it will be that PQ may not be needed any more.

Link to comment
/does every innocent comment get flamed around here????

I am sorry, I did not mean to flame you.

 

I thought the purpose of the notifier was to let you know as soon as possible that there is a new cache close to you so you can decide of you want to rush out and find it. Since events can not be found (attended) for several weeks at least it seamed an email notification for it would be of little use.

 

Currently I have a PQ setup to show all unfound caches within 100 miles of my home and the events show up in it giving me enough notice, but then if this notifier is as good as I hope it will be that PQ may not be needed any more.

Okay, no problem. Thanks.

 

I was not thinking of the *instant* feature so much as the inidividual email aspect of it. I rarely read the entire weekly notification, just the ones closest to me.

 

I will start using PQ's for event caches, never thought of that.

Link to comment

I get stack traces if I try to add more than 10 notifications.

The boring details are:

 

Server Error in '/' Application.
Input string was not in a correct format.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.]
  Microsoft.VisualBasic.CompilerServices.DoubleType.Parse(String Value, NumberFormatInfo NumberFormat) +195
  Microsoft.VisualBasic.CompilerServices.DoubleType.FromString(String Value, NumberFormatInfo NumberFormat) +82

[InvalidCastException: Cast from string "). Remove one to create a new no" to type 'Double' is not valid.]
  Microsoft.VisualBasic.CompilerServices.DoubleType.FromString(String Value, NumberFormatInfo NumberFormat) +171
  Microsoft.VisualBasic.CompilerServices.DoubleType.FromString(String Value) +7
  Geocaching.UI.LogNotificationControl.BuildControl() +337
  Geocaching.UI.notify_edit.Page_UserLoggedIn(Object sender, EventArgs e) +1081
  Geocaching.UI.WebformBase.IsLoggedIn() +1105
  Geocaching.UI.notify_edit.Page_Load(Object sender, EventArgs e) +99
  System.Web.UI.Control.OnLoad(EventArgs e) +67
  System.Web.UI.Control.LoadRecursive() +35
  System.Web.UI.Page.ProcessRequestMain() +750


Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032

Link to comment
I believe you're limited to ten notifications, hence the error message when attempting to create #11.

You are, but the message shouldn't be so ugly. I'll try to track this down in the morning. In the meantime, yes, you are currently restricted to 10 notifications during the beta period, which I promise will be much shorter than Google's.

 

CompuCash, the feature hasn't been officially announced.

Link to comment
But it doesn't seem that we should have to have a separate notification for each cache type. 

I'm not trying to be smarmy, but you seem to be complaining that you have too many options in how you wish to be notifed of new log entries. The granularity at which you can request notifications can be filtered right down to the type and log type (and area) you desire. And you want to just clicky on a list of cache types and get notified of everything? Yikes, that's a lot of logs and not a whole lot of options.

 

Instead the functionality is set up so you can decide on which log types you want that relate directly to the cache types you select. So with cache events you could, for instance, select the "attended" log type. These Insta-Notify options do not exist now but once the beta testing is over we will start opening them to more log types. If we went your way there would be no way to choose what log types you can have based on those cache listing types.

 

So yes, I agree that you may have to create a couple of notifications if you wish to watch a different type in the same area. It only takes a few minutes of your time and it sorta does its thing without any care and feeding.

OK, not trying to be re-smarmy... :blink:

 

I guess what would be nice would be if you could select multiple cache types in one notification. (Especially since I understand there is a limit of 10?)

 

I imagine there are a number of us who would treat new traditional, multi, letterbox (and maybe even puzzle) caches in the same manner.

 

But if the design doesn't allow that easily, I'll set up my multiple notifications and be happy for the new functionality. ;)

Link to comment
I believe you're limited to ten notifications, hence the error message when attempting to create #11.

You are, but the message shouldn't be so ugly. I'll try to track this down in the morning. In the meantime, yes, you are currently restricted to 10 notifications during the beta period, which I promise will be much shorter than Google's.

 

CompuCash, the feature hasn't been officially announced.

 

Thanks Lang -

 

Jeremy -

 

Yes I understood that OP had said it was beta.

 

But so many people were talking about it and I just coont find it - so asked.

 

hope I didn't blow your scoop -

 

nice feature - evun puts my home coords in automagically - cool - thanks -

 

cc\

Link to comment

I know it is way up in this thread...

 

but thanks Jeremy for the clarification on the Mystery/Puzzle caches as "Unknown". I kept associating this with unknown cache container types instead of unknown cache types when I read the listings -- three times I might add.

 

Now, I have to apologize to robertlipe who told me the type was there at dinner tonight and I insisted it wasn't! Oh well, I'll just blame my oversight on the fact that my mind is completely messed up from trying to figure out one of his latest "unknown" caches!!! :blink:;):D

 

Thanks again for the clarification and feature!

Link to comment
As someone who likes to jump in with both feet whenever a new feature is announced, I think I'll pass on this one, at least until I'm assured that there is a way to mass delete the insty-things. :blink:

Don't hold your breath on that one. ;)

 

(added a smilie. inside "joke")

Edited by Jeremy
Link to comment

I took it out of debug mode this morning. It sent out only a few emails already. I'm monitoring all logs within 50 miles of Seattle to see what that looks like, and I already received my first watch email. If everything looks good I'll "soft launch" it in the announcements and make a more formal one on the site.

 

This was a particularly fun project to work on.

Link to comment

I thought the purpose of the notifier was to let you know as soon as possible that there is a new cache close to you so you can decide of you want to rush out and find it.  Since events can not be found (attended) for several weeks at least it seamed an email notification for it would be of little use.

 

Actually it is probably nice for those who don't hunt paperless or use Pocket Queries.

Of course they most likely would not be Premium members, but just maybe they are.

Now they can just get an email that a new cache is nearby and put in on their to-do list.

 

Also will work great for those who plan ahead all week of what caches they want to hunt and have a notification setup for disabled caches in the area.

Last minute check of email and you would easily see that that one cache you was going to go 10 miles out of the way to grab just got disabled.

Or better yet, have it setup to send an SMS message to your cell if one is disabled.

 

I like it.

 

Thanks,

Kenneth

Edited by kennethpruett
Link to comment
Guest
This topic is now closed to further replies.
×
×
  • Create New...