karagenit / bracketology Goto Github PK

Will need to hash password & compare to file contents, create a session with a flag set and check that session (and redirect if necessary) on any 'admin' page.

Based on: knowledge, gender, age group.

Calculations: min, q1, median, q3, max, n, mean, stdev

E.g. set which regions play each other first in the final four rounds, or maybe which seeds play each other.

Instead of { south_0_0: "", south_0_1: "" } we should nest attributes, such as: { south: { round1: { index1: { ... }}} (of course, with arrays instead of hashes on the last two.

Right now, it just creates the final four buttons based on the indexes of the elite 8 selections - e.g. whatever team gets picked from elite 8 #s 0 or 1 is put in the Final Four #0 position. This is incorrect - we should make sure they go to the right regions.

The displayed text of the buttons looks like <small>1 </small> Name (W-L), but we shouldn't be passing this as the value as well (which gets stored in the DB) - we want to make it store either just the name or possibly the DB index if we do #27

Obviously, not available on the initial rows, but useful for updating the master bracket if mistakes are made.

As text files maybe, and on submit we run our ruby script to convert it to the JSON?

http://getbootstrap.com/docs/4.0/examples/sticky-footer/

view-source:getbootstrap.com/docs/4.0/examples/sticky-footer/

http://getbootstrap.com/docs/4.0/examples/sticky-footer/sticky-footer.css

Compares two brackets (a student's and the master) and returns a score based on the scoring table found on the index page.

Total cleanup needs to be done, particularly on the bracket generation code. I'd suggest we inline it, but we'll need to render brackets in the 'view-bracket' page and the 'master-bracket' page... so we'd need to update it to take a data param to fill in some later brackets if applicable.

We've changed some of the team names in the main JSON file (teams.json) - this means brackets in the DB are different... we need to use some regex to replace these. Changes:

• remove <small> tags (including the seed #)
• convert Virginia (31-0) to Virginia (31-2)

OnSubmit JS which checks all hidden inputs to make sure they have a value should do the trick.

Brackets don't look great on mobile. We could have a dynamic loading bracket that just shows the two teams, has them pick one, and loads the next pair (no long brackets) but this doesn't solve the displaying brackets issue.

E.g. NOT NULL DB Constraints

• ID#
• Team Name
• Seed #
• Region
• W/L

See #2

I think he'd like files available to download on the 'analysis' page or something for a class activity, I'll need to get more info about this.

Maybe only do top ~20 or so?