Creating Individual Test Files from the Rigel 288
When you import a CSV file containing multiple test results from the Rigel 288, E-Quip creates an individual file for each test within the CSV file and attaches it to the asset being tested. Previously these individual files were named using a combination of the equipment number and the data/time that the import was run:
(where fff represents the number of milliseconds).
The reason that the number of milliseconds is included in the file name is because it is possible for the same device to be tested with the Rigel several times in rapid succession. If the same device was tested twice within 1 minute this would result in 2 files being created with exactly the same name, which Windows will not allow.
The file name extension of “.txt” was chosen because every computer running Windows is able to open this type of file simply by double-clicking on it.
However, some users have requested that these files should be saved with a “.csv” extension. This is reasonable as it not only reflects the internal format of the file, but on computers with Microsoft Office installed, double-clicking a CSV file automatically runs Microsoft Excel, which some users prefer.
As from version 2.1.1 you can now choose which file name extension will be used when creating individual test files.
Note that this has no effect on the actual contents of the file, only the file name extension. The contents are exactly as they were in the original Rigel CSV file
Importing CSV (Comma-Separated Value) Files from Rigel
If you use Med-eBase to manage your Rigel safety test results then you have a powerful application to search through your historical test results. You can link a Med-eBase database to one or more jobs, assets or projects, which makes managing them very simple. But what if you use CSV files instead? You may have spent a week in a particular ward servicing all of their devices and you then have a complete set of Rigel test results that you would like to import.
The problem is (if you don’t use Med-eBase) that you have a single text file containing the test results for possibly hundreds of devices. Searching through a Med-eBase database is one thing, plodding through a text file is not nearly so much fun!
Starting with the next release of E-Quip a CSV file import will be available which will:
1. Read the CSV file downloaded from the Rigel
2. Identify each individual test within that file and create a single file for each.
3. Link each individual test file to the appropriate asset
4. Optionally, create a job to be associated with the test. If this option is chosen it is possible to specify the type and status of the jobs created.
So, if you have 1 file containing 100 test results, E-Quip will create 100 files and link each one as an attached document to the asset that the test relates to, and optionally, create 100 jobs, each with a job test record.
In the example above, where should these 100 new files be created? Different groups of users may have different network shares and different places where they would like to store safety test results. A new Role option Default EST Folder has been added. This specifies the default location for the files created by the EST Import to be written to.
Running the Import
From the right-click menu on the equipment summary screen select the Import Rigel 288 CSV menu. This will display the following wizard.
The operation of this is fairly self-explanatory, but there are a few points you should note:
1. Each test in the CSV file must start with the following two lines:
Tested on (followed by the test date)
Asset ID (followed by the Equipment No)
2. If you choose the Create Jobs option then the 3rd line of the CSV file must be:
Rigel 288 (followed by the tester Equipment No)
3. If the CSV file references an Equipment No which does not exist then a file will be created but this will not be linked to a device, and a job will not be created.
4. If the line “Rigel 288” references an Equipment No which does not exist, or which is not flagged as test equipment, then a job will be created but the Job Test record will not reference the test equipment.
5. The last line of the file must be:
End of Data
We hope that you find this useful. As always, we would welcome any feedback you might have.