Log4OM

Hi,

Just installed Log4OM so an absolute newbie. I have created the profile and also a database so Log4OM appears to be running in its most basic form. I have followed the instructions in the User Manual to load the SOTA CSV into the database. All appears to have succeeded - I see IMPORT COMPLETE. But when I close the import form I see no records displayed, neither has the database file grown at all. I appear to be missing a step somewhere ?

73 Andrew G4AFI

Andrew,
Log4om does not import your SOTA contacts from the SOTA DB it merges the SOTA DB into a database that already contains the QSO's and updates the QSO's - The SOTA DB is a merge not an import file

See the Log4OM user guide chapter "Downloading a “My Results” CSV file from SOTA"

Thanks for the quick response Terry.

So there is no facility to import my 5 years worth of historical SOTA Chaser entries from the SOTA database into a new (empty) Log4OM database ? This would be a great feature as I can then search through my historic records using the Log4OM search functions.

73 Andrew G4AFI

Hi Andrew,
There is an on line CSV to ADIF converter, use that to make an ADIF file from your SOTA CSV Data base, then use Log4om file/import ADIF to load it into Log4om

See http://www.g4lmw.co.uk/links.asp

Because SOTA don't conform to normal amateur radio software practices and use the ADIF format or DXCC numbers they make life hard for other developers but then looking at the P100/P150 debate that's hardly surprising

When we have time we will probably add the CSV import it's on our Mantis list

LOL re P100/P150 debate

OK thanks for that, I thought there had to be a way to do it.

73 Andrew G4AFI

G4AFI wrote:LOL re P100/P150 debate

OK thanks for that, I thought there had to be a way to do it.

73 Andrew G4AFI

In the spreadsheet I suggest you use the comments field for the activators summit reference and the notes field for the My sota ref this way when you import to Log4om we can help you resolve the ADIF SOTAref and MySORA Ref data

Unfortunately the CSV converter is not using ADIF version 3.04 which has the SOTA specific fields which where , would you believe, requested by SOTA MT. this is why I suggest you use the comments and notes fields.

If you need help with this then send me your SOTA CSV by email, my email is on QRZ

Hi Terry,

Well I tried out the process and I thought I had succeeded - I ended up with my SOTA Chaser Log in Log4OM. But .... when I looked at the entries I found that some of the dates had got mangled, with the day and month reversed. This is definitely some kind of bug in G4LMW's converter because I have examined the ADIF output file. After I have run the Cntrl q macro the date column in the spreadsheet gets mangled to match the mangled ADIF output. Very strange. Don't know if you have seen this yourself ? Perhaps I need to report this to G4LMW.

73 Andrew G4AFI

Oh! Perhaps Google for another?

Hi Terry,

I have emailed Rob, G4LMW to see if he can help me. I will also look for an alternative converter.

I am sure I will get there eventually. Can you explain what the SOTA Merge actually does once I have imported my ADIF file?

Thanks,
Andrew G4AFI

G4AFI wrote:I am sure I will get there eventually. Can you explain what the SOTA Merge actually does once I have imported my ADIF file?
I

Probably best to give you an example

G4???? logs several SOTA QSO's using another logbook program and he goes to the SOTA site and manually enters these SOTA contacts to the SOTA DB - He could be an activator or a chaser it makes no difference.

Because his existing program did not support the ADIF MYSOTA ref or SOTA ref fields he has been entering tha SOTA references into the comments or notes field.

He decides to change to Log4om so he exports an ADIF from his old logbook to Log4om because of our SOTA support but his SOTA references are in the wrong fields (comments/notes) in the imported ADIF.

He could of course manually enter the references into the correct ADIF fields one by one but this would be time consuming!

So by downloading his SOTA DB CSV file and using the Log4om merge facility the SOTA ref fields of his QSO's in Log4om are automatically updated with the correct information thus allowing correct display of his worked SOTA's

Once his logbook is up to date he has no further need to download from SOTA because the SOTA refs are now being correctly logged by Log4om all he needs to do from time to time is export a SOTA file from Log4om and upload it to the SOTA DB so that the SOTA MT can provide whatever awards he is due for.

We would have made the SOTA a download and upload an automatic operation like eQSL etc if the SOTA MT had been willing to cooperate with us

It's very similar to our LOTW or eQSL a download that updates the QSL status for each QSO automatically it does not add QSO's to the logbook

Merge basically updates any missing data