Skip to content
MyTardis - a data management system for private lab/facility data
Python JavaScript HTML CSS Shell
Latest commit de8f0fe May 26, 2016 @grischa grischa Merge pull request #631 from jasonrig/push-to-updates-18-may
Push to updates 18 may
Failed to load latest commit information.
utils added documentation for single search deployment and added the ss sch… Nov 22, 2011
CONTRIBUTING.rst documentation updates Mar 13, 2015
INSTALL.rst Converted of all the *.txt files into *.rst, which looks better on Gi… Jan 17, 2012
README.rst docs restructure and update Mar 17, 2016



Documentation Status Semaphore build status Codacy Badge Coveralls Badge

MyTardis is a multi-institutional collaborative venture that facilitates the archiving and sharing of data and metadata collected at major facilities such as the Australian Synchrotron and ANSTO and within Institutions.

An example of the benefit of a system such as MyTardis in the protein crystallography community is that while the model coordinates and (less often) the structure factors (processed experimental data) are stored in the community Protein Data Bank (PDB) the raw diffraction data is often not available. There are several reasons why this is important, which can be summarised as:

  • The availability of raw data is extremely useful for the development of improved methods of image analysis and data processing.
  • Fostering the archival of raw data at an institutional level is one the best ways of ensuring that this data is not lost (laboratory archives are typically volatile).

Find out more

Project homepage

The source code is hosted at

Documentation at includes

  • User documentation
  • Administrator documentation
  • Developer documentation


The default branch on GitHub is develop. This is the cutting edge development version. Please DO NOT use this in production, as it may have bugs that eat your data.

The master branch is the current stable release with all the latest bugfixes included. It will move to newer versions automatically. Follow this branch if you want to stay up to date in a production environment.

Each version has its own branch named by version number. At the time of writing this is 3.7. Follow this branch for your production installation and perform version upgradres manually.

Each bugfix or set of fixes bumps the minor version and each new release is tagged, eg. 3.7.2. Use tagged releases if you are paranoid about changes to the code you have not tested yourself.

To follow development, please see the contributing section below.

Reporting Bugs

Bug reports and feature requests can be made via our public issue tracker.


New contributors are always welcome, however all developers should review the pull-request checklist before making pull requests.

For any wishes, comments, praise etc. either open a GitHub issue or contact us.

Active developers are also welcome to join our Slack team.

Contact details can be found on

Something went wrong with that request. Please try again.