Meeting 2023-03-23
...
Current status
Splex integration for activities and game sync Venues updates and creation and 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
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
Create a new call for validating a coach to a team
team id
passport
list
office id of the game (optionnal )
Member profile sync
photo
status of the profile
suspension
Mutation
Easy report possible everyday to compare members in ID & PLAY?
Qualification
How do we manage picture
Pictures are in the public with the logo
Picture resize to a thumbnail
Add the logo
Get teams by last updated date
Offices and teams and players sync need to be way faster
Fields editing and push back to ML
Fields unavailabilities need to be simplified
Venues
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 server System JIRA serverId 03e16d48-9e59-3010-89f5-a1a3500d66b7 key SPR-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 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
...
- 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
...
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
...