Add metadata-driven Croissant parsers for HGNC and BindingDB#386
Draft
Add metadata-driven Croissant parsers for HGNC and BindingDB#386
Conversation
Contributor
Author
|
Check it out @EvanDietzMorris I think that the current metadata for going data->graph highlights the concern that the metadata will need to be just as complicated as code. So not 100% sure it's a win, but maybe that can be fixed. |
This file contains hidden or 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
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.
Summary
Validation
uv run pytest tests/test_metadata_driven_parser.pyuv run pytest tests/test_metadata_driven_parser.py tests/test_source_metadata.pyBindingDB_All_202603_tsv.ziparchive; both produced 1,200,861 nodes and 1,892,606 edges with identical node and edge SHA-256 hashesNotes
/tmp/orion_parser_runs_20260402/bindingdb_compare_202603/report.json/tmp/orion_parser_runs_20260402/hgnc_shared