Add Molecular Oncology Almanac #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It doesn't appear (after a very quick search) that this resource defines its own nomenclature, so there's no need to add a bioregistry ID. Thanks again for all of the PR's! After they're all merged I will make a new release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://moalmanac.org/
https://github.com/vanallenlab/moalmanac-db/releases
I didn't see this source in the Bioregistry (hopefully I'm not just missing it again...) so I didn't define a
bioregistry_idvalue.p.s. this latest collection of PRs covers most of our remaining use-cases -- when you have the time, it'd be awesome if you could push a release candidate so that we could start pulling from PyPI for our production tools. Thanks again for all of your work on this project and for your patience with my PRs!