Skip to content

remove slots that are only for submission-schema #2682

@mslarae13

Description

@mslarae13

These slots are in nmdc-schema

  • rna_isolate_meth
  • dna_lr_isolate_meth
  • dna_isolate_meth
  • emsl_store_temp
  • project_id
  • sample_shipped
  • sample_type
  • replicate_number
  • technical_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-schema in favor of extraction class & provide via submission-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 Extraction record. The slot `` will never have a record in mongo. @turbomam has requested, to avoid confusion, we do not have this slot in nmdc-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 via submission-schema

  • NMDC doesn't care or need to track this information.

    • emsl_store_temp : NMDC doesn't need to store this
    • project_id : NMDC will store this via Study slot emsl_project_identifiers
    • sample_shipped: NMDC doesn't need to store this
    • sample_type : TBD, definitely remove from the portal.yaml file. But should be on Biosample?
    • replicate_number : TBD, definitely remove from the portal.yaml file. But should be on Biosample?
    • technical_reps: TBD, definitely remove from the portal.yaml file. But should be on Biosample?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

❌ Discuss: Priority or Blocked

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions