Hello,
I was trying to set up new IOTA group reference trigger by loading my needed IOTA refs from .csv file. I prepared the file (separator is semicolon) and tried to load it with trigger’s IOTA QSO CSV upload button , but it results in “data[0] is undefined” message, and no selection made within IOTA list itself.
Can you provide a sample format for this csv file, or maybe there need to be some bug fix in file data parser after upload.
Thank you!
The expected format is as follows:
"Ref. No.","Callsign","UTC","Count for","Method","Status"
"EU-xxx","CALLSIGN","YYYY-MM-DD hh:mm:ss","HF bands","QSL","Accepted"
"EU-xxx","CALLSIGN","YYYY-MM-DD hh:mm:ss","HF bands","QSL","Accepted"
"EU-xxx","CALLSIGN","YYYY-MM-DD hh:mm:ss","HF bands","QSL","Accepted"
This at least used to be what could be downloaded from the IOTA website. If the format has changed in the meantime, I would be grateful if you could send me a sample CSV, so I can update the parser.
Thanks for reply
But format you provided is a list of already confirmed references plus extra info from IOTA user account, not the needed list as it should be in the case of this HamAlert Trigger.
And there should not be any other information except for just IOTA references needed, I suppose.
I think that’s far enough to have that simple csv file with refs needed with or without header, and after supplying that file, trigger will fill up an internal list of references in trigger’s optionbox.
What do you think?
It’s intended to work the other way around. You download a list of your worked/confirmed references from the IOTA website, upload it to HamAlert, and it will automatically select only those that you are missing.
Manuel, thank you for explaining that. The note down the upload button is not clear at all that I need data of from my account on www.IOTA-world.org.
Well, I did that and it works!
Maybe need to note the source of data in a more clear way in the trigger description in App.
Other than this - all is perfect.
73!
