Old journals fail to import due to missing 'ScanType'

[Silarn]

Until the Jan 25th 2018 update (v3, journal version 14) there was no ScanType in Scan events.

This is causing import errors for users with journals from back then.

There are a few caveats with this old data. Between the Aug 17th 2017 update (2.4b1) and the 3.0 update above, there was no way to differentiate between nav beacon scans and normal scans. Unfortunately that means those systems may have incorrect values in Pioneer as it will interpret them as scanned bodies. There's not much I can do about that.

However, the NavBeaconScan event was added in the Aug 24th 2017 update (2.4 open beta) which theoretically could be used to flag subsequent Scan events, but it seems problematic. I'd have to make sure I correctly track all the subsequent scans and then stop treating any additional scans as nav beacon data. I'm not sure how reliably that can be done.

I suppose the time period where this would have been an issue is relatively short, so maybe I'll just not worry about it.

I can differentiate between the 'basic' and 'detailed' scans by evaluating which data was included in the event.