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

Harvest aliases for ORCIDs (e.g. GOC:cjm) to make it easier for ontologies to replace #5

Open
cmungall opened this issue Jan 5, 2023 · 1 comment

Comments

@cmungall
Copy link

cmungall commented Jan 5, 2023

I would like to have some code that assists with

  1. repairing ontologies to replace ad-hoc aliases like GOC:cjm with orcids and other URIs
  2. dynamically mapping aliases to orcids when doing contributor stacks (e.g. include contributors and roles in summary statistics INCATools/ontology-access-kit#378)

I'm sympathetic to the idea that we should not do 2 as it removes a carrot to incentivize groups to do 1.

Either way, there is a task of harvesting mappings that needs to happen

In GO we have metadata about various contributors orcids, including their github handle and the much-loved GOC:nnn aliases.

https://github.com/geneontology/go-site/blob/master/metadata/users.yaml

Other ontologies may have their own files (though for a lot of ontologies with fewer contributors ad-hoc manual replacement should be encouraged)

Where should the ETL code live? I'm happy for it to live in this repo, and to possibly even distribute this alongside the abox ontology, but this is potentially out of scope (and we may also want to not grant further legitimacy to the GOC:cjm aliases). So equally happy for this to live somewhere else like OAK or a standalone.

@cthoyt
Copy link
Owner

cthoyt commented Jan 5, 2023

This repository has a single, well-defined purpose, so I would say code that does this should go somewhere else. There are plenty of low hanging fruit where some find/replace could get a lot of the work done. I have got positive feedback in some places and very negative feedback in others when sending PRs with this kind of stuff.

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