Website, Database

Job ID: 30812653

Budget: $1,500 – $3,000 AUD

require a developer to:
Database and Records
- develop a historical database from supplied records,
- parsing/import of historical records to build that database
- parsing/import of new records to maintain that database
- Identify and Set in the database Standard Parameters such as Course Record Times, Course Sectional Times with the ability to manually over-ride
- Develop code to query the database based on supplied equations

Design And Interface
- Output Future Race Card from Pre-Race Data Files, including (the equation calculated data) Predictive Velocity Ratings and Previous Historical Runs for each horse, and for Predictive> by default a merger of same distance races from historical data into averaged output for Today's Race (at same) distance. User has ability to select or deselect data used for the predictive calculations/merger. Also, calculate (from supplied equation) Predictive Velocity Based on Historical Runs from other distance to today's distance.

An example of how the Race Card would look is here ---> https://www.racing.com/form/2021-07-14/ladbrokes-park-hillside/race/1#/form

- Develop Race Card interface for viewing data output and presentation, similar looking to have the calculated equations (AJAX??) expandable details available at an instance
- Develop Race Card provision to output data to be interactive; for example selecting buttons for overlaying indicators (like a transparent line) denoting the Race "Class" average time within a 400m segment
*Additional for the Race Card interface Speedmapping and Field Position: Show Speed Map from the first Sectional (and each Sectional), but to correlate field position from the first to the next and subsequent sectionals, the horse next sectional value must start where the field position ended in the previous sectional. Visual indicator: if we were able to pliant or adjust horses field position, for example, acceleration or advance position in lengths in an earlier sectional, that expenditure of lengths used, above that horse's average, would result in those lengths been used out of total lengths available in the predicated energy expenditure available.

- Develop Calander Interface to review previous meetings to see and compare historical predictive figures and calculations from actual finish results

Develop for / Login / Subscriber / payments; ability to keep notes on each horse / race card / save any interactive setting

Develop Admin Interface with controls

I have a website on Hostgator with MySQL. I'm not fussed about the backend code, but want it simple, fast, and reliable.

*need advice* Unsure whether to historically Save calculated Velocity Values in the database or to just have them calculated on-the-fly with the working alogrithm