creating systems for general degree tracking is easily the most interesting topic i've recently come across in the past few years.
-- said man stranded on remote island
0. executive summary (boring stuff)
Scarlet Navigator (SN) required a system for tracking programs of study (PSTs). PSTs are a set of requirements that detail what is necessary for a degree or core curriculum to be fulfilled.
In Rutgers' instance of Degree Navigator (DN), PSTs are not publicly accessible. In fact, content is server-side rendered (SSR) behind a ASP.NET service. Therefore, DN would need to be sophistically scraped for all PSTs to be easily available to the public. Even so, it would still be worthwhile to develop a generalizable form for all PSTs which would facilitate frontend-consumption, increase overall flexibility for the user, and future-proof the tracking system.
Requirement:
- A general easy-to-understand YAML format that closely models the requirement systems established by DN (with current emphasis on C.S. B.S. and SAS Core Curriculum)
- Allow users to open a PR to add and share programs of study
1. Beginning (good stuff)
Okay. How can we model the requirements of a degree? What are the common elements that comprise degree and core curriculum requirements? We'll explore these questions, discover the common cloth tying them together, and the weird wrenches that are thrown into the works because life is never meant to be so easy.
Degree Navigator is
