search

BaconRadio / dx-logger

HF Logging Software designed for remote, local, and portable operations
2 stars 0 forks source link

DXpedition Tracker #2

Open cjtheham opened 2 years ago

cjtheham commented 2 years ago

Search for a callsign, and be shown a grid of bands and modes you have and have not worked them on.

PotatoesMakeChips commented 2 years ago

Where should the data come from? We could do it internally or pull from Clublog/LOTW etc...

Depends on where in the UI you want it, I guess. If you're going for an "awards" style page, then on the fly, polling new QSO conformations can be put in the API request for the data. But if you're thinking of more general logging (as in preventing dupes), you'd want the data to come from internal data.

A graphical chart like that would be much more useful data for the QSO logging screen than just a big red dupe warning. Maybe the date of the last contact could be included? But that adds a lot of complexity to the API data.

cjtheham commented 2 years ago

My initial thought was internally, see Log4OM as a reference to how they display this data. Can bring back the complexity in the API return data by only including it for the country rather than the specific QSO, and not displaying it for domestic contacts. But, still complex because you're adding in too many ifs on what returns the extra data.

Sorry I've been inactive on this project. Been working on a lot of physical projects and prep for upcoming events. My hope is that during uni I may have more time to dedicate, but that's still uncertain. This tends to be the fate of many projects I've started 😂

PotatoesMakeChips commented 2 years ago

Could do it by callsign on the logging screen

GET('api/bandsworked/')

would return something like:

{ "160CW":False, "160SSB":True, "160Data":True }