If you are encountering a technical problem with Miradi, please peruse the following lists of Frequently Asked Questions (FAQs) and Known Issues. You should also make sure to look at the relevant interview wizard pages in the application itself (in many dialogue boxes you can also click the Instructions button to go the appropriate wizard page). Additionally you should check out our YouTube Channel where we explain current features or commonly asked questions in short tutorials. If none of these solve the problem, licensed Miradi users can also contact us.
Miradi is written in the Java programming language, so it should run on any operating system that supports Java applications. With that said, we are currently focusing on the "big three": Windows, Mac OS X, and Linux.
For Windows, the MiradiSetup.exe installer will offer to download and install a private copy of Java if a suitable version is not already installed.
On Mac and Linux, Java must already be installed. Current versions of Mac OS X include Java automatically, so Miradi should just work with no further action required.
Miradi is legally owned by Foundations of Success on behalf of the Conservation Measures Partnership. Miradi is governed by a committee of CMP members that is responsible for guiding the development and financial administration of Miradi. Sitka Technology Group is responsible for executing software programming decisions reached by the committee.
You first have to download the appropriate Miradi installer for your operating system from the download page of the Miradi website. Next, depending on your operating system:
Miradi is available in many languages. Registered users can download these "language packs" from the main download page. There are tutorials on our YouTube Channel that explain how to install the language files. Some languages may not be fully up-to-date with the most recent version of Miradi, in which case most of the interface will be in the desired language, and the new/untranslated portions will be in English. We have designed the software so that it is relatively easy to produce versions in other languages. We would like to develop partnerships to translate and distribute Miradi into other languages. Please contact us if you would like to help create a version in your native language.
Use the <File/Export> command to create a Miradi file (.miradi) of your Miradi project. This can then be imported by any person running Miradi. Exporting to the .xmpz2 format creates a Miradi Share project file. Read the details on the website. Additionally there are many more export formats (e.g., rtf, png, jpeg, tab-delimited) that allow you to export specified portions of your file to other applications such as Microsoft Word or Excel.
Miradi stores active files on a special Miradi directory on your computer. You can view this location (or change it) from within Miradi by going into <Edit/Preferences> and clicking on the <Data Location> tab.
The default locations on each operating system are:
In this Miradi data directory, each Miradi project is a folder (aka directory). You can move, copy, delete, or rename these folders, as long as you are careful doing so. Keep in mind that the folder itself is the Miradi project. You can also manage these files from the Welcome page of the Miradi program.
In some rare cases you may want to change the Miradi data directory. For example, if your Windows laptop normally stores "My Documents/Documents" on a network drive, and you want to work on Miradi while disconnected from the network, you will need to tell Miradi to store your data in a local directory. To do so, select <Edit/Preferences> from the initial Miradi welcome page and click on the <Data Location> tab. Next, click on <Select Location> and then specify where you want Miradi to store your files.
When uninstalling Miradi, the projects and data you have created are not removed in the process. It is perfectly safe to uninstall an older version of Miradi, and then install the newest version.
When you chose to create or import your project, Miradi created the empty project file(s) on disk. Every change you make is automatically and immediately saved to this project. This is different from a word processing or spreadsheet program, in which you need to explicitly save your work. There is no "save" command in Miradi, because your data is always saved.
Key hints to keep in mind include:
There are many ways to export your information from Miradi to other applications.
We are building Miradi using an agile programming method -- basically the software world's version of adaptive management. This involves gathering "user stories" describing what we want Miradi to do, and then rapidly and iteratively building software modules to meet these needs.
The current version of Miradi supports many, but not all, of the functions in the CMP Open Standards and it already provides significant value in helping conservation practitioners to adaptively manage their projects. But as outlined in the <Help/Coming Attractions> menu command in the application, we have many ideas for additional functions that will be forthcoming in future releases. This has two important implications for Miradi users:
If you are using Miradi 4.0 or later, you should send your file as an attachment to email@example.com. If you are using an earlier version, Miradi will sometimes displays useful debugging information on the console. Information and exceptions related to errors that you encounter are found in the file named exceptions.log. This file is stored in the Miradi Data Directory.
This file is cleared each time Miradi is opened, so if you see an error dialog, or experience unexpected behavior, please check this file before restarting Miradi. If you can repeat the error or unexpected behavior, and decide to report what you found, send us an email at firstname.lastname@example.org and either attach the exceptions.log file, or copy the contents of the file into the email. The information in the exceptions.log file will assist our developers in troubleshooting the problem.
If you think you've found a bug in Miradi, you can send an email to email@example.com. Please be as descriptive, and provide as much information as possible. Please include as many of the following as you can:
If you have any questions about this process, or would like further assistance, please email firstname.lastname@example.org, and we will be happy to assist you.
Generally you access the right-click on a track pad with a two-finger click. If your Mac has a mouse with only one button, you can either hold the down the button for a couple of seconds, or you can hold the <Ctrl> key and use the mouse button. You could also set the track pad so that the bottom right corner operates like a right-click.
You can run multiple instances of any application in Mac OS X by launching it via the command line in the Terminal. The easiest way to do so is by using the ‘open’ command to launch a new instance of Miradi even if it is already running. Type the following command in the Terminal:
open -n /Applications/Miradi-4.X.X.app/
(substitute the .X with the appropriate Miradi Version numbers - e.g., Miradi-4.2.0.app)
This will launch a new Miradi instance and lets you open various projects at the same time. Please be aware that just like on a PC, you can't run the same project twice.
- From the Mac file system, select a file of the format type you wish to change the default application (Miradi) for
(note: you need to do this for all Miradi file types individually, i.e. Miradi, xmpz2, cpmz, mpz, xmpz)
- Select a file of the appropriate format type in the Finder window
- Pull down the “File” menu and choose “Get Info” (or hit Command+i) to access the Get Info window
- Click the “Open with:” sub menu, then click on the contextual menu and select the Miradi application to associate all files of this format type with it
- Click the “Change All” button and confirm the change when requested
- Close out of Get Info window, repeat for other Miradi file format types if desired
The threat rating and the viability rating are relying on algorithms that have been developed and refined over the years by various users of the Open Standards. Please see these documents outlining the Treat Rating Rules as well as the Viability Rating Rules. Additionally, here is a document that explains the difference in between a Direct Threat, Stress and a Biophysical Factor.