[FAQ] - Auto Upload to Online Service

[foldynl]

Q: Is it possible to implement online upload (synchronization) to online services?

A: Initially, I thought it was an easy task, but through a step-by-step analysis of the problem, I have concluded that this feature will not be implemented at the moment.

The following areas need to be addressed for online upload to be useful:

• Insert QSO
• Update QSO
• Delete QSO
• Behavior during offline mode, switching to online mode (only selected services are online and various combinations)

Except for point 4, when QLog should handle it, the implementation of points 1-3 depends on the service. Unfortunately, not all services have these basic operations implemented.

According to my research and public information, the situation is as follows:

• Clublog - all operations are implemented
• HRDLog - all operations are implemented
• QRZ - all operations are implemented. Delete requires LOGID, a QSO ID assigned during the Insert operation. QLog does not have such LOGID for imported QSOs. Obtaining this would require QLog to query all imported QSOs, a process that QRZ administrators might not approve of due to potential thousands of QSO queries after import. Querying the QSO before the delete operation is possible but time-consuming. What should happen if this operation is unsuccessful? Should QLog prevent deletion or accept the risk of desynchronization?
• Eqsl - insert and update are implemented, but delete is not implemented
• LoTW - all is controlled by an external application, delete is not possible, and update needs a special exception.

In general, question is what should QLog do if error is detected during update/delete. Should block the operation in Qlog, should store the operation for later processing, how long should store it?

There can be many situations where the online/offline log can become desynchronized. What should QLog do in such cases? There are also more questions, unfortunately without answers.

While there is a possibility to implement online upload for selected services, from the user's perspective, it would be confusing to determine which service the online upload applies to. Another limitation is that, for example, LoTW is not an online upload service; it is a batch-processing service.

Based on all the information above, it appears that online upload can only be practically implemented for ClubLog and HRDLog. Unfortunately, this is not acceptable from my standpoint.

Am I wrong? Should I change my mind and implement it only for selected services? Will it be understandable for users?