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

Be careful about subject/object distinctions in Monarch mapping commons? #16

Open
matentzn opened this issue Sep 28, 2022 · 0 comments
Open
Assignees

Comments

@matentzn
Copy link
Member

matentzn commented Sep 28, 2022

@kevinschaper mentions in his update:

I'm not quite sure how to think about the SSSOM being built of triples, and that those factual statements don't really dictate what ID we want or don't want, and that direction shouldn't really matter. In my code, I really want one column that is the ID I want and the other column to be IDs that I might potentially have, and I want to apply them with simple joins.

I think this is a great prompt for thinking about how to realise this. A few days ago I requested a "flip" operation in sssom py (flipping is not trivial due to metadata). I believe we can achieve perfectly formatted mapping sets for monarch with a mix of flip and filter.

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