{"id":2267,"date":"2014-06-22T16:09:00","date_gmt":"2014-06-22T16:09:00","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2267"},"modified":"2014-06-22T16:15:03","modified_gmt":"2014-06-22T16:15:03","slug":"week-3-update","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/prov-trace\/week-3-update\/","title":{"rendered":"Week 3 Update"},"content":{"rendered":"
On June 9th, Patrick and I met up at RPI to discuss presentation strategies for provenance records in OPeNDAP.\u00a0 When provenance for an OPeNDAP data product is exposed, two things will regularly be present: references to specific OPeNDAP modules<\/strong> and their contributors<\/strong>.\u00a0 Therefore, providing a consumer access to this information could be helpful in facilitating provenance interpretation.<\/p>\n Using information from OPeNDAP\u2019s SVN code repository, a listing of OPeNDAP modules and contributors was compiled along with a partial set of the following metadata:<\/p>\n Module:<\/strong> Contributors:<\/strong> Using this information, a set of mockups will be developed in the following week for a web-based service for presenting provenance records.<\/p>\n","protected":false},"excerpt":{"rendered":" On June 9th, Patrick and I met up at RPI to discuss presentation strategies for provenance records in OPeNDAP.\u00a0 When provenance for an OPeNDAP data product is exposed, two things will regularly be present: references to specific OPeNDAP modules and their contributors.\u00a0 Therefore, providing a consumer access to this information Continue reading Week 3 Update<\/span>
\n– SVN trunk root
\n– SVN tag roots
\n– Description<\/p>\n
\n– Name
\n– SVN username
\n– Website
\n– Development role<\/p>\n