Iran Monitor
Codebook
Definitions of every published field in Iran Monitor. The Introduced in column records either the numbered release in which a field first appeared or, for fields that currently exist only in the live database, their planned release status — so later additions remain distinguishable from the original fields.
Generated from the tables on this page
Included records — field definitions
Fields of the included-person records published in the Iran Monitor database.
| Field | Definition | Introduced in |
|---|---|---|
| Iran Monitor ID | Permanent identifier in the form IRM-P-####. It is maintained technically and is not edited in the master workbook. | v1.0 |
| Name | Canonical public English name used by Iran Monitor. | v1.0 |
| Persian-script name | Direct Persian-script transliteration of the exact current canonical English Name, preserving the same name components and their order and adding no honorific or other component absent from the English canonical name. A live website/presentation field only; it is excluded from Version 1.1 scholarly dataset exports. | Live database (website only; not in Version 1.1 export) |
| Aliases | Alternative spellings or transliterations retained for search and disambiguation. | v1.0 |
| Role at death | Fact-checked role, rank, institutional affiliation, command responsibility, or specialist function at the time of death. Wording is qualified when precise details are not securely established. | v1.0 |
| Category | One of: Diplomatic; Intelligence/Security; Military; Nuclear/Scientific; Political; State Media; Others. | v1.0 |
| Death date | Date of death in ISO format (YYYY-MM-DD), with its stated precision: day, month, year, range or unknown. Coarser precision is never resolved to an invented day. Range (introduced October 2026) denotes a bounded multi-day interval (for example 1–2 April 2026): the ISO date is left empty and the interval is recorded in the display text. | v1.0 |
| Age at death | Age at death mechanically derived from accepted birth information and the recorded death date. Displayed as an integer, or as a supported range where the birth information permits only that; otherwise Unknown. Included in routine dataset snapshots; birth dates and birth-data sources are not exported. | v1.1 |
| Location | Place of the qualifying lethal event. | v1.0 |
| Country | Country in which the qualifying lethal event occurred. | v1.0 |
| Actor | Foreign state or non-Iranian organization to which the qualifying lethal operation is attributed under the event criterion. No separate public attribution-confidence field is used. | v1.0 |
| Event | Plain-language grouping for the operation or event associated with the death. | v1.0 |
| Circumstances | Concise description of how the person was killed and the immediate circumstances, limited to details that can be supported by the available public evidence. | v1.0 |
| Selected Sources | Up to three sources chosen to represent the principal evidentiary basis of the record collectively. They are not claim-by-claim citations and are not an exhaustive bibliography. | v1.0 |
Reviewed Exclusions — field definitions
Fields of the reviewed-candidate records published in the exclusion register.
| Field | Definition | Introduced in |
|---|---|---|
| Iran Monitor ID | Permanent Iran Monitor identifier assigned to the reviewed candidate. | v1.0 |
| Name | Canonical public English name. | v1.0 |
| Role at death | Role or function considered during eligibility review. | v1.0 |
| Date | Death date or relevant date available during review. | v1.0 |
| Reason for exclusion | Principal reason the case did not qualify for the current release. | v1.0 |
| Note | Brief explanation of the exclusion decision where needed. | v1.0 |
Discrete operations (IRM-O) — field definitions
Discrete operation records (IRM-O) are nested under event/operational-episode records (IRM-E). One IRM-E may contain zero, one or several IRM-O records. A person is linked to at most one IRM-O, which must belong to the person's own IRM-E; people whose exact discrete operation cannot be established remain linked to the IRM-E only. Fields not supported by the cited evidence are left empty (NULL) and are never inferred. On the website, operations can be browsed as a third Database mode (People | Events | Operations).
| Field | Definition | Introduced in |
|---|---|---|
| Operation ID | Permanent identifier in the form IRM-O-####. Never reused or renumbered. | Live database |
| Parent event | The IRM-E event/operational episode that contains the operation. | Live database |
| Operation name | Plain-language name of the discrete operation. | Live database |
| Operation date / precision | Date of the operation in ISO format with its stated precision (day, month, year). Coarser precision is never resolved to an invented day. Where only a bounded range is supported (for example 1–2 April 2026), the operation date is left empty and the range is recorded in the display text. | Live database |
| Time | Time of the operation, recorded only when directly supported by evidence. | Live database |
| Location / Country | Place and country of the operation, no more precise than the evidence supports. | Live database |
| Target site | The specific site struck, recorded only when identified by the cited sources. | Live database |
| Operation type | Form of the operation, for example Airstrike or Targeted airstrike. | Live database |
| Weapon / platform | Weapon or delivery platform, recorded only when directly supported. | Live database |
| Actor / Attribution note | Actor to which the operation is attributed, with a note where the evidence does not securely identify which state carried out the specific strike. | Live database |
| Operational account | Concise description of the operation limited to what the cited sources support. | Live database |
| Linked people | Included people adjudicated to have been killed in this operation. Each person has at most one operation link. | Live database |
| Operation sources | Sources supporting the operation record itself. They are distinct from, and do not replace, each person's Selected Sources. | Live database |
Related pages
The records themselves are in the Database, excluded candidates in Reviewed Exclusions, and coding rules in Methodology.