Skip to content

Consider omitting attribute components #30

@csarven

Description

@csarven

Consider omitting attribute components that have quality issues in the data. For example, an attribute value in the data might use a text description of a code instead of a its identifier:

whereas it should be like:

Or there is simply a mismatch between the data and metadata.

These issues are better fixed at the source (and I'm reporting them), however, for the time being it might be better to provide a way to omit them in the results. Obviously precision will be lost but probably better than leaving inaccurate information.

Possible approaches (ordered from easiest to difficult):

  • Offer a config option to omit attributes with a certain @conceptRef
  • Leave everything as is in KeyFamily, but omit the values that have whitespaces (note: is this safe in general for attributes?) in GenericData
  • Omit the component in KeyFamily and the value in GenericData.

Kids, don't manipulate other people's data without parental guidance.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions