Replies: 2 comments
-
At the moment it probably won't do what you are after for Club QSOs, however, its coming, a member will need their own account and they will set up a Station Location as the club callsign this can then be shared via the Station Logbooks feature to link it all together. Most of the codes there its interface that needs to be built. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks!
I have another question: I am trying to sync / import my LOTW
confirmations, and it breaks each time, even when I try and make the date
range for QSOs smaller.
Ideas?
…On Mon, Jan 16, 2023 at 11:55 AM Peter Goodhall ***@***.***> wrote:
At the moment it probably won't do what you are after for Club QSOs,
however, its coming, a member will need their own account and they will set
up a Station Location as the club callsign this can then be shared via the
Station Logbooks feature to link it all together.
Most of the codes there its interface that needs to be built.
—
Reply to this email directly, view it on GitHub
<#1931 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMU3GS3BSAQKL6OOWJUYIXTWSV4OTANCNFSM6AAAAAAT44LZJI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
What is the best way to handle multiple ops/callsigns? I see the feature for "Station Logbooks", but are they completely seperate things? I am looking for the option to log club QSOs using a different callsign.
Thanks
Scott, W1AL
Beta Was this translation helpful? Give feedback.
All reactions