Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOLUS Objects #21

Open
uniphil opened this issue Jan 13, 2014 · 0 comments
Open

SOLUS Objects #21

uniphil opened this issue Jan 13, 2014 · 0 comments

Comments

@uniphil
Copy link
Member

uniphil commented Jan 13, 2014

Re-post of Queens-Hacks/qcumber-data#7

from @mystor:

I understand why we currently have SOLUS objects, to separate things like the raw_requirements 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant