Skip to content

How to add new GWAS requested trait terms to OBA and EFO?

1. Check if an appropriate OBA trait pattern already exists

Look into bio-attribute-ontology/src/patterns/dosdp-patterns/ and check if the GWAS trait term would fit into any of the existing patterns. - [ ] If yes, skip to the next step. - [ ] If none of the existing OBA trait patterns look appropriate, then create a new pattern. In some cases, the requested GWAS term may not fit the scope of OBA. In that case, an new EFO term can be created without an equivalent OBA trait term.

2. Create new OBA term(s)

For example, for a trait involving the 'age at which disease manifestations first appear', fill in the table disease_onset.tsv.. Create a unique OBA identifier by using the next available ID from your assigned range.

Also fill in the appropriate columns for the variable fields as specified in the actual DOS-DP yaml template file. For example, in the case of the disease_onset.tsv. table, you must use MONDO disease or disorder terms in the disease column.

NOTE: Keep track of the IDs from your range that you have already assigned.

  • Create a pull request (PR) with the edits. Request other people to review your PR.
  • If approved, merge the PR after the review(s) into the 'master' branch.

3. OBA release

The newly created trait terms can be imported into EFO from a publicly released version of OBA.

To run the OBA release pipeline, follow the instructions in the document Release Workflow for the Ontology of Biological Attributes (OBA).

4. Provide the new OBA terms to EFO

  • [ ] Add the newly created OBA term IRI and also all its component term IRIs to oba_terms.txt so that they get included in EFO dynamic imports. By component terms I mean all those terms that are used in the DOS-DP data filler table to compose the OBA term (terms from MONDO, UBERON, PATO, etc.) as specified in the corresponding DOS-DP pattern file.

    • NOTE: use full IRI, i.e:

    http://purl.obolibrary.org/obo/OBA_2040167 http://purl.obolibrary.org/obo/MONDO_0000481

  • [ ] This step depends on a new public OBA release.

  • [ ] You need to accomplish this in an EFO PR.