Getting Started | Upgrade | Releases | Roadmap | Status

For the Annotation Viewer or the integration with the OpenMinTeD platform, please refer to this branch.

NeuroCurator

Desktop application to perform systematic and collaborative curation of neuroscientific literature.

This is a Graphical User Interface (GUI) for the Python module NeuroAnnotation Toolbox (NAT).

This framework has been described in details in the following open-access paper: https://doi.org/10.3389/fninf.2017.00027.

With NeuroCurator, annotations are:

• traceable,
• reusable across projects,
• structured with controlled vocabularies.

---

Getting Started

Installation

After having installed the requirements:

pip3 install neurocurator

You might want to install NeuroCurator in a dedicated conda environment:

conda create --name neurocurator_env python=3.7
conda activate neurocurator_env
pip install neurocurator

To launch NeuroCurator:

neurocurator

Requirements

• Python 3.5+
• Git 1.7.0+ (NAT)
• ImageMagick 6 (Wand)
• Miniconda (optional)

Python dependencies

• NAT
• PyQt5
• NumPy
• pandas
• Wand

Upgrade

pip3 install --upgrade neurocurator

If you have used conda, activate the environment before:

conda activate neurocurator_env

Releases

Versions and their notable changes are listed in the releases section.

Roadmap

Ongoing

1. Stabilize NeuroCurator and NAT (Software Architecture).
2. Split NAT into nat-core, nat-analytics and nat-server (separation of scope).

TODO

1. Integrate fully the Annotation Viewer into NeuroCurator.
2. Semi-automate the Knowledge Extraction process.

Done (latest first)

• Make the annotations publishable into a Blue Brain Nexus instance.
• Remove legacy dependencies in NeuroCurator (Qt 4 and Python 3.4).
• Integrate OpenMinTeD annotations into the literature curation framework.
• Visualize NeuroCurator and OpenMinTeD annotations directly on PDFs.
• Make NeuroCurator easily installable, especially by scientists.

Updated on 04.10.18.

Status

Created during 2016.

Ongoing stabilization and reengineering in the branch refactor-architecture.

The branch refactor-architecture is not intended to be used by end-users.

New features, bug fixes and improvements are done on the reengineered code sections.

When a reengineered code section is stable, it's merged into the branch master and a release is published.