Use Classifications to Standardize your Miradi Data

Classifications in Miradi are used to help teams establish and use a consistent nomenclature for common types of information used in the practice of conservation. They help teams:

• sort and filter data to support analyses, identify commonalities and differences, and create effective reports,
• communicate more effectively within teams and across teams, and
• increase shared learning across the conservation community.

In Miradi, all projects have access to a set of standard classifications used globally for key types of information (e.g. Biodiversity Targets, Direct Threats, Strategies), and teams with Miradi programs can develop program-specific classifications to apply to almost any type of Miradi data. This article covers the following topics:

• Classification basics: Standard versus program-specific classifications
• Apply classifications to Miradi data
  • Classifications in Miradi projects
  • Classifications in Miradi programs
• Develop Program-specific Classifications for Miradi Programs
• Use Classifications to Sort and Filter Data in Data Views and Report Documents

Classification Basics: Standard versus Program-Specific Classifications

Classifications in Miradi are hierarchical systems of nomenclature applied to one or more Miradi data elements. For example, the Conservation Measures Partnership (CMP) Threats Classification 2.0 is applied to the Direct Threat factor type in Miradi. It classifies Direct Threats commonly addressed in the practice of conservation into 11 high level threats, each with one or more more detailed threats.

When applying the threat classification to Direct Threat content in a Miradi project, teams can choose whether to use the high level threat classes (1 - 11 below), or the more detailed threat classes (e.g. 1.1 or 9.3), depending on the level of detail that is most useful for a project team.

Why classify threats (or other conservation data)? 

Classifying Direct Threats using this standard classification system helps teams identify when they are talking about different threats, or when they are really working with the same threat but using different names. For example, one project team might have identified the threat of “cattle”, another “grazing”, and yet another “beef production,” but they are all likely dealing with the same issue, 2.3 Livestock Farming & Ranching.

By using classifications to classify data in the Miradi project database on the "back end", teams are then free to use language more familiar to the project partners and stakeholders in the working documents, while still being able to maintain high quality data that supports cross-project learning, roll-ups, analysis, and communication with the global conservation community.

Miradi provides a set of standard, global classifications for all Miradi projects, and Miradi programs have the option to develop and apply their own program-specific classifications.

Standard Classifications

All Miradi projects have access to four standard classifications:

• Countries 1.0 - Classify entire Miradi projects geographically
• IUCN Habitat Classification v3.0 - Classify Biodiversity Targets
• CMP Threats Classification v2.0 - Classify Direct Threats (NOTE: An older version 1.1 is also available in Miradi and an updated IUCN/CMP Direct Threats classification is expected later in 2023)
• CMP Conservation Actions 2.0 - Classify Strategies (NOTE: An older version 1.0 is also available in Miradi and an updated Actions classification is expected in 2024)

Read more about how to Apply Classifications to Miradi Data and how to Use Classifications to Sort and Filter Data. 

Program-specific Classifications

Teams working in a Miradi program space with multiple projects also have the option to create their own program-specific classifications. Program classifications are often applied to projects (as shown in the examples below). They can also be applied to most Miradi factors (targets, results, strategies, etc.), Miradi factor elements (indicators, goals, objectives, etc.), and other elements such as People and work plan assignments.

Program classifications can be complex or simple.  An example of a complex classification is Bush Heritage’s use of a multi-level list of Australian geographic locations called “IBRA” (Interim Biogeographic Regionalisation for Australia, Version 7):

An example of a simple classification is Bush Heritage’s “Organisation Unit” list:

These are just two of eighteen Program classifications used by Bush Heritage to help them create custom Miradi reports and to connect their Miradi work plan to their accounting system. 

Read more about Classifications in Miradi Programs and how to Develop Program-specific Classifications for your Program.

Apply Classifications to Miradi Data

Classifications in Miradi Projects

When working in a Miradi project, Classifications can be viewed and edited in the Factor Properties panel for any relevant factors. For example, Biodiversity Targets are associated with the standard IUCN Habitat Classification 3.0 and assignment to a specific class can be made by opening the Factor Properties for a Target, scrolling down to the Classification section, and editing the classification "selection". Descriptions of each value can be found by hovering over the "i" icon next to the name of each value.

In addition to diagram view, classifications can be accessed in the tree views in a factor's properties panel. For example, in the Actions tree shown below, Strategies can be associated with the original IUCN/CMP Action Classification 1.0, or the more recent, updated CMP Conservation Actions 2.0. 

