...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
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. |
...
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
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 have been able to stumble along without a full league sync for now as leagues can add any team to a schedule easily in Play. |
- 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
- Office member sync (associations and categories Team members (teams that are part of a league or tournament)
- ID: API for getting a list of office membersteams
Jira Legacy server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCR-2590725909 - 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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key SPRHCR-24425907 - ID: API for getting a list of teamsPlay: Setup automatic sync
Jira Legacy server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCRSPR-25909244 - Play: Setup automatic sync
Teams
Tipinfo |
---|
Status: Working, opportunity for improvement We already have teams and rosters syncing, no rush here. This is just to improve efficiency. |
- 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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key HCR-25911 - Play: Update automatic sync to use new API
Participants
Noteinfo |
---|
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 exportsWorking, opportunities for improvement Teams and officials are syncing well, just need to improve syncing profile data. Minor issue with merged profiles in SID not being notified in Play. |
- 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 - Play: Sync qualification categories
- Profile information
- First/last name and ID
- Photo
- Contact information
- Transfers
- Profile Status
- Merged members
Accounts
Notewarning |
---|
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
...
Page Tree | ||||
---|---|---|---|---|
|