Currently when I add a course to the data assets, I add a course description to one file, a node to another file, edges describing prerequisite relations in another file, and finally add the course into a subject listing.
This is kind of complex to just add a simple course and it makes contributing a little more difficult as well as error prone. I think we can improve this.
If you have a good idea for how to do this, feel free to implement it.
Otherwise, I was considering a few options.
First, we could consolidate the datasheets into a single file so each course datum includes its description, prereqs, and node information. This would simplify things, but then we would have to change the parsing logic to algorithmically build the edges, nodes, and description data structures on page load.
Alternatively, we could write a script that you could run to add a course where it then writes the course information to our four separate jsons.
Currently when I add a course to the data assets, I add a course description to one file, a node to another file, edges describing prerequisite relations in another file, and finally add the course into a subject listing.
This is kind of complex to just add a simple course and it makes contributing a little more difficult as well as error prone. I think we can improve this.
If you have a good idea for how to do this, feel free to implement it.
Otherwise, I was considering a few options.
First, we could consolidate the datasheets into a single file so each course datum includes its description, prereqs, and node information. This would simplify things, but then we would have to change the parsing logic to algorithmically build the edges, nodes, and description data structures on page load.
Alternatively, we could write a script that you could run to add a course where it then writes the course information to our four separate jsons.
Any thoughts?