To view and edit all of the classifications in a Miradi project, navigate to REPORTS & DATA > Classifications. This table shows all of the factors in the Miradi project that are associated with at least one classification. 

1. The Classification column identifies all of the classifications available for a specific factor. In the case above, Targets can only be associated with the IUCN Habitats 3.0 classification, while Direct Threats can be associated with the older IUCN/CMP Threats 1.1 classification, or the newer CMP Threats 2.0 classification. Your team can choose which classification to use.
2. The Selection column shows which value has been assigned to the specific factor in your Miradi project. For example, target A. Coral reefs is assigned the 9.8: Coral Reefs value, while Seabirds are assigned 13.1: Sea Cliffs and Rocky Offshore Islands since that is the habitat they use.

To edit the selection for a specific factor, hover over the selection (or blank cell if there is no selection yet) and use the Edit pencil to change or remove the assignment. (NOTE: You must have editor access to the project to change a selection).

Note that although the examples above only show the standard classifications for the example factors, if a program has developed program-specific classifications, they will be accessible and editable in all the same views along with the standard classifications.

Classifications in Miradi programs

Miradi programs have the option to develop program-specific classifications. These program classifications can be applied to almost any factor, from Targets, Threats and Strategies, to Indicators, Goals and Objectives, Resources and Expense assignments, Results Chain and Situation Model diagrams, and even the entire Miradi projects.

Some examples of program-specific classifications developed by Miradi users include

• Expense and Accounting classifications
• Rating or Prioritization Scale (e.g. High, Medium, Low)
• Content Status (e.g. Active, Draft, Abandoned, Archived)
• Geographies (specific regions, provinces, watersheds, etc)
• Thematic approaches (Community Conservation, Habitat Restoration, Education and Outreach, etc)

Access Classifications in Miradi Programs

All of the classifications available to factors in a program, including standard and program-specific classifications, are found at the program level under REPORTS & DATA > Classifications. In the first example below, the program only uses the standard classifications that are built into all Miradi projects. The standard classifications are applied to four factors in Miradi: Targets, Threats, Strategies and the entire Project, as shown on the left.

In contrast, in the example below, the program has developed numerous classifications applied to multiple Miradi factors. (The names have been greyed out to protect the organization's privacy)

To see what classifications are available for a Miradi factor, click on the factor name on the left. For example, Targets are associated with a single classification, IUCN Habitats 3.0.

In contrast, Direct Threats are associated with two classifications: IUCN/CMP Threats 1.1 and the newer CMP Threats 2.0 classification.

All of the details, including the names and descriptions for each value in a classification can be viewed online by expanding and collapsing the classifications in the right-hand window. A program's complete set of classifications can be exported as a .xls or .csv file using the EXPORT button in the upper right. 

Classifications are bundled into a program's "taxonomy set"

Classifications are bundled into "taxonomy sets" for a program. A program's taxonomy set is one of the three components that makes up a program's unique template: the "starter template project", the "taxonomy set" and the "Miradi object configuration". See Miradi Program Templates for a complete description of program templates.

• The "taxonomy set" is the collection of standard classifications and, if applicable, the program classifications available to projects that use a specific program template. (NOTE: If a program's Template name (1) and the Taxonomy Set name (2) are different, the template includes program classifications.)

• The "Miradi object configuration” (3) defines which factor(s) apply to which classifications, and also defines some of the attributes (name, single or multi-select, etc.) of each configuration. Programs can apply a program-specific classification across several different factor types (for example, Puget Sound Recovery has a “Vital Signs” program classification that is applied to five different factor types.)  

Programs who actively use their own program classifications strive to keep all of their projects updated to their latest template.  This ensures accuracy and completeness in their custom reports.  Programs that have projects with different Miradi versions will have more than one active template. See Develop Program-specific Classifications for Miradi Programs for more information on how to develop and manage your program-specific classifications.

Develop Program-specific Classifications for Miradi Programs

Program Administrators have complete control over any program classifications designed for a program, but at this time the Program Administrator must contact Miradi support to add new or edit existing program-specific classifications. In the future, we plan to provide Program Administrator access to develop and edit classifications directly in the Miradi application.

If you would like to add program-specific classifications to your program, contact Miradi support. Below is the information we will ask you to provide:

• Miradi Object - What the list classifies (e.g. Project, Target, Threat, Strategy, etc. See * below for a complete list)
• Classification Name - The name of your list that will be publicly visible to your Miradi projects (e.g. Priority Regions)
• Program Taxonomy List Name -  The full name of the list used to manage the classification in Miradi Share (e.g. My Program Priority Regions v2.0)
• Classification Description - Brief description of the classification to help users understand the purpose of the classification.
• Leaf / Any Node - If a list has multiple levels (see example Threat Classification 2.0 with two levels), can the user select "Any Node" (e.g. Threat 1 or Threat 1.1), or only at the most detailed, "Leaf" level (e.g. Threat 8.1.1 but not Threat 8 or Threat 8.1).
• Multi / Single Select - Can the user select multiple values (check boxes), or only a single value (radio button)
• List of values in the classification**, including for each value
  • Code - A unique identifier (e.g. 1, 1.1 or A, A.1)
  • Name - The name of the value (e.g. Coral Reefs)
  • Description - A brief description of the value (enter 'none" if you do not provide a description)
  • Example - optional, enter 'none' if no examples
  • Guidance - optional, information to help users select the appropriate value(s)

*The full list of Miradi objects that can be classified:

• Project
• Assumptions, Subassumptions
• Biodiversity Target, Human Wellbeing Target, Key Ecological Attribute, Stress
• Direct Threat
• Situation Model, Contributing Factor, Biophysical Factor
• Results Chain, Intermediate Result, Threat Reduction Result, Biophysical Result
• Objective, Goal, Indicator, Method
• Strategy, Task (Activity, Monitoring Activity and Task), Output
• Project Resource, Resource Assignment, Expense Assignment

**An example from the CMP Threats 2.0 classification of the information recommended for program-specific classifications:

Use Classifications to Sort and Filter Data in Data Views and Report Documents

Classifications are a powerful tool to help teams analyze and understand their data and relate content across multiple Miradi projects. Once Miradi project content has been classified, classifications can be used to sort and filter data in Data Views and in Report Documents at the project and program levels.

Access Classifications in Data Views

Standard and program-specific classifications are included for relevant factors in many Data Views. (See Viewing and Analyzing Miradi Data in Data Views for a basic introduction to accessing and using Data Views.)

Classifications can be used to sort and filter the data in Data Views. In the example below, the standard classification IUCN/CMP Conservation Action v1.1 has been used to classify all Strategies in the Miradi project and the Strategy + Activity Progress Table has then been sorted and filter to show all Activities by Conservation Action v1.1 type.

Miradi users can choose whether or not to include classifications as a column in the Data View using the Columns menu on the far right.

Use the Filters tool on the far right to select which values in the classification to include in your Data View.

Users with sufficient permissions at the project level (Project Editor or higher) or program level (Program Admin or higher) can save their sorted and filtered data views using the Custom Data Views tool on the right. See more about how to Save Custom Data Views.

Classifications in Program-Level Data Views Support Cross-Project Summaries and Analysis

Using the same tools as introduced above in Access Classification in Data Views, classifications can help teams makes sense of Miradi data across multiple projects within programs. For example, in the program-level Data Views, open the Target Summary Data View and use the IUCN Habitats v3.0 classification to sort and filter all of the Targets across all Miradi projects in the program.

Next, group by habitat type to quickly see all Miradi projects that are working on specific habitat types.

The filtered and sorted Target Summary data view now shows all the Targets (1) across all projects in the program (2) that are classified under each IUCN Habitat Type (3).

The same tools can be used to sort and filter data within programs using any of the standard or program-specific classifications applied to Miradi factors. Classifications are also included in data exported as .xls or .csv files.

Classifications in Report Documents

Standard and program-specific classifications can be used to sort and filter the data included in custom report documents that are exported to Word. Currently, the standard reports do not use any of the classifications. (See Report Documents in Projects & Programs for a basic introduction to using report document templates.)

Classifications can be included in report document templates in multiple ways to shape the content that is included in a report output:

• Filter the content that is included in a report to only specific values within a standard or program-specific classification, e.g. only include content related to Coral Reefs (IUCN Habitat class 9.8 Coral Reefs) or Residential & Commercial Development (IUCN/CMP Direct Threat class 1). If using program-specific classifications, report templates can be designed to focus on specific Targets, Threats, approaches, themes or geographies of importance to the program.
• Sort content based on the classification ID or Name, e.g. present Strategies associated with IUCN/CMP Direct Threats in the order of Direct Threat classes 1 to 11. If using program-specific classifications, report templates can be designed to present content in the order of programmatic priorities, based on classifications.
• List content associated with a specific class or set of classes, e.g. report out all Activities related to CMP Conservation Action classes C.7 Legal & Policy Frameworks and B.4 Law Enforcement & Prosecution.