PROV-ES Hack-a-thon
Earth Science Data Systems across NASA play a critical role in data processing and analysis of NASA datasets. However, there is a growing need to provide the provenance of these datasets as scientists increasingly need to assess the lineage of the data products to improve their understanding and trust of the science results. Lessons learned from Climategate show that there is public demand for more transparency and understanding in the science process. Science data systems are key to enabling the capture, management, and use of production provenance information. Science analysis now also may involve merging multi-sensor datasets where lineage can facilitate the understanding of the data. But there does not exists a formal recommendation for an interoperable standard for provenance representation for use in NASA's Earth Science Data Systems.
During 2013 and 2104, the Provenance - Earth Science (PROV-ES) Working Group primarily focused on defining extensions to the World Wide Web Consortium (W3C) PROV standard, and the technical aspects of an initial implementation of the specification to capture and explore lineage information for some sample projects. Technical work has been progressing through funded projects to mature the technology for capturing lineage information and make it easily viewable, understandable and useable. The NASA Earth Science Data Preservation Content Specification provides information on what has to be captured to ensure understandability of datasets in the future. PROV-ES aims to address how to capture the provenance for earth science data systems and what the level and type of provenance should be for supported content items.
We will give a brief overview of PROV-ES and dive into getting started with PROV-ES encodings, discovery, and visualization. We will provide an initial PROV-ES service virtual machine to deploy yourself.
We advise setting up this virtual machine ahead of time before the hackathon to avoid any potential issues with clogging the conference wifi network.
Please refer to our collaborative document here for notes and installation instructions.
Comments
updated