1.1. To implement a highly coordinated drought experiment requiring only nominal investment of time and resources by each investigator, but quantifying community and ecosystem responses in a wide range of terrestrial ecosystems.
1.2. To collect data from a broad range of sites in a consistent manner to allow direct comparisons of responses of ecosystems around the world to extreme drought. This is currently occurring at each site in the network and, when these data are compiled, will allow us to provide new insights into how and why terrestrial ecosystems may differ in their responses (sensitivity) to drought.
2. IDE Structure
2.1. At its heart, the IDE is a flexible, inclusive network of researchers who have all agreed to three basic network ground rules. Network participants must: (1) fund project infrastructure and implementation at their own sites, (2) exactly implement the core treatments and level 1 measurement protocols, and (3) openly share data associated with the project in a common repository.
2.2. Steering Committee. A steering committee serves to establish general guidelines for Drought-Net and IDE, including protocols, data use and timelines. This committee currently consists of the founding PIs (Smith, Phillips and Sala), and additional members (see Team). Other network participants who choose to spend significant time on network-wide Drought-Net and/or IDE management issues will be welcomed into the Steering Committee.
3. Code of Conduct
3.1. Experimental site set-up and data collection
3.1.1. All participating sites must follow the experimental protocol use the available templates for data submission available on the Drought-Net website: Protocols & Templates.
3.1.2. Any outstanding/unintentional treatments (e.g. fire, herbivore activity, harvesting or mowing) must be noted in data sheets before submission. This will allow appropriate treatment documentation and sorting for confounding effects if necessary.
3.2. Data use
3.2.1. Data will become available to network members once compiled by the data manager at Colorado State University. Data will be made publicly available on a 3-year moving window, although requests for access to newer data will generally be granted by the Steering Committee as long as there are no conflicts with ongoing papers or proposals.
3.2.2. Any participant is free to use IDE data for publication purpose, following guidelines listed in Paper Writing section. Data should be recognized as follows:
"Data were made available through Drought-Net RCN, a project funded by DEB-1354732 (M. Smith/R. Phillips/O. Sala)"
3.2.3. Data use for presentations, courses and other non-published venues should cite the Drought-Net project as above.
3.3. Paper Writing
3.3.1. By contributing data to IDE according to data submission protocols, you will automatically be included as a co-author on the core IDE papers (e.g., year 1, year 4 of drought) if you stay actively engaged (following deadlines and rules for data submission, providing appropriate contributing concepts, etc.) and in communication with the lead author. If you find that you cannot meet these requirements, we kindly ask that you opt-out of co-authorship.
3.3.2. Authorship on papers arising from IDE data will be earned through significant contribution to the scientific process, including but in addition to contributing data. Final authorship assignment is the responsibility of the lead author of the manuscript. We strongly favor being inclusive in authorship.
3.3.3. If you wish to write a paper using IDE site data, a working title and abstract should be submitted to the Drought-Net steering committee and the IDE listserv for general review one month prior to manuscript preparation. Individuals or sites interested in becoming contributing authors in the proposed paper must contact the lead author directly. As previously stated, we strongly favor being inclusive in authorship.
3.3.4. If a manuscript is proposed and subsequently abandoned for > 6 months, other interested IDE participants are encouraged to discuss with lead author about taking over the development of the manuscript.
3.3.5. While we encourage papers based on a subset of IDE data, these should be conceptually distinct from the full IDE papers. Subset papers should take special care not to compromise the power of the full Network by publishing on the main questions of IDE with a subset of the data.
3.3.6. Disputes over authorship and manuscripts will be referred to the Steering Committee for resolution.
Modified from NutNut guidelines.