Software · Data sharing

Share behavior and imaging data in standard formats

ConductScience Data Export turns ConductVision, ConductVision Image and ConductMaze results into data packages for labs sharing data under an NIH Data Management and Sharing (DMS) Plan.

What a data package holds

Original files

Exact copies of the files in the result folder. Every file in the package has a SHA-256 checksum, so anyone can confirm it is unchanged.

Tables and a data dictionary

CSV tables, and a data dictionary that gives each column's meaning and unit. The validation report names any column the tool could not define.

NWB and OME-TIFF files

ConductVision runs with a track file of each frame's positions become NWB files, and ConductVision Image label masks become OME-TIFF files.

Dataset description

RO-Crate metadata, which describes the dataset, who made it, its license and its files in a form software can read.

Validation report

A report you can open in a browser. It lists each check, what the check found and how to fix any problem.

Draft DMS Plan row

NIH's 2026 DMS Plan format has a data types table, and the package drafts the row for its data.

How it works

Scan

The tool reads a result folder and lists the files it found and the details it still needs, such as species or pixel size.

Fill in

It starts a metadata form with what the files contain, and your lab fills in the rest.

Package

It copies the original files and adds CSV tables, a data dictionary, NWB or OME-TIFF files, metadata and checksums.

Check

It checks each part of the package against the rules for its format, using the RO-Crate, Frictionless, NWB Inspector and OME schema validators.

What the package drafts and what your lab writes

Each package drafts its own row of the plan's data types table from the files it holds.

NIH limits the whole table to 100 words, and the tool counts the draft's words against that limit.

Each package also lists the parts of the plan only your lab can write:

  • How much of the data behind publications and other findings you will share
  • When you will share the data and how long they stay available
  • Any limits on sharing, explained in up to 300 words
  • Protections for participants' privacy, rights and confidentiality, if the project has human participants
  • Genomic data, if the project generates it
  • The repository that will hold the data

Read NIH's guide to writing a DMS Plan

What your lab is responsible for

The export tool only prepares and checks the files.

Your lab writes the DMS Plan and carries out the approved version. Your lab also chooses the repository and handles consent, privacy and who may access the data.

Questions

Does the package complete my DMS Plan?
No. It gives you checked files and a data dictionary, and drafts only the data types row. Your lab writes the rest of the plan and carries it out.
Does the tool upload data to a repository?
No. The tool runs on your lab's computer and writes the package to a folder you choose. Your lab deposits it in the repository the plan names.
Does it change the files the programs saved?
No. The package holds exact copies, and the files in the result folder stay as the program saved them.
What happens when a required detail is missing?
The check fails, and the report says how to add the detail. The tool never guesses units, time zones, calibration, species, sex or age.

Request the export tool

Tell us which software your lab uses and what you plan to share. We will reply with the tool and how to set it up.