Accessing MeSH NXO about nxontology-data HOT 8 CLOSED

https://github.com/related-sciences/nxontology-data/actions/runs/2296536149 🎉

It did fail the first time but not the second after deleting the branch, as you suggested.

from nxontology-data.

You'll want to use the MeSH in the output/mesh branch rather than the output/pubchem branch. We could consider no longer exporting MeSH from pubchem now that we have a dedicated export path for MeSH.

See the data here. Regarding the weird directory path undefined/actions_github_pages_1651177463639, looking into that in peaceiris/actions-gh-pages#740, but data is still usable, just make sure to commit hash version.

from nxontology-data.

You'll probably want the mesh_topical_descriptor_descendants.json.gz network. It only includes nodes that descend from a Topical Descriptor and so would exclude parts of MeSH such as Geographical Descriptors and disconnected Supplemental Concept Records.

from nxontology-data.

You'll want to use the MeSH in the output/mesh branch rather than the output/pubchem branch.

🤦

See the data here.

Awesome, thanks! That works.

from nxontology-data.

BTW if you'd like MeSH 2022, it will now be created upon the next CI mesh export following d0b3c82 (which might now work due to the deploy bug)

from nxontology-data.

That would be really great actually. Can I kick off these workflows myself sooner in https://github.com/related-sciences/nxontology-data/actions/workflows/create.yaml? Should I check "Overwrite output on an existing branch"?

from nxontology-data.

Yes kick off yourself and select overwrite, but I'm worried there will be a deployment bug. If so, you could try deleting the output/mesh branch and then rerunning. Should work that way.

from nxontology-data.

Regarding the weird directory path undefined/actions_github_pages_1651177463639

#6 fixed the weird path issue, so now the output/mesh branch contents are proper.

from nxontology-data.