Analyzer has several ways to import data, so your database stays current and you're always working with up-to-date information. This article covers each of them.
In this article
- Importing match text files
- Syncing your database with the cloud
- Importing CSV files
- Database conversions from Fair Play
- Importing ball-tracking data
- Where to go next
Importing match text files
From your local drive
- In Analyzer, select Match > Import > From Text File…
- Find the match text file in the folder where you saved it, and click Open.
- Highlight the match or matches you want to import, and click Import.
- Click OK on the completion window when the import has finished.
From the cloud
- In Analyzer, select Reference > Matches > Import > From Cloud…
- Select the match or matches you want to import into your database, and click OK.
- Highlight the match or matches to import, and click Import.
- Click OK on the completion window when the import has finished.
Syncing your database with the cloud
The cloud stores tables for matches, players, venues, coaches and officials, and your database should be kept in sync with them. Syncing regularly is strongly recommended: it protects the integrity of your database and means you always have the latest data.
In the sync window, each row is colour-coded by its status:
| Colour | Status | What to do |
|---|---|---|
| Green | Synced with the cloud | Nothing. |
| Red | Your database and the cloud differ | Use the Local v Comparison column to decide whether to import or export (see below). |
| Yellow | Missing from your database | Import from the cloud. |
Decide carefully which way each red row should go. Exporting overwrites the cloud, and with it every other user's data; importing overwrites your database. Check whether your data should update the cloud, or the cloud should update your data, before you click.
Exporting data is covered in its own article, Exporting Data.
How to sync a table
This example uses the Matches table; the other tables work the same way.
- In Analyzer, select Reference > Matches > Sync with Cloud…
- In the Set Up Matches window, filter to the matches you need with the drop-downs at the top, then tick Include Cloud at the bottom left. The table loads automatically.
- Click the Local v Comparison column header to group the rows by colour, so you can see what needs syncing.
- Highlight the rows you want to sync and click To Cloud or From Cloud at the bottom of the window. Where the direction is clear, Analyzer enables only the right button.
- Click Close to exit the sync window.
Reading the Local v Comparison column
In this example:
- Yellow rows are matches missing from your database, so import them.
-
Red rows show your value against the cloud's. Two
rows have a blank Cricinfo ID locally against
224180in the cloud, so import those to fill the gap. The Virtual Eye row is the opposite: your data is newer than the cloud's, so export it. - Green rows already match the cloud and need nothing.
Analyzer doesn't always pick the right direction. For the third red row in the example, it enables both buttons, and the choice is yours. Don't overwrite current cloud data with older information.
Importing CSV files
Use a CSV import to add specific data to a match. For example, if bowling speeds were recorded with a speed gun and saved as a CSV file, you can import them to update the speeds for that match.
- In Analyzer, select Reference > Matches > Import > From Ball Speed CSV.
- Select your CSV file, highlight the row, click Import, then Yes to confirm.
- Click OK to finish, then Close to exit.
If the file isn't in the right format (usually the column headings or the data values), Analyzer shows an error report telling you what to fix before it will import. The correct format for a ball speed CSV file will be covered in a Tips and Tricks article, which is still being written.
Database conversions from Fair Play
Fair Play delivers regular database conversions through Analyzer's software updates. They usually remove duplicate players, matches and venues, along with other essential updates to the cloud tables. They're the most efficient way to keep your database accurate and current.
Keep Analyzer updated so you receive the latest database conversions. See Installation, Licencing & Updating Analyzer for how.
Importing ball-tracking data
Importing data from third-party ball-tracking providers makes the data set more complete. This will be covered in its own article, 3rd Party Ingestion, which is still being written.
Where to go next
- Exporting Data: sending your matches and table updates to the cloud.
- Installation, Licencing & Updating Analyzer: keeping Analyzer up to date.
- Running AthletesAI after a match: importing AthletesAI ball-tracking for a coded match.
0 comments
Please sign in to leave a comment.