-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review the brief and ask any questions on this project #1
Comments
I'd like to know more about the
|
Should we use TALL stack in our app? |
Here is what @edgrosvenor shared with me -- this will mainly be all back-end functionality so feel free to use whatever you prefer, e.g. browsershot, curl, even python is ok, etc. The early output might be CSVs of the profile data just to check it (e.g. name, position, year in school, etc). If you are planning to do a front-end piece, TALL would be useful. Does that make sense? |
Thanks for letting me know, @barrytarter . |
@hardcommitoneself great, yes, this is best place to reach both me and Ed! |
I just finished import excel feature and now I am gonna build scrapper. |
@hardcommitoneself For now, whatever is easiest to get a 'test' version live that successfully pulls and stores data. If @edgrosvenor has any tips, he'll share them here as well. You'll need to create unique decision rules for pulling the roster data as some rosters are very similar and others are different, e.g. These ones also use Sidearm sports, but a different template I think: These are both from Presto Sports templates, but the templates look different: |
In my opinion, how about checking the number of |
@hardcommitoneself I like that approach. We might need a way to decipher the type of content listed. e.g. grade level (aka "graduation Year") values could be categorized by word, e.g. 'freshman', sophomore, junior, senior? I look forward to seeing how you figure it out! |
I just noticed that some rosters have no |
@hardcommitoneself here is one possible guide on how to map the data: https://docs.google.com/spreadsheets/d/1QBCGpvXjoDAH50wQTTnYLj5cWzb3TlXWWUPn-g3kk78/edit?usp=sharing. Specifically for the numbers, it could map as 1 = Freshman, 2 = Sophomore, 3 = Junior; 4 = Senior; 5 = Senior; 6 = Senior. |
https://www.loom.com/share/262f7d29525f45eba0caa4e8455a965d |
Thanks for sharing. Can we store both as text for now? The first is a height field and the second is where they played in high school. These are pretty common, so good to collect. |
@hardcommitoneself will you be able to begin developing the crawler that will find the missing Twitter and Instagram IDs? Step 3 in https://docs.google.com/document/d/1YmfAFYu4Cyl99ninB4KAeML4y-nmRW0gzI6Xeydg_2g/edit?usp=drivesdk Can you get a v1 of that part ready by Wednesday? |
@hardcommitoneself Go ahead and add any data that you think might be valuable as key / value pairs in the extra column. While you're at it, enable this package for that column: https://github.com/spatie/laravel-schemaless-attributes That will allow you to do things like |
Regarding the second crawler, I think we can use
That's it. I am not sure this approach is working for all rosters. So I just want to test with real links. |
I wrote my suggestion below.
Please take a look at it and give me your idea. |
Sure, we can test that out and see how the data looks. |
Hi, Hope you are having nice weekend! Please take a look at this video. Sorry to bother you. :) |
Please take a look at the following. |
@hardcommitoneself could we add a method that would allow us to get this person's instagram and twitter? |
So, do you want to get full twiiter link of atheltes like https://www.instagram.com/c_kendra2/ ? |
@hardcommitoneself yes, we want the twitter, instagram, opendorse links for all athletes in the crawler. |
@hardcommitoneself yes, if it doesn't exist, we definitely can't store one. Caleb Kendra does have one but we didn't store it -- how do we fix that? |
Great! Why didn't it store previously? |
Please take a look at it. I implemented |
@hardcommitoneself if you have any technical questions, feel free to post them in this issue here as should allow us to document the development process better.
The text was updated successfully, but these errors were encountered: