-
Notifications
You must be signed in to change notification settings - Fork 1
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
Model Revisions for Initial Release (v1.0) #10
Comments
I have moved the following item to ticket #11: reference entity for |
The EMX tags object is now built by pull attribute level tags and transforming them into EMX format. This eliminates the need to define tags in the YAML. The process is slightly manual in that you have to update the known tags or add additional search patterns. Errors are thrown if a tag is not recognized. |
Regarding the user who changed a record, we need to make the distinction between the change requester and the person who made the change (i.e., data manager, coordinator, etc.). |
Discussion Points
resolved
(in clinical table; consult experts)pathologicalState
lookupbelongsToCohorts
?AddWAIT FOR FAIR GENOMESanalyses
table and split sequencing table (use Fair Genomes as a guide)Changes
This is a sticky for all changes that are needed for v1.0
organization
entity: move out of lookupsreleases
: move out of lookupssubjects
, changeinclusionStatus
tosubjectStatus
(update tag)yearOfDeath
and taglabIndication
tosamplingReason
samplingDate
or changesampleTimestamp
samplingProtocol
to type reference (value, description, codesystem, code, iri)samplingProtocolDeviation
to typetext
changeSEE COMMENT BELOWbiospecimenUsability
to typexref
ormref
and create lookuppcrFree
to typebool
targetEnrichmentKit
toref
umIsPresent
to typebool
and rename toumisPresent
labProcedure
lookup out of lookups folderfiles
, changebelongsToSequencing
to typexref
and change name toproducedBy*
cohort
andstudy
cohorts
lookup table and reference in files, subjects, study, consentFeatures
statusOfDiagnosis
The text was updated successfully, but these errors were encountered: