Log Integrity

DXKeeper Online Help Contents

 

When you're logging a new QSO, DXKeeper makes it easy to record valid information, prompting you if you attempt to record invalid information. When you're importing QSOs, DXKeeper reports any that contain invalid information, and makes it easy to later locate and correct them.

In a QSO, these 5 items are considered mandatory:

Every QSO is expected to specify a valid value for each mandatory item; a QSO that does not satisfy this criterion is considered broken with a fatal error.

Every QSO is expected to specify a valid Station_Callsign; a QSO that does not satisfy this criterion is considered broken with a non-fatal error (unless it also contains a fatal error).

If the current log specifies one or more QTHs from which QSOs are made, every QSO is expected to specify a valid myQTH ID; a QSO that does not satisfy this criterion is considered broken with a non-fatal error  (unless it also contains a fatal error).

All other items can either specify a valid value, or be left empty; a QSO that does not satisfy these criteria is considered broken with a non-fatal error (unless it also contains a fatal error).

An item can be invalid for one of several reasons:

  1. The specified value is inconsistent with the rules governing the item; for example,

  2. The specified value contains more characters than DXKeeper will store; for example

  3. The specified value is inconsistent with the value of a related item, for example

If you attempt to log a QSO via the Capture window with a fatal error (one or more mandatory items that are missing or invalid), DXKeeper will render those items’ captions in red font, and refuse to log the QSO. If you attempt to log a QSO via the Capture window with one or more non-fatal errors, DXKeeper will log the QSO, and consider it broken.

If you use the Main window’s Log QSOs tab to create a new QSO, but fail to specify a valid value for each mandatory item, attempting to log the QSO will cause DXKeeper to render those items’ captions in flashing red font; DXKeeper will refuse to allow any other QSO to be selected until each mandatory item has been modified to specify a valid item, or until the QSO has been deleted. If you use the Main window’s “Log QSOs” tab to create a new QSO with one or more non-fatal errors, DXKeeper will when directed log the QSO, and consider it broken.

When importing a QSO from an ADIF or tab-delimited file, any record that does not specify both a Call item and a QSO_Begin item (both QSO_DATE and TIME_ON fields)  will be reported as illegal and rejected. All other imported records will result in the creation of a logged QSO; if the logged QSO contains fatal or non-fatal errors, the errors will be reported, and the QSO will be considered broken.

If you select a logged QSO that contains one or more mandatory items that don't specify valid values, DXKeeper will render those items’ captions in flashing red font; DXKeeper will refuse to allow any other QSO to be selected until each mandatory item has been modified to specify a valid item, or until the QSO has been deleted.

If a logged QSO not containing a valid Station_Callsign is selected, DXKeeper will make the Auxiliary panel visible and flash this panel's station call label in blue font.

If the current log specifies one or more QTHs from which QSOs are made and a logged QSO not containing a valid myQTH ID is selected, DXKeeper will make the QSL panel visible and flash this panel's myQTH label in blue font.

If a logged QSO containing a item with a non-fatal error is selected, DXKeeper will make the panel containing the item visible, and flash the item's label in blue font.

If a panel on DXKeeper's Main window spontaneously appears but with no label flashing, a QSO containing a fatal or non-fatal error was transiently selected; use the tools described in the following section to find and correct this QSO.

Finding Broken QSOs

To filter the Log Page Display to contain only QSOs that are considered broken, click the Broke button in the Filter panel at the bottom of the Main window's Log QSOs tab. If Subdivision validity checking is enabled, QSOs that specify invalid primary administrative subdivisions or invalid secondary administrative subdivisions will also be present in the Log Page Display

To review every logged QSO and report those that are broken, click the Recompute button at the bottom of the Main window's Check Progress tab; invoking the Recompute function will also reconstructs all realtime award tracking information in the current log.