Club Log

Club Log has no page of its own in the Third Party Logbooks menu. The login lives on your account. Which locations are included, and whether a new contact goes straight away, live on the station location.

The login

Open your callsign, Account, and the Third Party Services section. The Club Log card asks for Club Log Email and Club Log Password. The email is the address you use at Club Log. The box is an email box, and a callsign is rejected. The note under it says Club Log no longer accepts callsigns as usernames. Leave the email empty if you are not using Club Log.

Leave the password blank when you save the account for something else. The note under the box says an empty box keeps the password already stored. Both the email and the password have to be stored before anything is sent.

Which locations upload

Create or edit the station location. On the edit form the two lists sit on a card titled ClubLog. Both start on No.

• Upload to Clublog. Yes means this location is included when the timed job runs. The note under the list says the uploads go via /clublog/upload. No means the location is skipped, even with the password filled in.
• ClubLog Realtime Upload. Yes sends a new contact at the moment you save it, using the email and password from your account. Saving a change to a contact does not send it then. With this list on Yes, that save marks the contact to be sent again, and the timed job sends it, which also needs Upload to Clublog on Yes.

The callsign Club Log is given is the station location callsign. A /P or a club call has to exist on the Club Log account, or that location's contacts are refused.

The dashboard warns you when the email and password are stored, you have at least one station location, and every location still has Upload to Clublog on No. The warning asks you to enable at least one location.

The timed job

The job is clublog/upload. The Linux, FreeBSD, and OpenBSD install notes run it every six hours. It walks every user who has both an email and a password, and every location those users have set to Yes. It sends contacts that have never been sent, and contacts marked to be sent again.

A contact is marked sent after Club Log accepts the file. A new contact that realtime already delivered is already marked, so the job leaves it. If realtime was on and Club Log refused that contact, it stays unsent, and this job can send it on a later run when Upload to Clublog is Yes.

A LoTW match that fills in a grid, a state, a county, a zone, or an IOTA reference marks an already-sent contact to go again. That does not need Realtime Upload. It does need Upload to Clublog on Yes, because the timed job is what sends the change.

If Club Log answers with an authorization failure, Cloudlog clears the email and the password. When email is set up on this Cloudlog, it also emails you. A realtime failure while you are logged in shows a warning asking you to enter them again on your account. Until you do, nothing else is sent.

A log that is already on Club Log

On the ADIF page, under Mark as Uploaded to Online Logbooks, tick Mark imported QSOs as uploaded to Clublog Logbook. The note says to use that tick when the file does not already contain the Club Log upload status. A file that already has the status keeps it, and the tick does not replace it. Leave the tick off for a log Club Log has never seen, or the history will be treated as already sent.

Picture needed: clublog-station.png The station location edit form, the ClubLog card, with Upload to Clublog and ClubLog Realtime Upload.