Refactor the parsing logic to set up the reference between section and professors using compound keys

[mikehquan19]

Refactor the parser in parser/sectionParser.go and parser/professorParser so that the section can reference the list of associated professors using their compound keys (combination of fields that uniquely identify the object) and vice versa.

For example, each section can be identified by:

{
   "subject_prefix": XX, 
   "course_number": YYYY, 
   "term": 18F,
   "section_number": 001,
}

instead of just mongo.Id (Same thing for professor). How you want to set up this compound key is up to you as long as they are unique. You should only be concerned with the connection between course and section.

Refactoring the parser means that you will have to do the following things:

• Refactor the schema of profssor and section over the nebula-api repo
• Refactor the parsing logic between professor and section (main part)
• Refactor the professor and section validating part in validator.go
• Refactor the test in professorParser_test.go, sectionParser_test.go, and validator_test.go.

While you work on this issue, make sure to pull or push to the compound-key branch that I created in both nebula-api & api-tools repo.

[mikehquan19]

@KBui4 Just pushed the POC to branch compound-key-approach, you can look at the code as reference. I removed all the tests in that branch as it's distracting, but you are supposed to modify the tests for the modified parsers.

The result of the POC:

{
  "_id": "691837075e2afce51547386d",
  "first_name": "Adam",
  "last_name": "Majors",
  ...,
  "sections": [
    {
      "prefix": "ECS",
      "number": "1100",
      "term": "19F",
      "section_number": "010"
    },
    ...,
    {
      "prefix": "ECS",
      "number": "1100",
      "term": "20F",
      "section_number": "020"
     }
  ]
}

[KBui4]

Thanks, I'll take a look at it. I mostly have the parsers done already, just the tests left to do.

[KBui4]

Because of finals, I'm planning on finishing this after the semester ends.

[mikehquan19]

No worries.

[mikehquan19]

@KBui4 , I have redesigned the compound-key schema on nebula-api/compound-key a little bit. The one thing I've noticed in the previous compound-key schemas is that it contains redundant information in the schema, which is not undesirable. Can you take a look and rewrite the parser according to it?

[mikehquan19]

This should be closed by #140