monarch-initiative / phenio

An integrated ontology for Phenomics
https://monarch-initiative.github.io/phenio/
BSD 3-Clause "New" or "Revised" License
6 stars 0 forks source link

Consider filtering only a few annotation properties #13

Open matentzn opened 2 years ago

matentzn commented 2 years ago

@cmungall suggested we should be looking at the OMO profile for guidance.

I did, and IMO it still has way too much noise in it. I think something as crispy as the following set would make sense as a first pass, essentially stripping out everything else from PHENIO:

"alternative_term"
"broadMatch"
"category"
"closeMatch"
"contributor"
"created_by"
"creator"
"database_cross_reference"
"definition"
"deprecated"
"exactMatch"
"has_broad_synonym"
"has_exact_synonym"
"has_narrow_synonym"
"has_obsolescence_reason"
"has_related_synonym"
"in_subset"
"label"
"narrowMatch"
"never_in_taxon"
"term_replaced_by"
"term_tracker_item"
matentzn commented 2 years ago

cc @kevinschaper

caufieldjh commented 2 years ago

OK, it looks like that should cover current use cases at least. I'll try that in #9 - or do you think we could get this in a separate PR just to see what the result looks like?

matentzn commented 2 years ago

Whatever works for you! Dont worry about process at the moment. I guess since we cant even built phenio atm..