Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider filtering only a few annotation properties #13

Open
matentzn opened this issue Aug 3, 2022 · 3 comments
Open

Consider filtering only a few annotation properties #13

matentzn opened this issue Aug 3, 2022 · 3 comments

Comments

@matentzn
Copy link
Member

matentzn commented Aug 3, 2022

@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
Copy link
Member Author

matentzn commented Aug 3, 2022

cc @kevinschaper

@caufieldjh
Copy link
Member

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
Copy link
Member Author

matentzn commented Aug 4, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants