SK Notification to ARC

[k5dvt]

Is your feature request related to a problem? Please describe.
No - For back end (Non-public) use to notify the council if a repeater trustee goes SK.

Describe the solution you'd like

Have an API (Or it looks like in this case an XML interface? Never messed with that before) request do a callsign search periodically (Every 3 months?) for the repeater trustee of a given repeater, and see if the trustee has gone SK. After which the council will be notified and made aware that a "Rogue" repeater may be operating and may also open up the possibility to contact local clubs/hams to find out what the status is or whom to transfer the coordination to.

Describe alternatives you've considered

Using an API again to query the FCC or QRZ database to see if a callsign has been cancelled from expiring after the two year grace period, indicating the the operator has either passed or out of the hobby.

Additional information

I believe the SK status on QRZ is a user manually entered process, but it should show license is expired on their automatically.

[JoshuaCarroll]

Notes to self
Mark SKs with /SK
Mark expired with /EXP

Filter both from future QRZ checks.
Filter both from spListPossibleRepeaterUsers
Filter both from spListPossibleTrustees

Make sure someone marked "/EXP" can still log in, but disallow them from doing anything. Upon login, check to see if it is still expired, if not clear the flag.

[JoshuaCarroll]

Added Users.SK, Users.LicenseExpired, Repeaters.LicenseeSK, and Repeaters.LicenseExpired. All are bit datatypes.

Updated spGetAllCallsigns, spListPossibleRepeaterUsers, and spListPossibleTrustees.

[JoshuaCarroll]

Created spUpdateSilentKeys. Implemented in web services. Still need to handle expired licenses.

[JoshuaCarroll]

Something is causing a non-infinite recursive loop. Need to seek and destroy.

[ke4ahr]

The FCC has modified the ULS database in such a way as to keep callsigns Active while they are past expiration. Thus the date of expiration vs current date is the most reasonable information, unless the callsign has been cancelled and replaced by another callsign.

[JoshuaCarroll]

The FCC has modified the ULS database in such a way as to keep callsigns Active while they are past expiration. Thus the date of expiration vs current date is the most reasonable information, unless the callsign has been cancelled and replaced by another callsign.

We are referencing QRZ, not the ULS.

[ke4ahr]

I did find this: https://github.com/n00tz/FCCULS-mysql

[k5dvt]

It's probably better to reference QRZ since the amatuer radio community can share the obit and actually show the ham as deceased. The spouse of the deceased has to tell the FCC to cancel the license, which almost never happens because they are unaware that's the order of things, and the license has to wait to be expired. So for more timely information QRZ may be the best route.

…

On Mon, May 22, 2023 at 1:11 PM Kris Kirby ***@***.***> wrote: I did find this: https://github.com/n00tz/FCCULS-mysql — Reply to this email directly, view it on GitHub <#646 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGFB573YBWUUKTEBS73DT3TXHOT4BANCNFSM4V6JQUBQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>