Versions Compared

Old Version 1

changes.mady.by.user Tomi Mitrovic

Saved on

compared with

New Version 2

changes.mady.by.user Tomi Mitrovic

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. SID: Create a league/tournament, sync to Play (done)

  2. SID: Add organisations to the league/tournament, sync to Play (missing)

  3. SID: Create competitions, sync to Play as schedules (missing)

  4. SID: Add teams to the competition, sync to Play (missing)

  5. Play: Create games (done)

Models

SID API

SID properties

Play Model

Notes

affiliated-organisations

  • affiliated_organisation_id

  • linked_organisation_id

  • period_id

  • division_id

  • team_category_id

OfficeMember

  • Add seasonId, categoryId, externalId

  • Rollover?

competitions

  • name

  • organisation_id

  • period_id

  • division_id

  • team_category_id

  • start_date

  • end_date

Schedule

  • Identical

  • Dates will be required in SID next season

  • Add externalId

competition-teams

  • competition_id

  • team_id

ScheduleTeam

  • Identical

  • Add externalId

UX

Arrive in Play, all you need to do is create games. ✨

...

(question) How to determine when to limit member/schedule/team creation in Play? Should this be an office flag?

Implementation

Add externalId to OfficeMember, Schedule, ScheduleTeam

...

OfficeMember

Jira Legacy
serverSystem JIRA
serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
keySPR-755

  • OfficeMember: Add seasonId, categoryId

    • This has a similar problem with roster members as SID has a member per position, where Play groups as an array, so we need multiple rows to track the externalId correctly and figure out the UX

  • Authorization will be affected by seasonId/categoryId change

Sync

Jira Legacy
serverSystem JIRA
serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
keySPR-756

  • Add externalId to OfficeMember, Schedule, ScheduleTeam

    • Limit editing for all linked fields