You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
I would like to have some code that assists with
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.
The text was updated successfully, but these errors were encountered: