MyTardis - a data management system for private lab/facility data
Python JavaScript HTML CSS Shell
Latest commit e6332c5 Oct 24, 2016 @grischa grischa committed on GitHub Merge pull request #672 from wettenhj/ldap-changes
LDAP changes for decommissioning of
Failed to load latest commit information.
docs OU=Users should be included in DN for testing authentication, Oct 19, 2016
tardis OU=Users should be included in DN for testing authentication, Oct 19, 2016
utils added documentation for single search deployment and added the ss sch… Nov 22, 2011
.dockerignore docker based testing Jun 15, 2016
.gitignore added sqlite file to .gitignore Nov 9, 2015
.gitmodules json and fcs-table parameter support Jul 9, 2015
.pylintrc WIP pylint fixes Dec 1, 2015
.pylintrc.travis transition pylintrc from travis Feb 15, 2015
CONTRIBUTING.rst documentation updates Mar 13, 2015
CONTRIBUTORS.rst first iteration of release-focused updated documentation Aug 20, 2013
COPYING.rst dynamic SFTP download docs Nov 6, 2015
Dockerfile-base small docker image size improvement Jun 15, 2016
Dockerfile-build small docker image size improvement Jun 15, 2016
Dockerfile-run small docker image size improvement Jun 15, 2016
Dockerfile-test renamed images to point to hub repo Jun 15, 2016
INSTALL.rst Fixed static file collection and added settings to documentation. Jan 18, 2012 Converted of all the *.txt files into *.rst, which looks better on Gi… Jan 16, 2012
README.rst docs restructure and update Mar 16, 2016 update Mar 16, 2016
docker-build.yml renamed images to point to hub repo Jun 15, 2016
docker-test.yml renamed images to point to hub repo Jun 15, 2016 Replaced uwsgi with gunicorn (reason: downloads were not reliable wit… Sep 6, 2013 docker based testing Jun 15, 2016 renamed default settings to Dec 8, 2015
requirements-centos.txt Updates for integration testing. Apr 8, 2016
requirements-osx.txt Back button of publication form on the first page now closes the dial… Apr 17, 2015
requirements.txt use alternative paramiko branch Aug 16, 2016
setup.cfg added setup.cfg for automated sphinx documentation build and upload May 23, 2011 removed buildout Feb 9, 2015 optional code tools submissions Jun 15, 2016
ua_parser_regexes.yaml Switch to using django-user-agent instead od smartagent May 25, 2013 removed buildout Feb 9, 2015



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