Skip to main content
Schema: flow.nft Table: dim_allday_metadata Type: View

Description

Comprehensive metadata for NFL All Day Moments, including player information, team details, statistics, and rich content data. This table is produced via API integration and provides detailed information about each NFL All Day NFT moment, including play descriptions, video URLs, and comprehensive statistics. The data structure may differ from on-chain metadata available in other tables, providing a more complete and curated view of NFL All Day moments.

Key Use Cases

  • Analyze NFL All Day moment performance and market activity
  • Track player and team-based NFT analytics
  • Power NFL All Day dashboards and user-facing applications
  • Support content discovery and moment exploration
  • Enable player and team-based market analysis

Important Relationships

  • Can be joined with nft__ez_nft_sales for sales analytics
  • Links to nft__dim_moment_metadata for on-chain data comparison
  • Player and team data enables cross-platform athlete analysis
  • NFL All Day ID enables direct marketplace integration

Commonly-used Fields

  • nft_id: Unique identifier for the NFL All Day moment
  • nflallday_id: Official NFL All Day identifier for marketplace integration
  • player: Athlete featured in the moment
  • team: Team affiliation at time of moment
  • season: NFL season when moment occurred
  • set_name: Collection set name for organization
  • total_circulation: Maximum supply for rarity analysis
  • moment_description: Detailed play description

Columns

Column NameData TypeDescription
NFT_IDTEXTThe unique identifier for the NFT within its collection. Data type: STRING or NUMBER. This field uniquely identifies a specific NFT token within a collection, typically representing the token ID or serial number assigned during minting. Used for NFT-level analytics, tracking individual token movements, and joining with metadata tables. Example: ‘12345’ for TopShot moment #12345, or ‘A.1234567890abcdef.Moment#456’ for a specific moment. Important for NFT tracking, sales analysis, and metadata joins.
NFT_COLLECTIONTEXTThe contract address or identifier for the NFT collection on the Flow blockchain. Data type: STRING. This field identifies the smart contract that manages the NFT collection, enabling collection-level analytics, filtering, and protocol attribution. Used for grouping NFTs by collection, tracking collection performance, and joining with metadata tables. Example: ‘A.e4cf4bdc1751c65d.AllDay’ for NFL All Day, ‘A.87ca73a41bb50ad5.TopShot’ for NBA TopShot. Important for collection analytics, marketplace filtering, and cross-collection comparisons.
NFLALLDAY_IDTEXTThe unique identifier used by NFL AllDay for the moment. Data type: STRING. This field provides the official NFL AllDay identifier for the moment, enabling direct linking to the marketplace and cross-referencing with external NFL AllDay data. Used for marketplace integration, external data joins, and direct user navigation to moments. Example: Can be used in URL https://nflallday.com/moments/{nflallday_id} to view the moment on the marketplace. Important for marketplace integration, external data correlation, and user experience features.
SERIAL_NUMBERNUMBERThe serial number or edition number of the NFT within its collection. Data type: NUMBER. This field represents the specific edition number of the NFT, indicating its position within the total circulation of that particular moment or token. Used for rarity analysis, edition tracking, and determining the uniqueness of NFTs within a collection. Example: 25 for the 25th edition of a moment, 1 for the first edition. Important for rarity calculations, edition-based analytics, and determining NFT scarcity within collections.
MOMENT_TIERTEXT
TOTAL_CIRCULATIONNUMBERThe total number of NFTs minted for the particular play or moment. Data type: NUMBER. This field represents the maximum supply of NFTs for a specific moment, enabling rarity calculations, scarcity analysis, and market supply understanding. Used for rarity analysis, supply-side market analysis, and determining the relative scarcity of NFTs within a collection. Example: 1000 for a common moment, 10 for a rare moment. Important for rarity calculations, market supply analysis, and understanding NFT scarcity and value drivers.
MOMENT_DESCRIPTIONTEXTA detailed, long-form description of the play or moment captured in the NFT. Data type: STRING. This field provides a comprehensive narrative description of the sports play, including context, key details, and notable aspects of the moment. Used for content discovery, play identification, and providing rich context for NFT analysis. Example: ‘LeBron James hits a game-winning three-pointer with 2.1 seconds remaining in the fourth quarter.’ Important for content discovery, play identification, and providing rich context for NFT transactions and analytics.
PLAYERTEXTThe name of the athlete or player featured in the NFT moment. Data type: STRING. This field identifies the sports figure who is the primary subject of the NFT, enabling player-level analytics, performance tracking, and fan engagement analysis. Used for player attribution, performance correlation with NFT values, and fan behavior analysis. Example: ‘LeBron James’ for NBA TopShot, ‘Tom Brady’ for NFL All Day. Important for player-based analytics, fan engagement tracking, and athlete performance correlation with NFT market activity.
TEAMTEXTThe sports team that the player represented at the time the NFT moment was captured. Data type: STRING. This field identifies the team affiliation of the featured player, enabling team-level analytics, regional market analysis, and team performance correlation with NFT values. Used for team attribution, regional market analysis, and team-based fan engagement tracking. Example: ‘Los Angeles Lakers’ for NBA TopShot, ‘Tampa Bay Buccaneers’ for NFL All Day. Important for team-based analytics, regional market insights, and team performance correlation with NFT market activity.
SEASONTEXTThe sports season during which the NFT moment occurred. Data type: STRING. This field identifies the specific season when the moment was captured, enabling temporal analysis, season-based performance tracking, and historical trend analysis. Used for season-level analytics, performance correlation across seasons, and historical NFT value analysis. Example: ‘2021-22’ for NBA season, ‘2022’ for NFL season. Important for temporal analysis, season-based performance tracking, and understanding how NFT values correlate with seasonal sports performance.
WEEKTEXTThe week of the NFL season during which the game occurred.
CLASSIFICATIONTEXTThe broad category of play that is shown in the moment.
PLAY_TYPETEXTThe more granular (than play_category) type of play that is shown in the moment.
MOMENT_DATETIMESTAMP_NTZWhen the moment occurred.
SERIESTEXTThe series for this particular set of drops.
SET_NAMETEXTThe name of the NFT set or series in which the moment was released. Data type: STRING. This field identifies the specific set or collection within a broader NFT project, enabling set-level analytics, rarity analysis, and set performance tracking. Used for set attribution, set-based market analysis, and understanding the organizational structure of NFT collections. Example: ‘Base Set’ for TopShot, ‘Genesis’ for All Day. Important for set-based analytics, rarity calculations, and understanding the hierarchical structure of NFT collections.
VIDEO_URLSARRAYAn array containing links to the moments.
MOMENT_STATS_FULLOBJECTA dictionary of the full moment stats.
DIM_ALLDAY_METADATA_IDTEXTpk_id is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt.