View Revisions: Issue #2261

Summary 0002261: Logbook API used by QSO Relay (and JTAlert) fails to populate MY STATION fields into QSO records
Revision 2018-02-22 14:56 by WA9PIE
Description In working with Chris, VK2BYI, to get the API working so that Logbook will accept QSOs forwarded by QSO Relay, he has discovered that one thing remains to be done.

When the QSOs are created in Logbook, the fields in those records need to be populated with the data from the 'active' MY STATION information. Chris has indicated that - once this is done - he believes that this API will be complete and fully functional. It's an important part of the integration for 3rd party programs that will use HRD.

This applies to any integration using this API... but includes WSJT-X, JTAlert, and QSO Relay.
Revision 2017-09-22 23:08 by WA9PIE
Description In working with Chris, VK2BYI, to get the API working so that Logbook will accept QSOs forwarded by QSO Relay, he has discovered that one thing remains to be done.

When the QSOs are created in Logbook, the fields in those records need to be populated with the data from the 'active' MY STATION information. Chris has indicated that - once this is done - he believes that this API will be complete and fully functional. It's an important part of the integration for 3rd party programs that will use HRD.
Revision 2017-09-22 23:05 by WA9PIE
Description In working with Chris, VK2BYI, to get the API working so that Logbook will accept QSOs forwarded by QSO Relay, he has discovered that one thing remains to be done.

When the QSOs are created in Logbook, those records need to be populated with the data from the 'active' MY STATION information. Chris has indicated that - once this is done - he believes that this API will be complete and fully functional. It's an important part of the integration for 3rd party programs that will use HRD.