...
The mapping looks very sparse. The only file that has a schema is metadata.json. Everything else appears to be specific to the MTB app or assessments. Do we plan to update this mapping?
From our previous meeting, it sounded like we settled on this design because this was what D&T wanted. If we need to write a new schemas anyway, does we’re not actually saving that much work by re-using that design decision. (And we aren’t planning on using BridgeDownstream anymore anyway.) At that point, wouldn’t it make more sense to put them into AssessmentResources. This way, so we don’t have to load GitHub URLs write code to download a GitHub URL and parse a bespoke JSON files?file.
Are we only going to use the filename mapping? Or are we also going to use assessment and app mapping?
...