search

AthletiFi / athletifi-website

Official website for AthletiFi
https://www.athleti.fi
1 stars 5 forks source link

Start loading in REAL player data #320

Open qisforq opened 3 weeks ago

qisforq commented 3 weeks ago

Player names, parent emails, Placeholder card image, etc

qisforq commented 2 weeks ago

summer_select_signups.csv

chef-louis commented 2 weeks ago

Loaded 66 players into player_identities table. A couple items of note:

Follow-up questions:

  1. 66 players total (5 more than initially thought) -- is that correct?
  2. What should we use as the slug handle for Summer Select? ss-24?
  3. Do we have QR code mappings to card_ids that we need to follow (similar to what we had to do for vsa-23)?

To-do items:

qisforq commented 2 weeks ago

66 players total (5 more than initially thought) -- is that correct?

Hmm, it looks like 66 is actually correct now (that's what the AthletiFiSelectSignups excel sheet is showing now as well). We did have some last minute signups, and I guess they didn't get pulled into the excel sheet at the time I shared the 61 figure with you.

What should we use as the slug handle for Summer Select? ss-24? I was about to suggest the abbreviation for AthletiFi Summer Select, but after seeing it written out, ss-24 is definitely the way to go 😂

Or we can make it more human readable and do summer-select-24?

Do we have QR code mappings to card_ids that we need to follow (similar to what we had to do for vsa-23)?

Nope, the issue last time is that the cards were printed before the application existed, so we had to make a best guest to how the url's would be crafted. This time around we will create the QR codes afterward

chef-louis commented 2 weeks ago

summer-select-24 it is!

Makes sense on the QR codes. Thanks for the context.

chef-louis commented 2 weeks ago

@qisforq More follow-up notes/questions by table

public.clubs

public.league

public.teams

public.coaches

public.team_coaches

public.players_team_info

public.player_card_images

chef-louis commented 2 weeks ago

Basic data entries made to the following tables for all 66 players:

data points left blank where appropriate and/or filled in with placeholder values for now. Will update based on responses above.

qisforq commented 2 weeks ago

public.clubs

  • What is the location?

Glenside, PA

public.league

  • Not sure for this one. Is this some generic AthletiFi Summer Select League?

Good question! Perhaps just put 'independent'?

public.teams

  • With the 66 player roster, how many teams does this represent and what are their names (ie. Summer Select U12, Summer Select U14, etc)?

For the tournaments we have them listed as 3 teams: Athletifi Select '11, AthletiFi Select '12, AhtletiFi Select '14. Just FYI all the players with 2012 or 2013 birth years go into AthletiFi Select '12, and all the players with 2014 or 2015 birth years go into AthletiFi Select '14. Not sure if we need to, buy we may want to separate by boys and girls. If so we can make AthletiFi Select '12G or AthletiFi Select 12 Girls, etc.

public.coaches

  • It looks like there are 4 coaches in total (Darren John, AJ, Brian and Justin -- I don't have last names for the last 3 so left blank for now)

AJ is actually Ashley Johnson. Perhaps put his first name as Ashley "AJ", so that way the full name gets rendered as Ashley "AJ" Johnson. Then it's Brian Blasy and Justin Johnson

public.team_coaches

  • Using the responses from above, what are the mappings of teams <> coaches? If this is fluid, what inputs should I use here for now?

public.players_team_info

  • I can fill in most of this table with the initial player dataset and questionnaire, but currently missing player numbers (will leave blank for now)

I have some of the jersey numbers written down on the attendance sheet from the practices this week, but not all because not everyone has received a shirt yet. I will update you when I get this info digitized.

public.player_card_images

  • I'll leave card_image_url blank for now
  • Any preference for how to arrange dashboard_slug? Is a sequential ordering of slug okay (ie. alphabetically increasing example summer-select-24/1, summer-select-24/2, summer-select-24/3, etc.)?

I think a sequential ordering should be fine. That is how we handled the last collection. Whatever you think is best!

chef-louis commented 2 weeks ago

Great, thanks @qisforq. I've incorporated your edits into the database

To summarize where we are, we have incorporated the player data that we have (still missing some player's info/bios where questionnaire wasn't filled out). The remaining to-do items for filling in data include the following:

chef-louis commented 2 weeks ago
qisforq commented 5 days ago

Match videos from Hershey were uploaded https://us-east-2.console.aws.amazon.com/s3/buckets/athletifi-s3?region=us-east-2&bucketType=general&prefix=match_videos/

I'll add them into the database as well

chef-louis commented 4 days ago

@qisforq It looks like the lambda function for uploading S3 videos into Mux didn't run properly. Taking a look into why that failed and then will retrigger

chef-louis commented 4 days ago

It takes Mux a very long time to process the full length match videos (30+ minutes). The path forward here is to de-couple the upload of videos to Mux and writing the relevant video details to our postgres database once the Mux upload is fully processed.

chef-louis commented 4 days ago

Mux videos have now successfully loaded (most taking between 30 minutes and 1 hour to process) and relevant data entries into full_match_videos have been written by a manual run of the lambda function.

match_result_ids have also been mapped appropriately to the video data.