Skip to content

Research player discovery and ingestion strategy #46

Description

@Mattsface

Goal

Define the smallest practical player-data ingestion model before building Player analytics.

Questions

  • How should players be discovered for a season?
  • Which stats can be retrieved in bulk vs per player?
  • What request volume does one season require?
  • How should trades/team stints be represented?
  • Do we need season totals, game logs, or both for the first Player views?
  • What should player-ingestion completeness mean?

Constraints

  • Browser remains DB-only
  • Prefer explicit/idempotent ingestion
  • Avoid N+1 player requests when bulk endpoints exist
  • Do not design the schema around a Player chart until the required data grain is known

Completion

Document the recommended discovery path, request profile, persistence grain, and first-step ingestion strategy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions