MyTardis - a data management system for private lab/facility data
Python HTML CSS JavaScript Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update Jul 12, 2018
docs Update SFTP user docs and add sections on SSH key management Aug 14, 2018
features Switching from PhantomJS / Splinter to Headless Chrome / Selenium Jul 12, 2018
js_tests Upgrade Bootstrap to v2.3.2 (further upgrades beyond v2.3.2 are planned, Aug 3, 2018
tardis Rename SFTP to Aug 14, 2018
utils added documentation for single search deployment and added the ss sch… Nov 22, 2011
.codacy.yml Tell Codacy to ignore the Bootstrap v3 bundled with "Push To". Aug 10, 2018
.coveragerc Showing missed lines in test coverage report Jul 12, 2018
.dockerignore docker based testing Jun 15, 2016
.eslintignore Fixing some style issues Jul 12, 2018
.eslintrc.angular Adding some QUnit tests for jQuery code and starting to move jQuery Jul 12, 2018
.eslintrc.jquery Fixed some more style issues Jul 12, 2018
.gitignore Updating .gitignore to whitelist sftp dir Aug 14, 2018
.gitmodules json and fcs-table parameter support Jul 9, 2015
.jshintrc Fixing up some style issues identified by JSHint May 10, 2017
.pylintrc Added the pylint-django plugin Jul 12, 2018
.pylintrc.travis transition pylintrc from travis Feb 15, 2015
.pyup.yml configuring Nov 22, 2016
CONTRIBUTING.rst Adding, and scheduling to be deprecated in Jul 12, 2018
CONTRIBUTORS.rst first iteration of release-focused updated documentation Aug 20, 2013
COPYING.rst dynamic SFTP download docs Nov 6, 2015
Dockerfile-base Using newer npm version for CI builds, Jul 12, 2018
Dockerfile-build A recent setuptools version is needed to build a wheel for the Jul 12, 2018
Dockerfile-run small docker image size improvement Jun 15, 2016
Dockerfile-test Using newer npm version for CI builds, Jul 12, 2018
Gruntfile.js Fixed some style issues Jul 12, 2018
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 Updating to specify latest official release (v3.8.1) Jul 12, 2018 Remove reference to requirements-osx.txt Aug 5, 2018
docker-build.yml renamed images to point to hub repo Jun 15, 2016
docker-test.yml Fix for #998 May 11, 2018 Replaced uwsgi with gunicorn (reason: downloads were not reliable wit… Sep 6, 2013 Removing ipython which is not required to run MyTardis Jul 13, 2018 Remove, and use default_settings instead. Jul 30, 2018 Remove, and use default_settings instead. Jul 30, 2018
package-lock.json Adding ESLint check for facility_view.js (AngularJS) Aug 5, 2018
package.json Switch to jQuery ajax and enable jQuery eslint checks Aug 14, 2018
requirements-base.txt Update bleach from 2.1.3 to 2.1.4 Aug 16, 2018
requirements-docs.txt Update sphinx-rtd-theme from 0.4.0 to 0.4.1 Jul 29, 2018
requirements-mysql.txt Update mysqlclient from 1.3.12 to 1.3.13 Jun 27, 2018
requirements-postgres.txt Update psycopg2-binary from 2.7.4 to 2.7.5 Jun 17, 2018
requirements-test.txt Update selenium from 3.13.0 to 3.14.0 Aug 2, 2018
requirements.txt Moving test-specific requirements to requirements-test.txt and Jul 13, 2018
setup.cfg Switching from PhantomJS / Splinter to Headless Chrome / Selenium Jul 12, 2018 Both and are really just in any Jul 12, 2018 Using newer npm version for CI builds, Jul 12, 2018
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 began at Monash University to solve the problem of users needing to store large datasets and share them with collaborators online. Its particular focus is on integration with scientific instruments, instrument facilities and research storage and computing infrastructure; to address the challenges of data storage, data access, collaboration and data publication.


Key features for users

The MyTardis data management platform is a software solution that manages research data and the associated metadata. MyTardis handles the underlying storage to ensure that data is securely archived and provides access to the data through a web portal. Data hosted in MyTardis can also be accessed via SFTP.


Key features for instrument facilities

MyTardis takes care of distributing data to your users. Its instrument integration technology takes care of securely and automatically shifting data from instrument to repository and makes it accessible by the right users.


Developing for MyTardis

MyTardis is mostly written in the Python programming language and is built on top of the Django web framework. A complete installation of the service also includes an Elasticsearch index, a RabbitMQ-based task queue, an Nginx server, and a PostgreSQL database.

To set up and manage these services we employ the SaltStack orchestration software and cloud technologies.


Find out more

Project homepage

The source code is hosted at

Documentation at includes

  • User documentation
  • Administrator documentation
  • Developer documentation

The wiki at includes

  • Links to MyTardis add-ons, including apps and post-save filters
  • Information about MyTardis community events

Known deployments

Related projects and repositories


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, the latest release is 3.8.1, tagged from the series-3.8 branch. Follow this branch for your production installation and perform version upgrades manually.

Each bugfix or set of fixes bumps the minor version and each new release is tagged, eg. 3.8.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