The first batch of annual portal email reminders just went out; there were 60 folks who haven't logged in to the portal in over a year.
These reminders are currently scheduled to go out monthly. Starting this July, I think we'll consider someone inactive after 18 months of no login. (That's six reminders, so they can't say they weren't warned.)
Be sure to keep the portal up to date if you change your email or other contact data to avoid having problems.
Please remember that current registration with the portal is necessary to maintain allocations, gateway registration in the encap database, and other functions of the portal. It's especially important for coordinators to keep it up to date.
Thanks! - Brian
Brian / Chris:
With reference to "keeping things up-to-date" I noticed something odd.
When I drill down to my current 44.2.x.x registered clients, I see they all (except 1) say region "California, Sacramento".
This is the default when I approve them.
I did approve one but changed the region description *BEFORE* I hit the approve button. His listing does show the change.
Now, I wanted to go back into the others and update theirs to be more accurate to their town/location. I can do an update, and see the update as long as I'm logged into the portal.
If I log out of the portal, and drill back down, the changes are not visible.
So, there is a disconnect between what's visible when not logged in, verses when you are logged in.
Not a deal breaker by any means. Just a bug report I guess.
Thanks
Bill Lewis / KG6BAJ
On Thu, Feb 6, 2014 at 10:46 AM, Brian Kantor Brian@ucsd.edu wrote:
These reminders are currently scheduled to go out monthly. Starting this July, I think we'll consider someone inactive after 18 months of no login.
Why is portal login used as a qualifier of active/inactive status? Wouldn't it make more sense to check that their IPs are routable? If their gateway is still online after many years of no portal login, does that make it inactive? I would call that "stable".
Tom KD7LXL
On Thu, 6 Feb 2014 11:39:30 -0800, Tom Hayward esarfl@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Thu, Feb 6, 2014 at 10:46 AM, Brian Kantor Brian@ucsd.edu wrote:
These reminders are currently scheduled to go out monthly. Starting this July, I think we'll consider someone inactive after 18 months of no login.
Why is portal login used as a qualifier of active/inactive status? Wouldn't it make more sense to check that their IPs are routable? If their gateway is still online after many years of no portal login, does that make it inactive? I would call that "stable".
Tom KD7LXL _________________________________________
I'm a coordinator but I don't have a node up currently but I am active even though I don't have an active RF node or a gateway, are you going to disqualify me? I agree about having an active IP that can be verified operational makes it "stable" but a node is a robot and it doesn't know if it's owner is "active" or went SK 6 months ago. Is it really such a burden to log in to an account once or twice a year?