Here are some common questions we hear about Game Exchange
How is the game data validated?
The Interop .xchange file specification includes support for data that can be used to determine game information. Video editors have the ability to include this information as files are exported. The Vault Exchange Console assists by reviewing this data prior to uploading. If game data can’t be validated users have the ability to update the data and continue the upload process.
The following fields are used to determine the game data:
- Game Date
- Home Team
- Away Team
- Originating Team
We also utilize the NFL team code naming convention to identify our teams. For college football, this is a four-character code denotes the schools name and state it’s located. For example, LAST represents Louisiana State. Using the NFL team code ensures we have consistent data being delivered to our users.
How are ODK assets identified?
The Vault Exchange console scans files prior to upload to determine if it can automatically detect the ODK value. This is done by scanning the names of the files or looking through the .xchange. If a value can’t be determined then the Console will allow you to identify it.
How do you structure the game weeks?
We start the week with week one being any game played prior to the first Monday in September. Week two begins on the first Tuesday after. The game week operates on a Tuesday-Monday cycle to accommodate weekday games.
How are game assets named?
Game assets are named based on the season, week, home/away teams and ODK values. They’ll display differently for the home and away teams based on the version used. Downloaded files will be based on the following convention.
- If the Home team’s version is being used.
- [YY][MM] [Home Team Code] [ODK] [v] [Away Team Code]
- Example: 1911 MABC O vs FLST
- If the Away team’s version is being used.
- [YY][MM] [Away Team Code] [ODK] [@] [Home Team Code]
- Example: 1911 FLST D @ MABC