View Issue Details

IDProjectCategoryView StatusLast Update
00022671 - BacklogEnhancementpublic2018-04-15 08:07
ReporterWA9PIE 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Summary0002267: ADIF Field <qso_date_off> is not being imported
DescriptionWhen importing an ADIF file with the field <qso_date_off> in it, that field is not imported.

Generally, there are several new fields in ADIF that HRD does import.

As far as I can see, there are no target systems that use this field yet. For example, LOTW will not use this field for a match.
Steps To ReproduceBeginning with an empty log, import the attached ADIF file. The import dialog will display that the <qso_date_off> will not be imported. The rest of the data is otherwise imported.
TagsNo tags attached.
ModuleLogbook
Sub-ModuleImport Export
TestingNot Started

Relationships

Activities

WA9PIE

2017-10-07 11:08

administrator  

wsjtx_log - Copy.adi (2,099 bytes)

WA9PIE

2017-10-07 11:13

administrator   ~0004272

Image of import.

ADIFmessage.JPG (178,775 bytes)
ADIFmessage.JPG (178,775 bytes)

K7ZCZ

2018-04-15 07:25

manager   ~0004830

This error message is incorrect, as ADIF _does_ define a QSO_DATE_OFF field. It's relatively recent, but it's there.

The Logbook database is what doesn't have a QSO_DATE_OFF field. To fix this, we've got to add such a field; to add such a field, we need to migrate all existing customer databases when each customer upgrades to the first version of HRD they've run that supports the field.

Issue History

Date Modified Username Field Change
2017-10-07 11:08 WA9PIE New Issue
2017-10-07 11:08 WA9PIE File Added: wsjtx_log - Copy.adi
2017-10-07 11:13 WA9PIE File Added: ADIFmessage.JPG
2017-10-07 11:13 WA9PIE Note Added: 0004272
2017-10-07 11:18 WA9PIE Project 3 - Current Dev List => 1 - Backlog
2018-04-15 07:25 K7ZCZ Note Added: 0004830
2018-04-15 08:06 K7ZCZ Assigned To => K7ZCZ
2018-04-15 08:06 K7ZCZ Status new => assigned
2018-04-15 08:07 K7ZCZ Assigned To K7ZCZ =>