-
Notifications
You must be signed in to change notification settings - Fork 3
Type/Design/Method entity/field? #6
Comments
Similar comments here to those I made on #7. m2m seems wasteful if we are not expecting commonality - ie - that each trial just has its own text description(s) of method. Can you run some queries to see actually if there is any consistency here across trials? BTW @roll this is great work, well done. |
Is there a further way to break down these strings into more structured data? Example: @roll has an example which essentially is 'random'. If we look at these 43 manually, I'm curious if these are just textual variations on themes that could be enum-ed. |
@pwalsh But it's just one dataset. I think to make it more structured we have to have a very deep understanding of the domain and other dataset examples. To do not run into troubles further. All of this looks like point 15 of http://www.who.int/ictrp/network/trds/en/ (Study type):
|
But here we see more structure - https://clinicaltrials.gov/ct2/show/results/NCT00922272?term=schizophrenia&rank=121§=X30156 Study Type - Interventional |
Those methods, I'm inclined to say we make a list of types, and have a method description field. EG:
becomes:
WDYT? |
|
I see it in the same way on the dataset we have (about randomized/blinded/etc + type). Just a little bit afraid we don't see the whole picture. It looks like - #6 (comment) - it's kinda a reference for our problem. Here is some study types (1 type per study) and study designs (tags). |
Cochrane's RCT, CCT (from Dan): |
Background
Related to #21 issue.
Topic
Our ideal data model doesn't have a
Method
entity or field. It looks it's a vital part of a trial description. Example of method:Randomised - random number generation + admission order
Proposed solutions
Method
with m2m relation withTrial
(as in Cochrane database)Trial.method
implemented as an array of stringsSee also - https://github.com/okfn/opentrials-cochrane-schizophrenia-data/wiki
The text was updated successfully, but these errors were encountered: