Daily Change Log

The Daily Change Log updates you on significant changes like schedule adjustments, game results, player updates (such as name or number changes), and team modifications.

⏱️

Update Frequency

TTL / Cache: 300 seconds

Data Updates:

• Entries populate live for changes to teams, players, game statistics, schedules, and standings.
• Start time of the log is 05:00:00 UTC; end time is 04:59:59 UTC

Daily Change Log Scenarios

Post Game Updates and Revisions

The table below outlines scenarios and use cases for utilizing the Daily Change Log for applications that offer live game updates. This log provides updates and stat revisions for recent games.

To use Daily Change Log feed for monitoring changes to recent games:

1. Identify Change Types: First, review the Daily Change Log to identify the types of changes reported. These could be related to games, players, or teams. Each entry in the log will list relevant IDs (game, player, or team ID), depending on the type of change.

2. Use IDs to Retrieve Specifics:

   • Game Changes: If the ID is found within the "results" node, it typically indicates a change in game results. This ID is a game ID.
   • Player and Team Changes: Similarly, IDs associated with players or teams indicate changes relevant to these entities, such as updates to player information or team rosters.

3. Pull Detailed Data: Use the identified IDs to pull detailed information from the relevant feed. For example:

   • Play-by-Play Feed: If a game ID is mentioned, you can pull this feed to check for any new plays added or modifications to existing plays.
   • Game Statistics Feed: Use the game ID to retrieve updated player statistics and team performance metrics to see what specific data was altered.
   • Game Boxscore Feed: Pull this feed using the game ID to review any updates to the game summary, including scores and other significant game statistics.

4. Verify Changes: After pulling the detailed data from the relevant feeds, compare the newly retrieved data against previously stored data to verify the changes and update your records accordingly.

---

Changes to Standings and Rankings

The Daily Change Log can be a helpful tool for tracking potential adjustments to standings and rankings in NCAAFB (though rare). For example, if a game statistic is revised due to a correction or a late reporting of results, the change log will include an entry for the update in its results node

Steps:

1. Identify Change Type: When you encounter an ID within the results node, it signifies that some data associated with the game has been updated. This doesn't necessarily mean the final score has changed, but rather that various game-related details have been modified.

2. Pull Detailed Data: Use the game IDs to pull information from the Postgame Standings and Rankings feeds.

3. Verify Changes: After pulling the detailed data from the Postgame Standings feed, compare the newly retrieved data against previously stored data to verify changes to the standings and update your records accordingly.

Note: While standings and rankings data typically remains stable once games are concluded and results are recorded, rare changes can still occur, such as adjustments following a review of play outcomes or corrections of data errors. You can continue monitoring the Daily Change Log to catch any updates that could impact standings, even though such adjustments are infrequent.

---

Roster Updates

The table below outlines scenarios and use cases for utilizing the Daily Change Log based on team roster and player updates.

Steps:

1. Identify Change Types: First, review the Daily Change Log to identify the types of changes reported. These could be related to games, players, or teams. Each entry in the log will list relevant IDs (game, player, or team ID), depending on the type of change.

2. Use IDs to Retrieve Specifics:

   • Game Roster Changes: If the ID is found within the "results" node, this can indicate a post-game correction to the game roster. This ID is a game ID.
   • Player and Team Changes: Similarly, IDs associated with players or teams indicate changes relevant to these entities, such as updates to team rosters.

3. Pull Detailed Data: Use the identified IDs to pull detailed information from the relevant feed. For example:

   • Team Rosters Feed: If a team ID is mentioned, you can pull this feed to check for any updates to team rosters.
   • Game Roster Feed: Use the game ID to retrieve updated game rosters and to see what specific data was altered.

4. Verify Changes: After pulling the detailed data from the relevant feeds, compare the newly retrieved data against previously stored data to verify the changes and update your records accordingly.

---

Revisions to Seasonal Statistics

The Daily Change Log is useful for monitoring adjustments to NCAAFB seasonal statistics. For instance, if a game statistic that affects seasonal totals is corrected, the log will record this update in its results node.

Steps:

1. Identify Change Type: Spot any game IDs within the results node to signify changes in game-related data or statistics.
2. Retrieve Detailed Data: Use the identified game IDs to pull additional details from relevant feeds such as Game Statistics, Play-by-Play, or Game Boxscore. Game Statistics is recommended for its direct impact on seasonal statistics.
3. Access the Seasonal Statistics Feed: Utilize the team ID obtained from the detailed data to fetch the seasonal statistics.
4. Verify Changes: Compare the newly retrieved data with previously stored records to confirm changes in standings or player statistics. Use the player ID to access the Player Profile feed for deeper analysis of player-specific updates.

---