G'day Dan,
Dave T, you're a heavy CSV user... What would you think about adding that to the CSV load logic?
Probably a good idea, particularly while the file structure is expanding / changing on a regular basis and there is the likelihood that people have older version csv files. Currently if there is a new field I perform an export to csv and then manually compare the file structure and then make whatever changes are necessary.
What would probably be even more useful (IMHO) would be to publish on the wiki a simple data model that shows each of the fields, syntax, acceptable values (and whether they are generic or radio specific), as well as any default values (if no entry made). This would help reduce errors made by people manually editing any of the files.
I can probably assist, if no one else wants to, with putting together a draft (after the Xmas lights are up and running) but would need you to vet the data/format for accuracy.
Cheers,
Davidt, VK3UR