In the Linked Earth context, a working group (WG) is a self-organized coalition of knowledgeable experts, whose activities are governed herewith. This page is dedicated to the discussion of data and metadata standards for proxies based on glacier ice (see this page for a definition of the glacier ice archive), and aims to formulate a set of recommendations for such a standard.
We recommend that discussions focus on the following considerations, and explore potential commonalities.
For each observation type, we recommend:
structuring discussions around what scientific questions one would want to ask of the data
listing essential, recommended, and desired information for:
the measurements themselves
any inference made from the measurements (e.g. calibration to temperature)
the underlying uncertainties, and what those numbers correspond to (e.g. 1-sigma or 2-sigma?)
providing an ideal data table, so the community knows what to report and how to report it.
providing separate recommendations for new and legacy datasets, and for how to label measured and inferred variable (e.g. δD is measured, temperature is inferred)
thinking about how the rest of the paleoscience community, or other (non)scientists may make use of the data you describe.
Ice core projects are inherently collaborative in nature, and have thus developed mechanisms for data exchange, including some form of standards. We do not ask this WG to re-invent the wheel; if these standards are defined somewhere, please copy/paste freely here.
List of metadata
Definition of essential, recommended, and desired in regards to paleoclimate data standards
Any snowpit information from the same location (if available)
D
Core densities
D
Depths of brittle ice (if applicable)
D
Depth of firn/ice transition (if applicable)
D
Presence of elongated bubbles (if applicable)
D
Note: Do not edit the polls (even for typos) once voting has started as it will reset the vote counts to zero. If a change needs to be made, make an annotation above the old poll (i.e., above the poll tags) and place the new poll below the first one.
Results of the poll placed on Twitter between May 17th and 24th 2017
For datasets based on ice core archives, should the age scale and dating points be:
You are not entitled to vote. You are not entitled to view results of this poll.
There was one vote since the poll was created on 19:26, 25 April 2017.
poll-id 401E88A0CDD0B56CDA97B238567E1A8D
Results of the poll placed on Twitter from June 9th to 16th 2017
For datasets based on ice core archives, should the possible melt in transport be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:26, 25 April 2017.
poll-id DA6CC2E70B20F0D290064DCA536D99CD
Results of the poll placed on Twitter from June 9th to 16th 2017
For datasets based on ice core archives, should the depth of any melt layers be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:26, 25 April 2017.
poll-id 8512848F386FCD7C178715796651AFB1
Results of Twitter poll run from June 19th to the 26th 2017
For datasets based on ice core archives, should the depth of any ash layers be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 16:06, 25 May 2017.
poll-id 651B0D366A01CF5718B09017A7481BEB
Results of Twitter poll run from June 19th to the 26th 2017
For datasets based on ice core archives, should the list of all proxy observations determined in the core be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:27, 25 April 2017.
poll-id 13F79FB9EB1FD10220490D71C5D97785
Results of Twitter poll run from June 19th to the 26th 2017
For datasets based on ice core archives, should the geographical coordinates be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:27, 25 April 2017.
poll-id FCDF462412B677A0FDB8091CF9B71DB3
Results of the poll placed on Twitter between June 22nd and 29th 2017
For datasets based on ice core archives, should the continous vs discrete sampling label/flag be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:28, 25 April 2017.
poll-id 0800AB20F54E15A8CB101A5079629899
Results of the poll placed on Twitter between June 22nd and 29th 2017
For datasets based on ice core archives, should the coring techniques be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:29, 25 April 2017.
poll-id D3F57D28CD33DD0D6D367D884274FA66
Results of the poll placed on Twitter between July 6th and 13th 2017
For datasets based on ice core archives, should the interpretation of the proxies be:
You are not entitled to vote. You are not entitled to view results of this poll.
There was one vote since the poll was created on 19:30, 25 April 2017.
poll-id 73C4D09DD53F98F5CA743A15749E0717
Results of the poll placed on Twitter between July 6th and 13th 2017
For datasets based on ice core archives, should the core cutting techniques be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:30, 25 April 2017.
poll-id F9990A0A41288CB6CF23EC24E4B3F481
Results of the poll placed on Twitter between July 6th and 13th 2017
For datasets based on ice core archives, should the core storage conditions be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:31, 25 April 2017.
poll-id 4B15ED4530FBDF0268EF9F330628136F
Results of the poll placed on Twitter between July 10th to 17th 2017
For datasets based on ice core archives, should an annotation about the fact that the bedrock has been reached be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:31, 25 April 2017.
poll-id 7675232BDD1B77C770075EEA6823FD37
For datasets based on ice core archives, should the borehole temperatures be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:31, 25 April 2017.
poll-id 1701D3357A1A385CA5720CFAEA802017
For datasets based on ice core archives, should the depth and composition of any organic material be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:32, 25 April 2017.
poll-id DC818AA54667855BC7212C6136A89090
For datasets based on ice core archives, should thesnowpit information from the same location be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:32, 25 April 2017.
poll-id B0C76CABB1AB9748980A2DADF789ECEB
For datasets based on ice core archives, should the core densities be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:32, 25 April 2017.
poll-id BE095E03E9DE1E0E2449A7787383EEE1
For datasets based on ice core archives, should the depths of brittle ice be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:33, 25 April 2017.
poll-id 81E78440C12D92682E9AD15D9E72A323
For datasets based on ice core archives, should the depth of firn/ice transition be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:33, 25 April 2017.
poll-id 09178CBD2472E0C37BBC18B26811654A
For datasets based on ice core archives, should the presence of elongated bubbles be:
You are not entitled to vote. You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 19:33, 25 April 2017.
Is there a unified way to report on timescale construction? Should there be? What does a user need to know about the timescale was constructed to make the best use of the data?