CitSci.org (www.citsci.org) is an open, comprehensive cyber-infrastructure platform for citizen science programs currently supporting 97+ programs and curating 81,400+ observations. Recognizing citizen science as a new... [ view full abstract ]
CitSci.org (www.citsci.org) is an open, comprehensive cyber-infrastructure platform for citizen science programs currently supporting 97+ programs and curating 81,400+ observations. Recognizing citizen science as a new instrument for collecting data across broad temporal and spatial scales, filling gaps, and providing additional information where none may exists, citizen science platforms (e.g. iNaturalist, eBird, and CitSci.org) are emerging as new sources for data and information. These new data sources contribute information to making science-based decisions and integrating information in synthetic research activities. If citizen science support platforms are to be positioned as valid online resources for novel, valid, and rigorous data, then we must ensure that the information provided is re-useable and of sufficient integrity and quality. Metadata (e.g., “data about data”) supports data re-use by providing essential documentation of who, what, where, when and how data are collected. Data discovery online or through automated processes requires machine-readable, structured metadata. For this reason, metadata standards are being established and adopted by many research communities and tools are being developed to create structured metadata (e.g. Darwin Core, Ecological Metadata Language). To support such standards, we are developing a suite of features (a.k.a., a metadata tool box) to make it easier for project coordinators to document metadata associated with their projects, datasheets, protocols, measurements, and sample designs. The design of these tools will be informed by monthly webinars together with stakeholders through a process of participatory design to ensure we balance the need for such metadata tools with system ease of use. We discuss challenges in balancing efforts that produce rich, standardized documentation and high quality information, with the burden placed on project coordinators who must provide such metadata. We conclude by offering suggestions to system developers who may recognize and balance similar tensions in their systems.
