|Deletions are marked like this.||Additions are marked like this.|
|Line 17:||Line 17:|
|DXKeeper can also import QSOs from a tab-delimited file, such as can be exported by a spreadsheet application; see the '''tab-delimited file''' option documented [http://www.dxlabsuite.com/dxkeeper/Help/Import.htm#ADIF%20Style here].||DXKeeper can also [http://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Importing%20tab-delimited%20files import QSOs from a tab-delimited file], which can be created from a spreadsheet application.|
To import QSOs from an ADIF file,
Select the Main window's Import QSOs tab
in the Options panel,
uncheck all boxes except the Record import errors in error file box, which should be checked
set the ADIF style options panel to Import standard ADIF unless your ADIF file was generated by one of the applications listed in this panel, in which case you should select that application
click the Start button in the window's lower-left corner; a standard Windows file selector window name ADIF Import will appear
use the ADIF Import window to select the ADIF file you wish to import; when you click it's Open button, DXKeeper will import the contents of the selected file into your log; if errors are encountered during this process, DXKeeper will display a file describing these errors when the import process has completed.
DXKeeper can also [http://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Importing%20tab-delimited%20files import QSOs from a tab-delimited file], which can be created from a spreadsheet application.
There are two primary issues when importing an ADIF log exported by another logging application:
- recovering each QSO's DXCC entity
synchronizing with the ARRL's [http://www.arrl.org/lotw/ Logbook of the World (LotW)]
Recovering each QSO's DXCC entity
The ARRL defines a unique, immutable Entity Code for each DXCC entity in [http://www.arrl.org/awards/dxcc/dxcclist.txt]
The [http://www.dxlabsuite.com/ADIF.htm ADIF specification] provides a tag named DXCC to convey each QSO's Entity Code. If your ADIF file specifies a DXCC tag for each QSO, then DXKeeper will accurately recover the DXCC entity you logged with each of your QSOs with no additional action required on your part.
Unfortunately, some logging applications do not include the DXCC tag in exported ADIF files. When DXKeeper imports an ADIF record that doesn't specify an Entity Code, it determines the QSO's DXCC entity by analyzing the callsign -- using today's callsign-to-entity rules. If you logged a QSO with KA1DX back in 1952, and your logging application exports this QSO without the Entity Code for Minami Torishima (which in ADIF would be <DXCC:3>177), then DXKeeper will assign the imported QSO's DXCC entity to be the continental US (Entity Code 291). To automate the correction of such QSO's, Joe W4TV created a set of Fix scripts that inspect each QSO in DXKeeper's log, apply the callsign-to-entity rules in force as of the date of the QSO, and if appropriate modify the QSO's DXCC entity, CQ zone, ITU zone, Continent, and IOTA tag. You'll find these scripts in DXKeeper's Scripts sub-folder:
To run a script, click the button labeled ~ in the Filter panel at the bottom of the Main window's Log QSOs tab; this will cause a Scripts button to appear. Click the Scripts button, and use the resulting Run Script window to navigate to DXKeeper's Scripts sub-folder and select the Fix script you wish to run.
If you select a script that potentially modifies your QSOs (as all Fix scripts do), you'll be given the opportunity to make a log backup before running the script; agreeing to create such backups is a good idea. After a script runs, DXKeeper will display a report that summarizes the changes made. More information about Scripts can be found in [http://www.dxlabsuite.com/dxkeeper/Help/Scripts.htm], or by clicking one of DXKeeper's Help buttons and navigating to the Filtering, Modifying, and Reporting with Scripts topic in the Logging and Managing QSOs section.
Synchronizing with LotW
Increasingly, logging applications are tracking LotW status independently of hardcopy QSL card status for each QSO. ADIF was slow to define a standard way to do this, so many logging applications defined "private" tags for this purpose. DXKeeper can read the private LotW status tags exported by [http://www.logger32.net Logger32] and [http://www.dx4win.com DX4WIN], but there's an alternative: direct DXKeeper to review all of the QSOs you've uploaded to LotW and all of the QSLs that LotW has generated in your account, and to then update your logged QSOs to reflect the status information reported by LotW. Step-by-step directions for doing this are provided in [:QSOsAlreadyUploadedLotW:Handling QSOs already uploaded to LotW]; before doing this, you must first [:ConfigureLotW:Configure DXKeeper for Interaction with LotW].
[http://groups.yahoo.com/group/dxlab/post Post a question or suggestion on the DXLab reflector]
[:GettingStarted:Getting Started with DXLab]