Meeting 2023-03-23
...
| 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. |
- 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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key SPR-179
...
| Info |
|---|
Status: Partially functioning Currently a manual sync since BC Hockey offices didn’t change very much, but now that we have leagues, Play needs to setup an automatic sync. Leagues, members and teams are new in SID, so that’s a new API that hasn’t been integrated in Play yet. We can stumble along without a full league sync for now as leagues can add any team to a schedule easily. |
- 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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCR-25907 - Play: Setup automatic sync
Jira Legacy server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key SPR-244 - Team members (teams that are part of a league or tournament)
- ID: API for getting a list of teams
Jira Legacy server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCR-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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCR-25911 - Play: Update automatic sync to use new API
...
| Note |
|---|
Status: Minor blocker for SQ assigners Play uses clinic attendance for syncing, but SQ doesn’t have clinic attendees. Need an API to sync data directly, but we can stumble along with data exports. 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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCR-25913 - Play: Update sync
Jira Legacy server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key SPR-142 - Profile information
- First/last name and ID
- Photo
- Contact information
- Mutations
- 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
Integration
| Warning |
|---|
Status: New work, not yet planned Play has the ability to sync games to other systems. Currently this was designed for an Assignr sync for PCAHA, but it’s feasible to extend this to other systems. |
- Integrate with Splex