search

vzdc / vzdcwebsite

https://www.vzdc.org
3 stars 4 forks source link

Solo certs not expiring... #141

Closed victor46 closed 4 years ago

victor46 commented 4 years ago

Look at Jayden Herman, was supposed to expire on June 30th, 2020, still showing soloed.

image

image

victor46 commented 4 years ago

image

fixterjake commented 4 years ago

@victor46 Is this both solo certs for vatusa and the tower ones which are only on our end, or is it just ones through vatusa?

victor46 commented 4 years ago

no just local solo certs. This isn't linked in anyway with VATUSA.

fixterjake commented 4 years ago

@victor46 Gotcha, so do you know which value in the status field means it is active?

fixterjake commented 4 years ago

Also what is the process for adding a new solo cert. I assume for tower it is just the website, but for higher positions is it vatusa and our site, or just vatusa where you set it and let the site call the api and update from there?

victor46 commented 4 years ago

So if it's on VATUSA it means they are getting a solo CERT = aka a position higher than what they are certified for. On our website we do SOLO AUTHs which is current level but allows to control at a specific position they haven't been cleared for yet on a temp basis. It's a training tool if the MTR / INS decides to use it.

Thanks,

Aaron M. Albertson aaron.albertson@gmail.com (Cell) 540-632-1424

On Sun, Jul 19, 2020 at 2:46 PM Jacob Boyles notifications@github.com wrote:

Also what is the process for adding a new solo cert. I assume for tower it is just the website, but for higher positions is it vatusa and our site, or just vatusa where you set it and let the site call the api and update from there?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vzdc/vzdcwebsite/issues/141#issuecomment-660689781, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEL4EEEGGS4DEA6CL5YREL3R4M5SHANCNFSM4PBPEQGQ .

fixterjake commented 4 years ago

But from our end on the database side it is essentially the same from what I can see. If it is a solo auth it is just set through the roster edit page, but then vatusa solo certs are done though pulling from the api. As for the status do we track solo certs and solo auths differently in the solocerts table or the same? From what I can see active solo cert sstatus is 1, and expired is 2 but just want to confirm.

victor46 commented 4 years ago

Correct, but we do not pull from the VATUSA solo cert side. It's just our own database. And yes 2 is expired. but it's not expiring them properly.

Thanks,

Aaron M. Albertson aaron.albertson@gmail.com (Cell) 540-632-1424

On Sun, Jul 19, 2020 at 3:00 PM Jacob Boyles notifications@github.com wrote:

But from our end on the database side it is essentially the same from what I can see. If it is a solo auth it is just set through the roster edit page, but then vatusa solo certs are done though pulling from the api. As for the status do we track solo certs and solo auths differently in the solocerts table or the same? From what I can see active solo cert sstatus is 1, and expired is 2 but just want to confirm.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vzdc/vzdcwebsite/issues/141#issuecomment-660691662, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEL4EEDOLWZTM6DIKNXZKWLR4M7GDANCNFSM4PBPEQGQ .

fixterjake commented 4 years ago

The solo cert scheduled console event does actually pull from the vatusa api