-
Notifications
You must be signed in to change notification settings - Fork 9
Description
These slots are in nmdc-schema
rna_isolate_methdna_lr_isolate_methdna_isolate_methemsl_store_tempproject_idsample_shippedsample_typereplicate_numbertechnical_reps
This was so we could create the submission-schema. We now have the ability to create slots in submission-schema without them coming from nmdc-schema.
These slots were not moved out of nmdc-schema, but should be
-
remove slots from
nmdc-schemain favor of extraction class & provide viasubmission-schema -
rna_isolate_meth,dna_lr_isolate_meth,dna_isolate_meth -
in the submission portal, we need to collect the long read & short read extraction information. Upon ingest to mongoDB, this information should be on an
Extractionrecord. The slot `` will never have a record in mongo. @turbomam has requested, to avoid confusion, we do not have this slot innmdc-schema. We can create an alias on Extraction so it's clear that this information from the submission portal is capture here, but that that slot will not hold any information in mongodb. -
remove slots from
nmdc-schema& provide viasubmission-schema -
NMDC doesn't care or need to track this information.
emsl_store_temp: NMDC doesn't need to store thisproject_id: NMDC will store this viaStudyslotemsl_project_identifierssample_shipped: NMDC doesn't need to store thissample_type: TBD, definitely remove from the portal.yaml file. But should be onBiosample?replicate_number: TBD, definitely remove from the portal.yaml file. But should be onBiosample?technical_reps: TBD, definitely remove from the portal.yaml file. But should be onBiosample?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status