data-models
data-models copied to clipboard
chop-dbhi
Collection of various biomedical data models in parseable formats.
Some indexes (on foreign key fields) were dropped in pedsnet 2.2 for unknown reasons and should be replaced in the 2.3 model.
##### pedsnet The `fact_relationship`.`fact_id_1` and `fact_relationship`.`fact_id_2` are not indexed, which might affect some joins to the domain tables. Queries that need to look at a large portion of the rows...
@bruth @murphyke @burrowse Do you think we should try to pull the vocabulary model out of the OMOP and PEDSnet models into its own directory? This would reduce duplication and...
The json-table-schema spec gives the following attributes: - `name` - `title` - `description` - `type` drawn from `string`, `number`, `integer`, `boolean`, `null`, `object`, `array`, `datetime`, `date`, `time`, `duration`, `geopoint`, `geojson`,...
As per the discussion in chop-dbhi/data-models-service#20, the "reasonable default" behavior for missing attributes on types is causing problems and, frankly, seems hackish. These files should be the single source of...
The json-table-schema spec organizes the schema by table objects, which contain field definitions, primary key definition, and any foreign keys on the table. I think we should emulate this with...
Again, I think this was targeted at potential users who would be intimidated by parsing the separate constraints file, but we haven't found many of those users.
Sometimes I wish I could distinguish between the PEDSnet vocabulary tables and the core tables. Maybe I want a tags column for tables (and fields?), or maybe I want the...
Not nulls should be specified on the field, as per the json-table-schema. The key for this attribute in the spec is `required`. The attribute we currently have called `required` is...
As per the json-table-schema, simple unique constraints should be defined on the field itself. Multi-column unique constraints can still be expressed through multi-column unique indexes, as they are now.