> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/plugins/first-party-ango-plugins/stage-export.md).
# Stage Export
## Overview
The Stage Export plugin is an export plugin that downloads workflow-stage activity and annotation-count information for your project.
Use this plugin when you need a CSV report showing which stages a task passed through, who labeled or reviewed it, how long work took, and how many labels were present at each stage.
## Plugin Functionality
The Stage Export plugin creates a ZIP file containing a CSV report for the selected tasks.
The export includes:
* Batch
* Stage
* External ID
* Task ID
* Labeler and reviewer names by stage
* Labeling and review dates, start times, end times, and durations
* Review task status by review stage
* Number of pages
* Counts of classifications, tools, tool classifications, and relations by stage
* Optional classification answer columns by stage
When both `gold_stage` and `evaluation_stage` are provided, the plugin also adds label comparison metrics between the two stages, including accepted labels, fixed labels, precision, recall, and accuracy.
## Plugin Configuration
From the **Stage Filter** field, pick the stages containing the tasks you'd like to export. Similarly, from the **Batch Filter** field, you may select one or more batches. By default, all tasks are exported from all batches.
If you wish to receive an email when the export is complete, toggle **Send Email** on.
You may vary a number of settings related to your export from the **Config JSON** field. Each option is detailed below:
```json
{
"start_date": "2020-12-31",
"end_date": null,
"duration_unit": "sec",
"gold_stage": null,
"evaluation_stage": null,
"ignored_schema_ids": [],
"include_key_frames_only": true,
"logging_frequency": 0
}
```
* **"start\_date":** Start date for filtering stage history included in the export (YYYY-MM-DD).
* Example:
* "start\_date": "2020-12-31"
* **"end\_date":** End date for filtering stage history included in the export (YYYY-MM-DD).
* Example:
* "end\_date": "2021-12-31"
* **"duration\_unit":** Unit used for duration columns.
* Example:
* "duration\_unit": "sec"
* **"gold\_stage":** Optional stage used as the reference stage for comparison metrics.
* Example:
* "gold\_stage": "Review"
* **"evaluation\_stage":** Optional stage evaluated against the gold stage.
* Example:
* "evaluation\_stage": "Label"
* **"ignored\_schema\_ids":** List of schema IDs to exclude from the stage comparison metrics.
* Example:
* "ignored\_schema\_ids": \["12345", "12346"]
* **"include\_key\_frames\_only":** Included in the default configuration for consistency with video export plugins. The Stage Export plugin exports stage and annotation-count data from the selected export scope.
* Example:
* "include\_key\_frames\_only": true
* **"logging\_frequency":** Defines how frequently progress logs are displayed; setting this value to 0 disables progress-frequency logging.
* Example:
* "logging\_frequency": 0
* "logging\_frequency": 100
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.imerit.net/plugins/first-party-ango-plugins/stage-export.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
