{"id":19784057,"url":"https://github.com/openeventdata/plover","last_synced_at":"2026-02-07T05:31:13.052Z","repository":{"id":48306954,"uuid":"71364206","full_name":"openeventdata/PLOVER","owner":"openeventdata","description":"Next generation event data ontology","archived":false,"fork":false,"pushed_at":"2024-02-04T13:06:02.000Z","size":10974,"stargazers_count":73,"open_issues_count":5,"forks_count":7,"subscribers_count":12,"default_branch":"master","last_synced_at":"2025-07-27T01:41:14.848Z","etag":null,"topics":["event-data","nlp","political-science","shared-tasks"],"latest_commit_sha":null,"homepage":null,"language":"TeX","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/openeventdata.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2016-10-19T14:12:10.000Z","updated_at":"2025-07-08T08:40:46.000Z","dependencies_parsed_at":"2023-12-22T15:11:08.577Z","dependency_job_id":"446eb812-be55-4392-81ab-ecfa272ee707","html_url":"https://github.com/openeventdata/PLOVER","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/openeventdata/PLOVER","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/openeventdata%2FPLOVER","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/openeventdata%2FPLOVER/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/openeventdata%2FPLOVER/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/openeventdata%2FPLOVER/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/openeventdata","download_url":"https://codeload.github.com/openeventdata/PLOVER/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/openeventdata%2FPLOVER/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29187174,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-07T05:07:31.176Z","status":"ssl_error","status_checked_at":"2026-02-07T05:06:15.227Z","response_time":63,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["event-data","nlp","political-science","shared-tasks"],"created_at":"2024-11-12T06:10:12.660Z","updated_at":"2026-02-07T05:31:13.034Z","avatar_url":"https://github.com/openeventdata.png","language":"TeX","funding_links":[],"categories":[],"sub_categories":[],"readme":"# PLOVER\n\n![plover_icon](https://github.com/openeventdata/PLOVER/blob/master/media/plover_icon175.png \"PLOVER logo\")\n\nPLOVER–Political Language Ontology for Verifiable Event Records–is a\nnext generation political event coding specification under development by the\nOpen Event Data Alliance (http://openeventdata.org/) which is intended\nto replace the earlier\n[CAMEO] (http://eventdata.parusanalytics.com/data.dir/cameo.html)\nsystem. \n\nThe full PLOVER codebook is available in the repo\n[above](https://github.com/openeventdata/PLOVER/blob/master/PLOVER_Manual.pdf),\nand a short introduction to PLOVER and event data is below.\n\nThere is currently a near-real-time PLOVER-coded global event data set on Dataverse at https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/AJGVIT. Extensive details are available at these two open-access papers:\n\nHalterman, Andrew, Philip A. Schrodt, Andreas Beger, Benjamin E. Bagozzi and Grace I. Scarborough. 2023. “Creating Custom Event Data Without Dictionaries: A Bag-of-Tricks.” Working paper presented at the International Studies Association, Montreal, March-2023. [arXiv link](https://arxiv.org/abs/2304.01331)\n\nHalterman, Andrew, Benjamin E. Bagozzi, Andreas Beger,  Philip A. Schrodt, and Grace I. Scarborough. 2023. PLOVER and POLECAT: A New Political Event Ontology and Dataset.” Working paper presented at the International Studies Association, Montreal, March-2023. [socArXiv link](https://osf.io/preprints/socarxiv/rm5dw/)\n\n## Event Data and Ontologies\n\nEvent data in political science is a structured way of recording interactions\nbetween political actors described in text. For instance, a researcher\nencountering the sentence \n\n\u003e A town in western Sudan's South Kordofan state has been recaptured by Sudanese\n\u003e government forces from the rebel Sudan People's Liberation Army (SPLA).\n(AFP_ENG_19970408.0772)\n\nmight want to represent it as ACTOR = \"Sudanese military\", EVENT = \"capture\nterritory\", TARGET = \"SPLA\", a process that can be applied over hundreds of\nthousands of reports to create datasets of thousands of such events for\nanswering research questions. \n\nThe software to extract and categorize these events exists (see OEDA's\n[Petrarch2](https://github.com/openeventdata/petrarch2), for instance), but all\nevent data systems require an ontology defining what actors events will be\nrecorded and how they will be defined.\n\nOntologies face difficult tradeoffs: broader groupings of event types and\nactors are easier to define and implement, are easier to work with, and provide\ndata at a useful level of aggregation, especially analyzed globally. More\nspecialized and specific ontologies will sometimes be necessary for answering\ncertain research questions and allow more granular and subnational study, but\nare more difficult to implement and may provide distinctions that are not\nuseful to most researchers. In the example above, should the event be\ncategorized as a general \"seize\" event? Or a more specific \"capture territory\"?\nShould the target be the group the land was taken from, or should we think\nabout the territory itself as the target. If the group it was taken from,\nshould the target here be coded as a general \"Sudanese rebel\" or the very\nspecific \"SPLA\"? \n\nThe best level of detail will depend on the question and resources of the\nresearcher.  PLOVER is a new event data ontology that choses to be more\ngeneral, easier to implement (including across languages), and at the level of\ndetail demanded by most existing users of event data. At the same time, PLOVER\ndefines and provides guidance on making \"PLOVER-compliant extensions\" that will\nfit into the ecosystem of tools for creating and analyzing PLOVER event data.\n\n\nPLOVER event categories \n====================\n\nPLOVER defines 18 event types, many of which are aggregations of older CAMEO\ncodes:\n\nCAMEO code | CAMEO text | PLOVER category |\n--- | --- | --- |\n01 | MAKE PUBLIC STATEMENT | dropped |\n02 | APPEAL | dropped |\n03 | EXPRESS INTENT TO COOPERATE | AGREE |\n04 | CONSULT | CONSULT |\n05 | ENGAGE IN DIPLOMATIC COOPERATION | SUPPORT |\n06 | ENGAGE IN MATERIAL COOPERATION | COOPERATE |\n07 | PROVIDE AID | AID |\n08 | YIELD (081 to 083) | CONCEDE |\n08 | YIELD (084 to 087) | RETREAT |\n10 | DEMAND | DEMAND |\n11 | DISAPPROVE | DISAPPROVE |\n12 | REJECT | REJECT |\n13 | THREATEN | THREATEN |\n14 | PROTEST | PROTEST |\n15| EXHIBIT FORCE POSTURE | MOBILIZE |\n16 | REDUCE RELATIONS | SANCTION |\n17 | COERCE | COERCE |\n18,19,20 | ASSAULT, FIGHT | ASSAULT |\n\nPLOVER quad categories\n----------------------\n\nMany users of event data aggregate events into four categories in a 2x2 of\ncooperation--conflict and verbal--material. Those categories are defined in\nterms of their constituent categories here:\n\nQuad category | PLOVER categories |\n--- | --- |\nVerbal cooperation | AGREE, CONSULT, SUPPORT, CONCEDE |\nMaterial cooperation | COOPERATE, AID, RETREAT, INVESTIGATE |\nVerbal conflict | DEMAND, DISAPPROVE, REJECT, THREATEN, SANCTION |\nMaterial conflict | PROTEST, CRIME, MOBILIZE, COERCE, ASSAULT |\n\nMigrating From CAMEO \n---------------------\n\nThe existing standard ontology for event data is\n[CAMEO](http://eventdata.parusanalytics.com/data.dir/cameo.html). Users who are\nfamiliar with CAMEO may be interested in the differences between CAMEO and\nPLOVER.\n\n-  A set of standardized names (\"fields\") for JSON\n   records are specified for both the core event\n   data fields and for extended information such as geolocation and\n   extracted texts. Most of these fields are optional but standardized\n   field names will allow for the development of common utilities, which\n   cannot be done with the current proliferation of incompatible CSV and\n   tab-delimited formats.\n-  Only the 2-digit event 'cue categories' have been retained from\n   CAMEO: our hope is that these are sufficiently broad and distinct\n   that it will be possible to achieve a reasonably high level of human\n   inter-coder agreement— hence \"verifiable\"—on the coding categories,\n   and that can be consistently implemented, across all categories, in\n   automated systems. These are defined in much greater detail than they\n   were in WEIS and CAMEO.\n-  Much of the detail previously incorporated in the 3- and 4-digit CAMEO categories is\n   now reflected in category-specific \"mode\" fields and a general \"context\"\n   field: in effect, this \"category-mode-context\" scheme covers the \"what-how-why\" of\n   the event. We anticipate these will be much easier to systematically code\n   than the 250 or so hierarchically-arranged numerical codes of CAMEO. The \"context\" field also to handles\n   issues such as refugees, disease, natural disaster, elections, parliamentary\n   processes and cyber-security.\n-  The CAMEO 01 and 02 categories dealing with comments have been\n   eliminated.\n-  A new category has been added for criminal behavior.\n-  The WEIS/CAMEO YIELD category has been split into verbal (CONCEDE) and material (RETREAT) components.\n-  The complexity of substate actor codes has been limited, and the\n   allowable substate modifiers have been substantially simplified.\n-  The \"target\" is optional in some categories.\n-  Both the source and target fields can have compound actors, rather than \n   dealing with compounds by duplicating event.\n-  'dead', 'injured' and 'size' fields are available for recording information\n   on the magnitude of acts of violence and protests.\n-  In the near future, we are hoping to make available a large corpus of\n   \"gold standard records\" for validation purposes: these will include\n   Spanish and Arabic cases as well as English. The current release\n   has a file of English-language gold standard records derived from\n   from the CAMEO manual.\n\n\nWhy \"PLOVER\"?\n=============\n\n[Plovers](http://www.rspb.org.uk/discoverandenjoynature/discoverandlearn/birdguide/name/r/ringedplover/)\n(Charadriidae) are a globally-distributed family of short-billed\ngregarious wading birds who spend their lives frantically poking through\nendless stretches of sand and muck trying to find something of interest.\nIt is difficult to imagine a better analogy to the process of coding\nevent data.\n\nDescription of files in repository\n==================================\n\n* **PLOVER_Manual.pdf/.tex**\n\n   Version 0.8 draft which is being implemented by the Political Instability Task Force\n      \n* **PLOVER.bib**\n\n   BibTex entries for the manual\n\n* **plover_reference.html**\n\n   Basic reference for the PLOVER event categories in HTML format\n      \n* **gold_standard_records/PLOVER_GSR_CAMEO.txt**\n\n   This is a JSON file of the example sentences from the CAMEO 1.1b3 manual classified by PLOVER categories. The CAMEO LaTeX markup indicating source, target and event texts has been converted to a simple in-line markup; some locations have been added manually. The details of the coding are found in the files *PLOVER_GSR_CAMEO_readme.tex/pdf* and the version of PLOVER being coded is in the older file *plover-manual_draft.0.6b1.pdf*.\n   \n* **CAMEO-PLOV.txt**\n\n   Translation table for CAMEO to PLOVER: this is still something of a draft but will get you started\n\nAcknowledgments\n===============\nThis program was developed as part of research funded by a U.S. National Science Foundation \"Resource \nImplementations for Data Intensive Research in the Social Behavioral and Economic Sciences (RIDIR)\" \nproject: Modernizing Political Event Data for Big Data Social Science Research (Award 1539302)\n\n\nAny opinions, findings, conclusions or recommendations in this document are [only *probably* still] those of [at least one of] the authors and do not necessarily reflect the views of the National Science Foundation, or any company or government agency employing or funding the authors or otherwise contributing to the document.\n\nThis work was partially supported by the Political Instability Task Force (PITF). The PITF is funded by the Central Intelligence Agency. The views expressed in this codebook are the authors' alone and do not represent the views of the US Government.\n\nThis work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fopeneventdata%2Fplover","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fopeneventdata%2Fplover","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fopeneventdata%2Fplover/lists"}