{"id":2505,"date":"2014-08-18T16:24:24","date_gmt":"2014-08-18T16:24:24","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2505"},"modified":"2014-08-18T16:24:24","modified_gmt":"2014-08-18T16:24:24","slug":"week-9-update-wrapping-up","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/prov-trace\/week-9-update-wrapping-up\/","title":{"rendered":"Week 9 Update: Wrapping up…"},"content":{"rendered":"
Over the course of this summer’s DataONE OPeNDAP effort, a key goal of ours has been the development of two things: new practices for managing provenance tracing within the OPeNDAP framework, as well as reference code for future developers to use as a reference.\u00a0 As of now, our reference code consists of the following contributions: (i) a set of “splash” pages for displaying content attached to provenance records (i.e., contributors to modules, as well as module versions) and (ii) extensions to OPeNDAP’s code base for tracking versions of modules utilized by specific provenance traces.<\/p>\n
Over the next 1-2 weeks, our code extensions will gradually be pushed to the project’s OPeNDAP repository for public access: https:\/\/github.com\/tetherless-world\/opendap.\u00a0 Additionally, a collection of splash pages for presenting dynamic content from our provenance repository will be made publicly accessible on http:\/\/opendap.tw.rpi.edu.<\/p>\n","protected":false},"excerpt":{"rendered":"
Over the course of this summer’s DataONE OPeNDAP effort, a key goal of ours has been the development of two things: new practices for managing provenance tracing within the OPeNDAP framework, as well as reference code for future developers to use as a reference.\u00a0 As of now, our reference code Continue reading Week 9 Update: Wrapping up…<\/span>