Category:Working Group

From Linked Earth Wiki
Revision as of 04:37, 23 February 2017 by Khider (Talk | contribs) (Move polls for new datasets to appropriate page)

Jump to: navigation, search
( Pages with a poll )


What is a Working Group?

In the Linked Earth context, a working group (WG) is a self-organized coalition of knowledgeable experts who elaborate and discuss the components of a data standard for their field of expertise. WGs can be created by any member of the LinkedEarth community to discuss topics of interest. The rationale for such WGs is that the paleo community is incredibly diverse, and what matters to a coral geochemist may be very different than what matters to a dendrochronologist. That being said, both might care about similar things. The WGs should just span the interests of the community and how they intersect.

Current WGs

They are basically of three types:

How to join a WG?

On your profile page, you have the option of joining working groups simply by inputting their names in the "Working Groups" tab. The only WGs to pop up are those currently in existence. If the one you want doesn't exist yet, please create it.

Note that joining a working group adds all pages belonging to that working group category to be added to the user's watchlist.

Joining a working group doesn't commit you to participate in every discussion on the subject. Rather, it lends support to the need for the creation of a standard and shows trust in the community.

How to create WG?

To create a WG, create a new page and tag it as a sub category of the WG category. The list of working groups will be shown automatically at the bottom of this page (as subcategories of the Working_Groups category). Each WG page needs the following elements:

  • A list of the various group Members
  • Polls on specific questions.
  • A log of decisions made (e.g., table with dates and content of discussions)

To get started, just log on, look at any WG page, and just copy&paste the relevant elements. When you want to categorize any wiki page as belonging to that working group, add the working group category (at the bottom) to the wiki page. For instance, a page on layer-counting might be relevant to the tree, coral, and ice core working groups.

Working Group Charter

Membership

Membership of each WG is open to all wiki users, with some monitoring from WG coordinators. The coordinators are community members of recognized expertise who have volunteered to serve in this position. Their role is to organize discussions and check progress of other WGs to ensure maximum uniformity.

Aims

The primary goal of WGs is to standardize how paleoclimate data are described and shared. The process is defined here and the specific charge emanating from the first workshop on paleoclimate data standards is outlined on this page. Each WG should take up these questions as relevant to their interests; to ensure that common solutions are designed, WG coordinators will regularly check-in with each other and with LinkedEarth leadership.

Decision-process

Each WG operates by consensus. Wiki polls track the answers to specific questions.

Timeline

The preliminary timeline of WG activities is defined here but will evolve as work begins.


Legacy Datasets

Contributor

For legacy datasets, should contributor be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:32, 5 October 2016.
poll-id FDA561A3D43205B54516AF8CC309C0D1

Location

Latitude
For legacy datasets, should latitude be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 5 votes since the poll was created on 23:32, 5 October 2016.
poll-id A917CFFFF14798FF6B9B8BD4AC283DF9

Longitude
For legacy datasets, should longitude be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 5 votes since the poll was created on 23:32, 5 October 2016.
poll-id 0F75DA172113098D02C1FC72029A5623

Altitude
For legacy datasets, should altitude be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 5 votes since the poll was created on 23:32, 5 October 2016.
poll-id EF0A019E92F27CDF2A583E0E2B8C2287

Publication

Authors
For legacy datasets, should authors be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id 8874AA9A21FDDC5E4A99A49252FE4648

Publication Year
For legacy datasets, should publication year be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id 11CE9B21F6A77491A8F6D178D3B2C087

Title
For legacy datasets, should title be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id A1F454820CABEA47E0D2E1096D23532E

doi
For legacy datasets, should doi be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id 34439BF697F7A1B7D7D3D43AF6630F86

Funding

Principal Investigator
For legacy datasets, should principal investigator be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id 13CB12C7A0965B73D8BE12188A56AA10

Funding Agency
For legacy datasets, should funding agency be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id 2C6BDBF01E2B0FDDB1E8508CACB95860

Funding Country
For legacy datasets, should funding country be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id EAB24970CE7C48B367FBAE71866306B5

Grant Number
For legacy datasets, should grant number be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 23:33, 5 October 2016.
poll-id F44C024724C78ED2DCBC0B9ABD7ECE5C

PaleoData

PaleoData refers to the "y-axis" of the dataset and contains the information about paleoenvironment. Before answering the poll below, head to the Discussion page for an example of a dataset not containing y-axis information.

For legacy datasets, should the presence of PaleoData information be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:34, 6 October 2016.
poll-id 73A7170BBB4982C1F9480440F2579468

Depth vs age

The information obtained from the archive is taken at a certain "depth".

For legacy datasets, should PaleoData depth be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:34, 6 October 2016.
poll-id E6CC0641CF9DBDB4D7305F9ECE25A6BC

For legacy datasets, should the PaleoData contain information about how this "depth" was transformed to age, and if possible give an estimate of age at each horizon in the archive.
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:34, 6 October 2016.
poll-id 7D6E363D664E434E164BABA96F461C66

Variables
For legacy datasets, should the PaleoData include the raw measurements (for instance d18O)
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:34, 6 October 2016.
poll-id F0CCAED9E3DCCEEC5031B7E4C8B21CEE

For legacy datasets, should PaleoData units (e.g., cm, per mil, deg C) be considered
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:35, 6 October 2016.
poll-id 43C48186CF5FF9ABCE75028F6907B739

Interpretation
For legacy datasets, should information about the interpretation of the PaleoData be
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:35, 6 October 2016.
poll-id F8A0A53E2DF1BE4C58742963D84C3187

calibration
For legacy datasets, If the interpretation is given, should information about the PaleoData calibration be
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:35, 6 October 2016.
poll-id EE6CF118A69952A5A2B4E76A02234CE5

uncertainty
For legacy datasets, should information about uncertainty in the PaleoData be
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:35, 6 October 2016.
poll-id 98CF77924C4B7DB9CFD38E7115C4D99B

See the uncertainty working group for details on the data and metadata standards when reporting uncertainties.

ChronData

ChronData refers to the "x-axis" of the dataset and contains the information about the age model. Before answering the polls below, head to the Discussion page for an example of a dataset not containing x-axis information.

For legacy datasets, should the presence of ChronData information be (assuming there is a chronology, maybe in addition to depth, in the PaleoData):
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 3 votes since the poll was created on 20:37, 6 October 2016.
poll-id 7EE181C479EFAEF5AA284F9EFD3BE5D0

For legacy datasets, should the presence of ChronData information be (assuming no chronology in the PaleoData):
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 3 votes since the poll was created on 20:38, 6 October 2016.
poll-id 6EDBC878D27D0D813CD013388F39ABEF

Variables
For legacy datasets, should the ChronData include the raw measurements (for instance radiocarbon)
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 3 votes since the poll was created on 20:47, 6 October 2016.
poll-id 9DAA9D9358304A951B4AB93817F2665D

For legacy datasets, should ChronData units (e.g., cm, per mil, deg C) be considered
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:47, 6 October 2016.
poll-id D3B7B93857E8E5E734F03E526542E8FF

Interpretation
For legacy datasets, should the interpreted calendar age be
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 4 votes since the poll was created on 20:47, 6 October 2016.
poll-id 76F19B1B62028C8550248BD59727405C

uncertainty
For legacy datasets, should information about uncertainty in the ChronData be
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 2 votes since the poll was created on 20:48, 6 October 2016.
poll-id 2BBB9D9DF96BB8F0F46AEFC129FDCA62

See the uncertainty working group for details on the data and metadata standards when reporting uncertainties.

Pages in category "Working Group"

The following 2 pages are in this category, out of 2 total.