Versions Compared

Old Version 15

changes.mady.by.user Jean-Philippe Michaud

Saved on

compared with

New Version 16

changes.mady.by.user Jean-Philippe Michaud

Saved on

Key

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

Meeting 2023-03-23

...

  • How do we manage picture

    • Pictures are in the public with the logo

    • Picture resize to a thumbnail

    • Add the logo

  • Managing the duplicate

  • Return the deleted teams

  • Get teams by last updated date

...

Note

Status: Surfaces imported, no automatic syncing

We have a list of surfaces that were manually imported, which allows for scheduling. Might have some issues with data quality as there was a lot of guess work in cleaning up the data.

This is not automatically synced, but we have external IDs stored for the eventuality.

Changing a LOT of venues and fields in PLAY, data needs to be push back to ML.

  •  Venues and surfaces
    •  ID: Provide raw data so we can populate Play by March 1st
    •  ID: API for a list of surfaces
    •  Play: Setup automatic sync
      Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySPR-179

...

  •  Offices v1
    •  ID: API for a list of offices
    •  Play: Manual sync
    •  Play: Setup automatic sync with limit on moves
  •  Leagues v1
    •  Office member sync (associations and categories that are part of a league or tournament)
      •  ID: API for a list of office members
        Jira Legacy
        serverSystem JIRA
        serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
        keyHCR-25907
      •  Play: Setup automatic sync
        Jira Legacy
        serverSystem JIRA
        serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
        keySPR-244
    •  Team members (teams that are part of a league or tournament)
      •  ID: API for getting a list of teams
        Jira Legacy
        serverSystem JIRA
        serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
        keyHCR-25909
      •  Play: Setup automatic sync

...

  •  Teams
    •  ID: API for a list of teams
    •  Play: Automatic sync
  •  Rosters v1
    •  ID: API for a list of members by team
    •  Play: Sync roster members for each team (inefficient)
  •  Rosters v2
    •  ID: API for a list of roster members by office search (not by team)
      Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keyHCR-25911
    •  Play: Update automatic sync to use new API

...

  •  Officials v1
    •  ID: API for a list of clinic attendees
    •  Play: Automatic clinic sync
  •  Officials v2
    •  ID: API for a list of officials and their qualifications by office search
      Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keyHCR-25913
    •  Play: Update sync
      Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySPR-142
  •  Profile information
    •  First/last name and ID
    •  Photo
    •  Contact information
  •  Mutations
  •  Profile Status

...

Note

Status: Not integrated. Workable, but awkward introduction

Play has not yet integrated with My Account. Officials and teams can create an account and log in without too much trouble, but it’s not the single sign-on we promised.

  •  My Account: Documentation for how to authenticate and get profile information
  •  ID: Revisit permission discussion for administrator onboarding
  •  Play: Integrate log in with My Account

...