-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add FAIRsharing IDs when possible #52
Comments
thanks @cthoyt - to be clear, you suggest using the FAIRsharing ID as the kg-registry ID where possible, right? |
I would keep those separately to be honest, since the fair sharing key is optional
|
@matentzn ah okay, no strong feelings. I guess we'd have to add an attribute |
Please also consider the information resource registry when naming things (or at least a methodology like it where we can store extra metadata about the source). Having a slot to fill here, with infores identifiers, would be very helpful. https://biolink.github.io/information-resource-registry/ (in particular, the code here to help generate a sankey of data->resulting KG movement is very helpful to consumers) |
@sierra-moxon very good idea! we could simply use It might create a little overhead if we actually have to add to the infores catalog but I think this would be useful! |
Some KGs correspond to a specific resource, like HGNC or DrugBank, so it would be great to keep a FAIRsharing ID for them. For the ones coming from obo-db-ingest, which are tagged with Bioregistry IDs, you can look up the FAIRsharing ID with the Bioregistry Python package:
I could also include this (or other arbitrary information available in the Bioregistry) in the obo-db-ingest metadata (re #49) to help fill out these fields. LMK!
It might even be the case that entries in this registry could be assigned a FAIRsharing ID.
The text was updated successfully, but these errors were encountered: