Syncing the compilation stage

[TathagataChakraborti]

We want to have a single compilation run to produce the starting point for the Insights tab. This avoids having two separate spreadsheet reads and nightmares with what structures are supported and what is not + no having to map between IDs and slugs from separate reads.

• Produce starting YAML file for configuring rules @TathagataChakraborti
• Remove slugs and replace them with automated slugs @TathagataChakraborti
• Modify the encoding script to read from the YAML and compiled JSON instead. @haz
• Remove vestigeal flask stuff from the encoding script @haz
• Streamline the preference specification process 👀

This is the current compiled JSON schema; and here is an example JSON. Do you need me to modify or add things to it that make your job easier?

[haz]

Shouldn't get a jump on this until things are squashed.

[haz]

Changes coming in #21

[haz]

Ok, I've rotated through random hacks for parsing this taxonomy, but nothing is sticking. Can you rework it slightly? Problem is that there's too much reliance of the order of lists in the json to keep things unambiguous. If there are similar parent tags in the ontology, or even worse, similar child-parent pairs across the ontology.

Ideally, tagging (both the in the specific paper data and overall taxonomy) would be of the form A > B > C, like we've had already from the CSV parsing.