tbrittain
commented
1 year ago As part of this, it may be beneficial to have two separate VMs and views for Position Players vs Pitchers. But that might get complicated when we start to think about 2-way players, since for those players we would want to display their batting stats as well.
One solution may be to just pull back batting and pitching data, but then ordering the DataGrids for pitchings vs batting differently, depending on their primary position. Of course we will still need to display different header rows.
https://www.baseball-reference.com/players/o/ohtansh01-bat.shtml#all_batting_advanced
BBREF favors the display of batting stats in the header row over pitching for Ohtani, so perhaps we just do the same
This should be a screen similar to https://www.baseball-reference.com/players/a/aaronha01.shtml It should have the general player stats in a header section, like
Under the summary, there should be a career stats summary with counting and rate stats
Position Players
Pitchers
and a list of the individual seasons, with the following columns:
Position Players
Season
Age
Team (clicking this will navigate to the Team Season page)
Conference
G
PA
AB
R
H
2B
3B
HR
RBI
SB
CS
BB
SO
BA
OBP
SLG
OPS
OPS+
TB
HBP
SH
SF
Secondary Positions
Traits
Pitchers
Season
Age
Team (clicking this will navigate to the Team Season page)
Conference
W
L
W-L%
ERA
G
GS
GF
CG
SHO
SV
IP
H
R
ER
HR
BB
SO
HBP
Batters Faced
ERA-
FIP
FIP-
WHIP
H/9
HR/9
BB/9
SO/9
SO/W
Bonus points if we can have some sort of metadata associated with each of the stats that can conditionally display whether the given stat
It would also be nice to have a Totals row at the bottom, AND a 162 game average Total row