Analyzer allows you to import data to improve functionality and ensure access to up-to-date information. It provides several import options, making it easy to keep your database current.
- Importing match text files from your Local Drive or the Cloud
- Syncing your database with a table in the cloud
- Importing CSV Files
- Database conversions supplied by Fair Play
- Importing Ball Tracking Data
Importing Match Text Files from your local drive or the cloud:
To import a match txt file from your local drive, following these simple steps:
- Open Analyzer and select Match>Import>From Text File…
Image 1: Importing a match text file from your local drive
2. Find the match text file in the folder where you first saved it, then click Open
3. Highlight the match/es that you wish to import and click Import
Image 2: The Import Match Text File window
4. Click Ok on the completion window when the import process has finished
To import a match txt file from the cloud, following these easy steps:
- Open Analyzer and select References>Matches>Import>From Cloud…
Image 3: Importing a match text file from the cloud
2. Select the match/es that you wish to import into your database, press OK
Image 4: Selecting the matches you wish to import
3. Highlight the match/es that you wish to import and click Import
Image 5: The Import Match Text File window
4. Click Ok on the completion window when the import process has finished
Syncing your database with a table in the cloud:
The cloud system stores tables for matches, players, venues, coaches, and officials, and these should be kept in sync with your database. Each row is colour-coded to show its status—whether it is already synced, needs to be imported because it differs from the cloud, needs to be exported after a local update, or is missing from your local database.
Note that Exporting data is covered in another Zen Desk article ‘Exporting Data’:
The Colour Codes:
| Colour | Status | Additional Comments |
Green |
Currently synced to the cloud | No action required |
Red |
Local v Cloud difference detected | Determine whether an import or export is required by the Local v Comparison column. WARNING: Be careful to determine whether your data should update the cloud or whether the cloud should update your database. Maintaining data integrity is essential. |
Yellow |
Missing from your local database | Import from the cloud |
Regularly syncing your database to the cloud is strongly advised. Doing so helps you easily preserve your database’s integrity in Analyzer and ensures you always have access to the most up-to-date data.
To Sync your database with a table in the cloud: (The Matches Table for this example)
- Launch Analyzer, choose Reference>Matches> and select Synce with Cloud…
Image 6: The tables within the cloud that can be synced with your database
2. Once the ‘Set Up Matches’ Window appears, filter to the required matches on the top drop-down options and tick the include Cloud box at the bottom left-hand corner. The table will automatically load when you tick the include Cloud box.
Image 7: Matches that require action to sync to the local database
Image 8: The far-right columns of Image 7 showing the Local v Comparison Column
3. Click on the 'Local v Comparison' column header shown in Image 8 to group the table rows by colour which facilitates your determination on what needs to be synced with your database.
Note the following from the example in Image 8:
- The yellow-coloured grouping requires the import of the rows as the row detail indicates that this information or matches are missing from your local database
- The red coloured grouping in the Local v Comparison Column show what is in your database compared to the cloud. Local (your database) = CricInfo: blank space (so no data in your database) v ‘224180’ (what is recorded in the cloud). It’s evident that you should import these two matches into your local database, as this information is currently missing from your records. For the ‘Virtual Eye’ row, you need to export your match data to the cloud because it will replace much older data.
- The green coloured grouping requires no action as your details sync with the cloud.
4. To import any entry from Image 7 or 8, highlight the desired row/s and select the ‘To Cloud’ or ‘From Cloud’ button located at the bottom of the window. Please note that Analyzer will automatically determine and enable the appropriate button when it is clear whether data should be imported or exported to your database. For example, the ‘To Cloud’ button may appear inactive under certain conditions as shown below.
Image 9: After the selection of matches, Analyzer may automatically select ‘From Cloud’ to update your database
Note: The Analyzer may not always select the optimal option automatically. Exercise caution to avoid overwriting current cloud data with outdated information. For instance, when selecting the third red row from image 8, Analyzer presents both cloud button options. It is essential to determine whether to import or export data, as this choice will affect the integrity of the cloud and other user’s databases.
Image 10: Analyzer allowing the user to choose the ‘To Cloud’ or the ‘From Cloud’ button when selecting a row
5. Click on the Close button to exit the Syncing window
To import CSV files to your database:
This tool in Analyzer is helpful when you need to import specific data into a match file. For example, if bowling speeds have been recorded using a speed gun and saved in a CSV file, you can import this data into Analyzer to update the bowling speeds for a particular match.
To import a CSV file into Analyzer, following these simple steps:
- Open Analyzer. Select References>Matches>Import>From Ball Speed CSV
Image 11: Importing a CSV file into Analyzer pathway
2. Select your CSV file, highlight the row and click Import and Yes that you wish to proceed
Image 12: The Import CSV window
3. Click on OK to finish and the Close Button (Image 12) to exit the CSV import process
Note: In order to import a CSV file, Analyzer will require and prompt you when importing your selected CSV file if the file needs to be edited before import. This usually means columns headings and the right data values. See the image below and a link to a Zen Desk ‘Tips and Tricks’ Article for the correct format for a ball speed CSV file – see here (currently under development)
Image 13: The error report window
Database Conversions supplied by Fair Play
This process is vital for maintaining an accurate and current database. Fair Play provides regular database conversions through their software updates. These conversions typically include the removal of duplicate players, matches, and venues, along with other essential updates to the data tables stored in the cloud. This method offers the most efficient and effective approach for importing or preserving the data in your database.
We strongly recommend keeping Analyzer updated so you receive the latest database conversions.
Click here (currently under development) for instructions on updating your Analyzer Software.
Image 14: An example of a Database Conversion delivered by Fair Play
Importing Ball Tracking Data
Another key importing process ensures our data set is comprehensive and supported by third-party ball tracking providers. For more details, see the Zen Desk article ‘3rd Party Ingestion’ – see here (currently under development).
0 comments
Please sign in to leave a comment.