I understand why we currently have SOLUS objects, to separate things like the rawrequirements from our data set. Unfortunately this has implication on the API. Our current system only allows filtering based on base level fields, which means that we either get ALL of the solus objects, or none of them. I think it would make sense to instead prefix the name of the fields with solus, getting names like solus_requirements and solus_id.
In addition, it may make more sense for them to be ps_requirements (peoplesoft requirements), as solus is just a queens name.
Re-post of https://github.com/Queens-Hacks/qcumber-data/issues/7
from @mystor:
I understand why we currently have SOLUS objects, to separate things like the rawrequirements from our data set. Unfortunately this has implication on the API. Our current system only allows filtering based on base level fields, which means that we either get ALL of the solus objects, or none of them. I think it would make sense to instead prefix the name of the fields with solus, getting names like solus_requirements and solus_id.
In addition, it may make more sense for them to be ps_requirements (peoplesoft requirements), as solus is just a queens name.