... thanks, Kees - and I have my (!) workflow in mind when writing down my ideas.

This workflow has been developed in 50+ years of DXing, and proofed efficient. Well you may also do something 50+ wrong ;-)

I am very open to adapt to other solutions which might please other workflows.

If you work mainly with "strings" an empty database is really fine. But you should have number/time/data formats for these entries.

73 Nils, DK8OK

The logbook is Nils' hobby :-)

I would be very pleased with extending the frequency database with the fields of ILG.
Recently I was struggling in trying to alter the csv-files to manipulate the columns that are imported, but no success for me.
But with an "empty" database or extending the current ILG one with some columns, I would be in SDR's heaven :-)

Was denkts du, Nils ?

Kees,
PA3KVE

-- 
dk8ok.org

... thanks, Simon.

Keeping the logbook separate, is also a good idea to make things even clearer.

The idea behind combining logbook and database keeps the usual workflow in mind:

* track database during current reception
* if you hit one station already enlisted, do a simple entry with all data into the logbook
* if you hit a new one, a new entry is made in this (master) list and can be filled out - either on the fly, or, better, via SQL after importing it

So both approaches will make sense.

Thanks a lot & 73: Nils, DK8OK

Nils,

 

I think I would keep a logbook separate from the Frequency Database as it may be desirable to use an advanced database with replication – SQL Server etc.

 

All other comments noted.

 

Simon Brown, G4ELI
www.sdr-radio.com

 

 

From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Nils Schiffhauer
Sent: 16 October 2018 07:36
To: main@SDR-Radio.groups.io
Subject: Re: [SDR-Radio] Archive XML-file Frequency Database - Format?

 

Hi, Simon (& Kees) - thanks for your early mails ...

The general idea of V3's database should be to support reception (by tracking) and logging (by transferring of current data into a database).
All usual database management should be left to some specialized software like mySQL, FileMake or even EXCEL. From/to there, the user simply has to import/export by CSV.
However, one function should be provided, if possible:
* to query all entries of a specific "Station's name".
Then you can easily run through all parallel frequencies of a specific station.

In my view, a logbook must/should contain the following; first all data already provided by V3:
* frequency, down to one Hz
* Mode
* Filter (bandwidth)
* AGC data
* date
* time
As other data like CW Peak, Noise blanker, Notch and Squelch are mainly depending upon the current propagation, they should be to "Off".

Secondly, you should add some more information to those basic ones; here ILG gives a good template:
* Call sign/ID
* Stations's name
* transmitter's location (name)
* Locator
* Lat/Long (would be nice to have both in one column, plus hyper-linked to Google Maps)
* Name of country
* ITU 3-letter-code of country

* Modulation (ITU calls it: "Emission")
* corresponding channel (QSX)
* Language

* PWR
* Azi

* Target [Region]

* Dist(ance to transmitter)
* PS
* PI

* On/off (one column each to mark the transmission time)
* Days (1234567, to mark the days of activity)
This will be important for a later check against current date and time - to show or to suppress this data accordingly

* Notes
* Reference: Station (a reference to each unique station - for later database management)
* Reference: Log (a reference to each unique log - for later database management)

* Source (eg ILG od DK8OK)
* Added (date)

This hefty list should cover most applications.
Simon's idea of ticking those columns which should be imported, is great. So, the user may reduce the information for his specific needs.

I have a database of 3000+ utility logs from this year (FileMaker), and I would be more than pleased to try any beta version of such a database!

Thanks and 73: Nils, DK8OK

 

Am 16.10.2018 um 05:11 schrieb Simon Brown:

Hi Nils,

 

1.       Please just let me know the ILG (or other database) fields which are not being added, and the field they should be added to. This is a big help.

2.       Please let me know the field you want in the logbook database.

 

Simon Brown, G4ELI
www.sdr-radio.com

 

 

From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Nils Schiffhauer
Sent: 16 October 2018 06:07
To: main@SDR-Radio.groups.io
Subject: Re: [SDR-Radio] Archive XML-file Frequency Database - Format?

 

Hi, Simon and Kees - as I am also very interested in this topic:

* an "empty" CSV import/export option would be a great help
* as ILG seems to cover the most information, its pattern/format should be the guideline

* it would be also excellent, if one can import the current settings of V3 (ie frequency, time, date, mode, bandwidth etc) into a second file. This may work as perfect logbook. It then should additionally cover the ILG dataset

BTW: In the recent Version of V3, column "TX Location" seems to get lost in the conversion process; see annotated screenshot attached.

Thanks and 73: Nils, DK8OK

 

Am 15.10.2018 um 18:17 schrieb Simon Brown:

Hi Kees,

 

I added the XML as an archive / interchange option. I’m busy with ANAN / TX at the moment, I can add a CSV Import / export if that would help.

 

What format is your data in?

 

Simon Brown, G4ELI
www.sdr-radio.com

 

 

From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Kees van Engelen
Sent: 15 October 2018 18:56
To: main@SDR-Radio.groups.io
Subject: [SDR-Radio] Archive XML-file Frequency Database - Format?

 

Hello Simon,

I want to try to feed the Frequency database via the XML Load button.
So I saved a sample (SAVE button) to look what's like.
Now I do not know a lot about XML and stuff, but could you help me with some hints ?

What format / sort XML do you use ? Is it some standard?
I cannot find anything, so a hint would be very nice :-)

73
Kees
PA3KVE

-- 

dk8ok.org

-- 

dk8ok.org

-- 
dk8ok.org

Hi, Simon (& Kees) - thanks for your early mails ...

The general idea of V3's database should be to support reception (by tracking) and logging (by transferring of current data into a database).
All usual database management should be left to some specialized software like mySQL, FileMake or even EXCEL. From/to there, the user simply has to import/export by CSV.
However, one function should be provided, if possible:
* to query all entries of a specific "Station's name".
Then you can easily run through all parallel frequencies of a specific station.

In my view, a logbook must/should contain the following; first all data already provided by V3:
* frequency, down to one Hz
* Mode
* Filter (bandwidth)
* AGC data
* date
* time
As other data like CW Peak, Noise blanker, Notch and Squelch are mainly depending upon the current propagation, they should be to "Off".

Secondly, you should add some more information to those basic ones; here ILG gives a good template:
* Call sign/ID
* Stations's name
* transmitter's location (name)
* Locator
* Lat/Long (would be nice to have both in one column, plus hyper-linked to Google Maps)
* Name of country
* ITU 3-letter-code of country

* Modulation (ITU calls it: "Emission")
* corresponding channel (QSX)
* Language

* PWR
* Azi

* Target [Region]

* Dist(ance to transmitter)
* PS
* PI

* On/off (one column each to mark the transmission time)
* Days (1234567, to mark the days of activity)
This will be important for a later check against current date and time - to show or to suppress this data accordingly

* Notes
* Reference: Station (a reference to each unique station - for later database management)
* Reference: Log (a reference to each unique log - for later database management)

* Source (eg ILG od DK8OK)
* Added (date)

This hefty list should cover most applications.
Simon's idea of ticking those columns which should be imported, is great. So, the user may reduce the information for his specific needs.

I have a database of 3000+ utility logs from this year (FileMaker), and I would be more than pleased to try any beta version of such a database!

Thanks and 73: Nils, DK8OK

Hi Nils,

 

1. Please just let me know the ILG (or other database) fields which are not being added, and the field they should be added to. This is a big help.
2. Please let me know the field you want in the logbook database.

 

Simon Brown, G4ELI
www.sdr-radio.com

 

 

From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Nils Schiffhauer
Sent: 16 October 2018 06:07
To: main@SDR-Radio.groups.io
Subject: Re: [SDR-Radio] Archive XML-file Frequency Database - Format?

 

Hi, Simon and Kees - as I am also very interested in this topic:

* an "empty" CSV import/export option would be a great help
* as ILG seems to cover the most information, its pattern/format should be the guideline

* it would be also excellent, if one can import the current settings of V3 (ie frequency, time, date, mode, bandwidth etc) into a second file. This may work as perfect logbook. It then should additionally cover the ILG dataset

BTW: In the recent Version of V3, column "TX Location" seems to get lost in the conversion process; see annotated screenshot attached.

Thanks and 73: Nils, DK8OK

 

Am 15.10.2018 um 18:17 schrieb Simon Brown:

Hi Kees,

 

I added the XML as an archive / interchange option. I’m busy with ANAN / TX at the moment, I can add a CSV Import / export if that would help.

 

What format is your data in?

 

Simon Brown, G4ELI
www.sdr-radio.com

 

 

From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> On Behalf Of Kees van Engelen
Sent: 15 October 2018 18:56
To: main@SDR-Radio.groups.io
Subject: [SDR-Radio] Archive XML-file Frequency Database - Format?

 

Hello Simon,

I want to try to feed the Frequency database via the XML Load button.
So I saved a sample (SAVE button) to look what's like.
Now I do not know a lot about XML and stuff, but could you help me with some hints ?

What format / sort XML do you use ? Is it some standard?
I cannot find anything, so a hint would be very nice :-)

73
Kees
PA3KVE

-- 

dk8ok.org

-- 
dk8ok.org