Biocypher
A unifying framework for biomedical research knowledge graphs
Install / Use
/learn @biocypher/BiocypherREADME
BioCypher
| | | | |
| --- | --- | --- | --- |
| License | | Python |
|
| Package |
| Build status |
|
| Tests |
| Docker |
|
| Development |
| Contributions |
|
❓ Description
Knowledge graphs (KGs) are an approach to knowledge representation that uses graph structure to facilitate exploration and analysis of complex data, often leveraging semantic information. They are popular in many research areas, including the life sciences, due to their versatile use, for instance in data storage, integration, reasoning, and more recently in artificial intelligence. The creation of KGs is a complex task; BioCypher helps you in creating and maintaining your own KG. For more overview, usage notes, and a tutorial, read the docs here.
<img style="display: block; margin-left: auto; margin-right: auto; width: 70%;" src="docs/assets/img/graphical-abstract-biocypher.png" alt="Graphical Abstract"> </img>
📖 Documentation
Tutorial and developer docs at https://biocypher.org. For a quickstart into your own pipeline, you can refer to our project template, and for an overview of existing and planned adapters for resources and outputs, as well as other features, visit our GitHub Project Board.
⚙️ Installation / Usage
Install the package from PyPI using pip install biocypher. For Neo4j online mode
support, install with pip install biocypher[neo4j]. More comprehensive
installation and configuration instructions can be found
here.
Exemplary usage of BioCypher to build a graph database is shown in our tutorial and the various pipelines we have created. You can find these on the Components Project Board.
🤝 Getting involved
We are very happy about contributions from the community, large and small! If you would like to contribute to BioCypher development, please refer to our contribution guidelines. :)
If you want to ask informal questions, talk about dev things, or just chat, please join our community at https://biocypher.zulipchat.com!
Imposter syndrome disclaimer: We want your help. No, really. There may be a little voice inside your head that is telling you that you're not ready, that you aren't skilled enough to contribute. We assure you that the little voice in your head is wrong. Most importantly, there are many valuable ways to contribute besides writing code.
This disclaimer was adapted from the Pooch project.
✍️ Citation
The BioCypher paper has been peer-reviewed in Nature Biotechnology. It is available as a self-archived version on Zenodo, online version here. Before, it was available as a preprint at https://arxiv.org/abs/2212.13543.
Acknowledgements
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 965193 for DECIDER and No 116030 for TransQST.
Related Skills
oracle
334.1kBest practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
prose
334.1kOpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.
Command Development
82.1kThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
Plugin Structure
82.1kThis skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
