Why use mx

From mx Help Wiki
Revision as of 18:48, 16 February 2007 by Matt (Talk | contribs)

Jump to: navigation, search
  1. mx is completely web based. Your data goes with you wherever you have access to the web.
  2. The core object in mx is the OTU, not a taxon name. This means your can handle a virtually unlimited number of taxonomic concepts in one place. For instance you can track morphospecies along with described species, genera with manuscript names, groups of specimens, or whatever circumscription that you actually do work with.
  3. mx supports multiple projects each with multiple users, with some components (taxonomic names, references (soon), ontologies) shared across projects. This is ideal for labs with members that study a range of different taxa with some overlap between groups.
  4. mx contains a cool matrix builder. Once you code an OTU for a character is coded in all matrices that combination occurs in. This allows you to rapidly test data partitions, new characters, or the effect of adding or removing taxa.
  5. mx has cool AJAX search functionality, just start typing and the database automatically starts being queried.
  6. You can attach images and tags to nearly every object in mx. This universality lets you group, annotate, or illustrate everything.
  7. mx is a Ruby on Rails application, so you can take advantage of all the cool AJAX and plugin code (like this) that community develops.
  8. The project is open source, and all the necessary components are free.
  9. Contributions made to the sourcecode benefit the taxonomic community as a whole. For instance if you create a new view or fancy search your helping not just you're own project, but everyone else too.
  10. mx links to Morphbank, so you can store your images there, and attach them to your data in mx.
Personal tools