Skip to content

Determine/validate the approach for representing "NA" (not_available) vs. unspecified or not_applicable in TDR #2

@NoopDog

Description

@NoopDog

Need

Not all metadata fields are applicable to all file types (e.g., reference_genome is relevant for BAM files but not for FASTQ). We need to review how this is currently handled in the Terra Data Repository (TDR) schema for the AnVIL project, specifically:

  • How not_applicable, not_available, and unspecified values are represented (if at all).

  • Whether there is a standardized mechanism for marking a field as not applicable.

If no consistent method exists, we should define a clear and interoperable approach for representing these cases across metadata fields and file types.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions