Program AWARD_SECRETARY performs two types of checks data in the imported file .adif
This check is done both if you selected data from the logger or the data is passed through page CLUBLOG
The program AWARD_SECRETARY is equipped with a control mechanisms correctness for every field adif in the imported ADIF file. adi This check is made using a special technology, programming RegEx Regular Expression based on the so-called pattern of the field. This technology is new to Windows programming technology and provides a high possibility of finding errors. There are found : ordinary errors and so-called critical errors which may cause stop the program or give erroneous results. In the event of critical errors further work program is suspended. Adjustments must be made for critical errors in the logger and again to produce a file of .adi. Some errors as far as possible will be corrected automatically .After selecting a file of adif in the previous section, the following window will appear.
| Windows with error messages when you select
a file ADIF to import from looger |
Errors that the program found is consist of two types
1. | Errors ordinary, which probably will not cause a malfunction program AWARD_SECRETARY . |
2. | Critical errors which may then cause erroneous operation of the program or give erroneous results. There belong here also too long length fields, what not fit in the declared lengths of the fields in MySQL. In this case of an on-screen appears this message |
| The message of the occurrence of critical errors.
Further work program is not possible |
In the case of critical errors occur when you press OK, admittedly remain in the program, but we should exit the program by pressing
The final screen after the initial load of data may look like
| The finish scren after preliminary load adif file |
From this screen, we see that all Polish characters will be replaced by the ASCII characters .This is forced by international using AWARD_SECRETARY program. Also in the windows of the information that report from errors is stored in two files .
• | Error_critical_report.txt |
• | Error_report.txt , which you can then view and take appropriate actions, mainly based on the edit the data in a logger and produce the new adi file. |
If there are no critical data is a further process step is as bellow :
Buttons for choice
After choice Delete all existing QSO and awards - Enter New data appear
A warning message that all
data and tables will be cleared
After choice the Enter /Update QSOs will appear
| Window on the course to update or
insert new records |
| Create auxiliary file |
| Screen for the end of update or insert QSOs |
|
Before loading a file adif to page CLUBLOG is done first selecting the file to upload described here, and check all the fields with the pattern Regular expresssion described here. As we see the file ADIF for upload was selected earlier than we will actually upload to the site CLUBLOG. Below I will show you how to automatically this name file will be used for upload without re-choice file adif .This check for entities is performed only if the file adif was loaded to the page CLUBLOG, and then compared.
In this method for the first time run , appears to us first special browser pages for uploading adif file and download file after the calculations performed on the server CLUBLOG .However, before appearance of a the browser appears for a short time preliminary window
In this release introduces a new browser for viewing web pages. In the previous version of the browser call Internet Explorer, which, however in the current version of IE 11.0 was stripped of services the pages in HTML5 standard .The new website CLUBLOG's were written in HTML5 - so with this version introduces a new browser Browser_chrome.exe It is written using elements browser Chrome by Google. However, it not depends from the Chrome browser, because all the necessary components are present in the form of dll files are included in the program directory AWARD_SECRETARY . So that changes in Chrome will not affect the operation of the program. Because all services for windows to upload file ADIF is included in the page code in JavaScriopt, which I have no control, I had to use quite a breakneck tricks included in the Window API. Therefore, when you start Browser_chrome.exe , you will get us the following preliminary window. This dialog box appears only for about 2 - 3 seconds and automatically disappears. But on slow computers might not disappear, and then you must press the CANCEL button. It may look like
- for Windows Vista and Windows 7 as follows
| Preliminary window for Browser_chrome.exe for
Windows Vista and Windows 7 |
- for Windows XP , Windows 2000 and earlier
| Preliminary window for Browser_chrome.exe for
Windows XP and Windows 2000 |
Then we will see a browser with the web CLUBLOG in which we can be logged (cookies). Login you must do with a full e-mail address.
|
|
Browser.exe program for handle web CLUBLOG.
Here is shown login to your account. Bring a login
use the full email address. If we do not have
account created can also register here |
When you press Login Now will see a page
|
Browser._chrome.exe program for handle web CLUBLOG.
Here is shown the page after logging in. This site may
appear to us as the first if you have previously logged
and have already been set cookies |
If you have previously been loaded a file to the web page CLUBLOG you can seee yourself one of two possible messages
lub
Upload ADIF file to the server CLUBLOG
Uploading the file is described detail in the inside Browser
| First page to upload a file ADIF to CLUBLOG server.
Detailed descriptions in the picture |
| Automatic selection file and directory for
uploading to the server CLUBLOG. After selecting
this window will be closes automatically |
| Page second to upload file ADIF to the server CLUBLOG.
Detailed descriptions on the picture. |
After loading a file to the server by pressing Submit CLUBLOG Upload for , we have the possibility to stay in Browser or exit from it and then you can also Exit from the program.
| Third page to load a file of ADIF (upload) to CLUBLOG server.
Description detailed in the picture |
Now you must observe your e-mail box , to which you should come an e-mail titled Feedback on upload for SP9AUV .You can show it briefly , although this is not necessary, since the main differences you can display on the screen by program AWARD_SECRETARY . If we had not been included there same QSO, and we have already confirmed it by QSO card, you should reported this QSO to CLUBLOG. Specific links to the different situations of the QSO are in the e-mail.
|
|
Download file ADIF after correcting from CLUBLOG server
If you exit from the program without waiting for a e-mail, and then we launched it again, you will show yourself this message
After its approval, will be show to us Browser and there you should choose SETTING
| Page downloading a revised file of ADIF
Detailed descriptions in the picture. |
| Download file after corecting -from CLOBLOG
Detailed descriptions on the picture |
| Chose diretory and name file is proposed
by program .You have to leave the choice that
has been made by the program |
| Proggres in the download adif file |
| Close Browser |
After closing Browser will be read the data from the two files of as you see bellow . We can here click on the small box Display record what will display of QSOs. This is useful when we have a file with some errors. If this error occur , the program stops after checking to the end of the file , and we definitely should open your file of in a text editor and correct the invalid field, but preferably do this in the logger and again produce file .
f
| No existing QSO - not accepted by CLUBLOG
and duplicate QSO also not accepted by CLUBLOG
But for duplikcate QSO parameters for entities
is determined on the basis of which is the base
for the QSO duplicat |
If there are any difference between your file .adi from the logger's and a file obtained from .adi CLUBLOG , these differences, and their sum will be displayed in the window
| Differencies between the data on the Entities
No Adif, CQZone, ITUZone from the logger and the
data from CLUBLOG website. You now do
decision whether to continue or interrupt
and once again perform the above steps |
Let us analyze these results:
• | only two QSOs have different ADIF_NO . .It is a QSO with an invalid character 2IOVFO and others |
• | 280 QSOs has a different CQZone from Logger and CLUBLOG . The first part data comes from Logger32 - for which CQZone is not determined on the basis of CLUBLOG .Logger32 has its own method of determining the CQZone. Logger32 remembers the calculated CQZone and ITUZone from the past and they never changed even if you do recalculation. CQZone was not always good, especially if QSOs were imported from other logger's. So the result considered 280 different should be good. |
• | 1226 differences for ITUZone when AWARD_SECRETARY takes this data based on an old file of CTY.XML, should not be considered as bad. However, if you will required to notify to the award for ITUZones area, I recommend checking the results in the QSL card. |
• | I recommend reviewing before continuing the work check two files: Error_report_adif.txt and eror_report.txt. There may be especially QSO for old Russian station , that the same prefixes have been used for other zones CQ (oblast) in the past. The best in this case, see the QSL card and see what gives QSL card for the country, CQ Zone, ITU Zone. Corecting should be made in the looger's and over again produce a file .adi |
If there are errors in the data in the window as below, ie when comparing data CLUBLOG (they occur very rarely)
|
|
|
Continuing point 2.
Steps to take when you want to load or updating the QSO data
we have two Buttons to enter data into an table
• | first button which will delete all records QSOs from the and removal of all tables for awards . This button should only use only when the 1st reading data from the logger or if we want removing all of our tests on awards . Loading data is here do by the fast hurt method . When you select this button, you are see . |
|
|
A screen with information that
will be deleted all the awards
and auxilary tables |
|
Ekran for hurt import data |
|
End of hurt impor data |
|
The main screen after reading data to QSOS_AWARDS |
• | Second button is used to enter data with correction data (update) from the file QSO records obtained from the file . are checked in the existing table . If the record QSO exists in the table then all fields are corrected according to the fields in the imported file .adi. If a record does not exist in the table qsos_awards, then to this table is added a new record. As an indicator that the QSO is in the table is assumed compliance conformity of the following fields in the file adi and table |
|
• | field TIME_ON This field is also used to search for the same QSO - this means that if we make the correction in the QSO data TIME_ON time up to 1 sec. it is another QSO. Old QSO with the previous time is also remembered - as AWARD_SECRETARY can mark this QSO as assigned to any award . It is not recommended to make in in the logger making such correction as may be the reason for the erroneous behavior of the program AWARD_SECRETARY |
Program to check whether there is the same QSO searches it in the at each QSO. It is not used as a marker of the same QSO QSO number (which would give a faster correcting QSOs) - because it may was changed in a logger ( renumber ) .This approach provides a way that QSO can be loaded onto the existing fixed QSO - because we receive QSL card for this QSO . . But this safe way correcting QSO - results in a way slower update table .
If you click this button get the possibility to choose the ADIF file as above, and an information window on the adjustments of ADIF number. Then you will see
|
Window on the progress upadte or
insert new records |
|
End of the update process
or insert records |
The main screen for table QSOS_AWARDS after loading the data looks like in the previous picture that can contain more rows of data