Versions Compared

Key

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

Summary

  • Teams are syncing

    • Potential issues when categories are missing in Play (manual process to update, not 1:1 with ID)

    • Deleted teams are not being automatically deleted. Script available to manually cleanup

  • Rosters are syncing

    • Photos are not yet syncing

    • Transfer status is not yet syncing

  • Offices are syncing

    • Missing i18n and common name from sync

    • League team relation is not being synced

    • Office parent change and deleted offices are not currently automatically synced

  • Competitions are not syncing

    • While the league offices are syncing, the participating offices/teams/categories within are not yet synced

  • Qualifications are syncing

    • Qualification level must have a display_order

  • Venues are syncing

    • This is synced through Talend

Last updated 2023-09-13

...

  •  Offices v1
    •  ID: API for a list of offices
    •  Play: Manual sync
    •  Play: Setup automatic sync with limit on moves
    •  Play: Use common name
    •  Play: i18n
    •  Play: Deleted/archived offices
  •  Leagues v1
    •  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
    •  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
    •  

...

  •  Teams
    •  ID: API for a list of teams
    •  Play: Automatic sync
    •  Play: Remove deleted teams
  •  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

Participants

Note

Status: Minor blocker for SQ assigners

Play uses clinic attendance for syncing, but SQ doesn’t have clinic attendees.

ID has provided a qualifications API, Play has not yet integrated it

  •  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
    •  Play: Sync qualification categories
  •  Profile information
    •  First/last name and ID
    •  Photo
    •  Contact information
  •  Transfers
  •  Profile Status

Accounts

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

Venues

Tip

Status: Syncing via Talend

Play acts as the primary source of venues and generates externalIds for new venues that Talend uses to sync to other platforms (Splex). No further action is currently considered to be required.

  •  Venues and surfaces
    •  ID: Provide raw data so we can populate Play by March 1st

...

Objective : we need to align what is missing for the integration between play and Id and line up the 2 teams. We need to see if there is a work around for a short period of time and if not what needs to be developped and when

Subject :

  • Current status

  • Tournament

    • Tournament and league structure goes live this week

    • We have built the integration and we will be able to load data in stage this week

    • Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySID-309

  • Splex integration for activities and game sync and activity sync

    • Remove access to PTS

    • Create a form in Jira to ask a field change or adding a field

    • Only Spordle staff will access the fields in PTS

    • Do a cron job to push to Meta location

    • Be able to access the database from

    • We can read from your game table and practice tables to send the data

    • Create a query to see the fields assigned to a game last season

    • Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySID-651

Qualification call ( referees and coach by organization )

...

real names in ID, not only numbers

...

Read from qualification

...

Tomi will verify the call and see if the call is ok

Jira Legacy
serverSystem JIRA
serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
keyHCR-25913

...

Create a new call for validating a coach to a team

  • team id

  • passport

  • list

  • office id of the game (optionnal )

  • Jira Legacy
    serverSystem JIRA
    serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
    keySID-657

...

  • Member profile sync

    • photo

    • status of the profile

    • suspension

    • Mutation

    • Easy report possible everyday to compare members in ID & PLAY?

    • Qualification

    • Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySID-658

  • How do we manage picture

    • Pictures are in the public with the logo

    • Picture resize to a thumbnail

    • Add the logo

    • Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySID-659

  • Review the get team call for Play

    • Return the deleted teams

    • Get teams by last updated date

    • Jira Legacy
      serverSystem JIRA
      serverId03e16d48-9e59-3010-89f5-a1a3500d66b7
      keySID-311

  • Managing the duplicates

...

Page Tree
root@self
startDepth1