Chronicles of Nature Calendar: A long-term and large-scale multitaxon database on phenology

We present an extensive, large-scale, long-term and multitaxon database on phenological and climatic variation, involving 506,186 observation dates acquired in 471 localities in Russian Federation, Ukraine, Uzbekistan, Belarus and Kyrgyzstan. The data cover the period 1890-2018, with 96% of the data being from 1960 onwards. The database is rich in plants, birds and climatic events, but also includes insects, amphibians, reptiles and fungi. The database includes multiple events per species, such as the onset days of leaf unfolding and leaf fall for plants, and the days for first spring and last autumn occurrences for birds. The data were acquired using standardized methods by permanent staff of national parks and nature reserves (87% of the data) and members of a phenological observation network (13% of the data). The database is valuable for exploring how species respond in their phenology to climate change. Large-scale analyses of spatial variation in phenological response can help to better predict the consequences of species and community responses to climate change. The recording scheme implemented at nature reserves offers unique opportunities for addressing community-level change across replicate local communities. These data have been systematically collected not as independent monitoring efforts, but using a shared and carefully standardized protocol adapted for each local community. Thus, variability in observation effort is of much less concern than in most other distributed cross-taxon phenological monitoring schemes. To enable analyses of higher-level taxonomical groups, we have included taxonomic classifications for the species in the database. The compilation of the data in a common database was initiated in the context of the project “Linking environmental change to biodiversity change: long-term and large-scale data on European boreal forest biodiversity” (EBFB), funded for 2011-2015 by the Academy of Finland, and continued with the help of other funding to OO since 2016. We organized a series of project meetings that were essential for data acquisition, digitalization and unification. These meetings were organized in Ekaterinburg (Russia) by the Institute of Plant and Animal Ecology, Ural Branch of RAS (Russian Academy of Sciences) in 2011; in Petrozavodsk (Russia) by the Forest Research Institute, at the Karelian Research Center, RAS in 2013; in Miass (Russia) by the Ilmen Nature Reserve in 2014; in Krasnoyarsk (Russia) by the Stolby Nature Reserve in 2014; in Artybash (Russia) by the Altaisky Nature Reserve in 2015; in Listvyanka, Lake Baikal (Russia) by the Zapovednoe Pribajkalje Nature Reserve in 2016; in Roztochja (Ukraine) by the Ministry of Natural Resources of Ukraine in 2016; in Puschino (Russia) by the Prioksko-Terrasnyj Nature Reserve in 2017, in Vyshinino (Russia) by the Kenozero National Park in 2018, and in St Petersburg (Russia) by the Komarov Botanical Institute of the Russian Academy of Sciences in 2019. The compilation of the data into a common database was conducted by the database coordinators (EM and CL) in Helsinki (Finland). Those participants that already held the data in digital format submitted it in the original format, and those that had the data only in paper format digitized it using Excel-based templates developed in the project meetings. Submitted data were processed by the database coordinators according to the following steps: The data were formatted so that each observation (the phenological date of a particular event in a particular locality and year) formed one row in the data table (e.g. un-pivoting tables that involved several years as the columns). The phenological event names were split into event type (e.g. “first occurrence“) and species name. The event type names (provided originally typically in Russian) were translated into English and the species names (usually provided in Russian) were identified to scientific names, using dictionaries that were partly developed and verified in the project meetings. All scientific names were periodically verified by mapping them to the Global Biodiversity Information Facility (GBIF) backbone taxonomy. We associated each data record with the following set of information fields: (1) project name, i.e. the source organization, (2) dataset name, (3) locality name, (4) unique taxon identifier, (5) scientific taxon name, and (6) event type. We imported the data records in the main database (maintained as an EarthCape database at https://ecn.ecdb.io). During the import, the taxonomic names, locality names, and dataset names were matched against already existing records. The database consists of six data files, each formatted as a .csv (comma-separated values) file. The main data are provided in the phenology table, where each row describes at which day of the year (Field Day.of.year) a particular phenological event (Field Event.type) was observed for a particular species (fields Taxon and Taxon.identifier) in a particular year (field Year) and particular study site (field Study.site) that was part of a particular project (Field Project). Each row contains also a quality indicator (field Quality), which his set to “OK” if the data point has passed all the technical validation steps described in the data paper. Cases that were highlighted by the technical validation steps and thus that may be unreliable (and that we recommend to remove from analyses) are indicated as “Event.Type outlier”, “Locality-Taxonomic.Name-Event.Type bimodal”, “Locality-Taxonomic.Name-Event.Type outlier”, “Taxonomic.Name-Event.Type bimodal”, and “Taxonomic.Name-Event.Type outlier”. The criteria for how these were defined are described in the data paper. The remaining data tables contain additional information that can be linked to the phenology table. First, the taxonomy table describes the taxonomical information (e.g. species for which the observation is made), and is linked to the phenology table through the shared fields Taxon and Taxon.identifier. Second, the phenological events table gives further information for each phenological event, and is linked to the phenology table through the shared field Event.type. Third, for data points that refer to climatic rather than to phenological events, the climatic events table gives further information for each climatic event, and is linked to the phenology table through the shared field Event.type. Fourth, the study sites table gives the longitude and latitude of each study site, and is linked to the phenology table through the shared field Study.site. Fifth, the information sources table gives the reference to the original data, and is linked to the phenology table through the shared field Project. Data files (consult with metadata.txt for details): phenology.csv (the phenology table)<br> taxonomy.csv (the taxonomy table)<br> phenologicalevents.csv (The phenological events table)<br> climaticevents.csv (The climatic events table)<br> studysites.csv (The study sites table)<br> informationsources.csv (The information sources table)

Перевод пока недоступен