We manually create the courses we play currently, and while it's not a big deal to do one time setups, it's annoying having to redo it when the dev environment changes or when we want to try a new course with real data.
Example Flow
Admin logs into admin area, and goes to Course Import section
DGCR uses course -> hole - tee -> pin as a structure, and we use course -> layout -> hole which means we either need to convert to our model or switch to their structure. Point for moving to the other data structure is when we get to scoring our own rounds, we can support dynamic layouts where we can change the pin placement or tee used on the fly if needed (such as a tee being flooded or bee infested idk).
We manually create the courses we play currently, and while it's not a big deal to do one time setups, it's annoying having to redo it when the dev environment changes or when we want to try a new course with real data.
Example Flow
Course Import
sectionSchema Change
course -> hole - tee -> pin
as a structure, and we usecourse -> layout -> hole
which means we either need to convert to our model or switch to their structure. Point for moving to the other data structure is when we get to scoring our own rounds, we can support dynamic layouts where we can change the pin placement or tee used on the fly if needed (such as a tee being flooded or bee infested idk).