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

categorical Result Type doesn't exist based on vocab database. #126

Open
lsetiawan opened this issue Nov 21, 2017 · 3 comments
Open

categorical Result Type doesn't exist based on vocab database. #126

lsetiawan opened this issue Nov 21, 2017 · 3 comments

Comments

@lsetiawan
Copy link
Member

Based on ODM2 Vocabulary Repository for Result Types, I don't see anything with Categorical, but python api is using it. The closest thing I see is Category observation

if 'categorical' in type.lower():

@emiliom
Copy link
Member

emiliom commented Nov 21, 2017

Side question: are you currently trying to implement ALL result types in the REST API?? Or just a narrow subset that @horsburgh specified in the design doc? (I don't remember). I don't think we should be trying to implement every single result type in the REST API, at this time. Time Series and Measurements should be the targets, for now, unless Jeff's Specimen DB actually uses categorical results.

But back to your main point: it sounds like odm2api needs to be updated to match the CV term.

@lsetiawan
Copy link
Member Author

lsetiawan commented Nov 21, 2017

are you currently trying to implement ALL result types in the REST API??

I'm implementing what the database allows me to, others I can't really test, so I don't implement them, the code is there though, since it was easy to just put it there (I took similar code from the python api) It was just something I noticed, so I opened an issue, not planning to act on it whatsoever.

@emiliom
Copy link
Member

emiliom commented Nov 21, 2017

I'm implementing what the database allows me to, others I can't really test, so I don't implement them, the code is there though, since it was easy to just put it there (I took similar code from the python api)

I'm not sure I completely follow. But my recommendation is not to bother implementing result types we're not using yet in an actual ODM2 database you're aware of. Things may change in the future with the REST API design (eg, see Jim Kreft's email a minute ago!), so let's focus on what we know we're likely to use and test (Jeff's design doc) soon.

But we digress from this github issue. Again, thanks for creating this issue here. Totally relevant and helpful.

@emiliom emiliom added this to the v0.7.2 release milestone Apr 8, 2019
@emiliom emiliom removed this from the v0.7.2 release milestone Apr 21, 2019
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

2 participants