Category:Working Group

From Linked Earth Wiki
Revision as of 20:10, 17 February 2017 by Khider (Talk | contribs) (Add a getting started with standards section)

Jump to: navigation, search
( Pages with a poll, Marine Sediment Working Group )


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 specific sub-field.

Working groups can be created by any member of the LinkedEarth community to discuss topics of interest.

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)

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 showing confidence in the community.

Current WGs


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).


When you want to categorize any wiki page as belonging to that working group, add the working group category to the wiki page.

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 Paleoclimate Data Standards workshop is outlined on this page. Each WG should take up these questions as relevant to their archive of choice; 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.

Getting Started

Getting started with creating a standard for the entire community can be seen as a daunting task. The most obvious questions are "what does a standard actually look like?", "Where do I start?".

What does a standard actually look like?

To answer the first question, a standard is a document that can live on the web or in the case of the standard being developed here, can take the form of a peer-reviewed article. Anyone contributing to the discussion on developing standards for paleoclimatology (either during our workshop on paleoclimate data standards, on the wiki, or teleconference) will be included in the list of authorships.

Where do I start?

The ultimate goal of LinkedEarth is to provide scientists with tools to make better science, including allowing scientists to upload the metadata they need to make their science reproducible, allows complex queries on the system to easily retrieve datasets, and provide packages in R and Python using the standards developed by the community.

Uploading the needed metadata

The strength and appeal of the field of paleoclimatology reside in its diversity. This community relies on the work of geochemists, geologists, computer modelers, statisticians ... to understand past climates. This diversity is also reflected in the datasets generated within the community. Therefore, a one-size-fit-all template for all paleoclimate datasets isn't useful. The LinkedEarth wiki allows to store the metadata each community needs to represent their data. For instance, the cleaning methodology may be important to the foraminiferal Mg/Ca community but completely irrelevant to the tree-ring community. Therefore, one possible way to create a standard is to ask oneself: "What pieces of metadata would I require to reproduce this particular dataset and therefore which one should I provide for my own datasets?"

Some of these metadata will be standard across all archives (i.e., geographic coordinates, publication information). Some will be archive (and even observation)-specific. See for the beginning of a discussion on foraminiferal Mg/Ca.

Querying the datasets

Another way to think about the essential/recommended/optional metadata is to think about the kind of queries one would want to enable for their research. For instance, Testing the Millennial-Scale Solar-Climate Connection in the Indo-Pacific Warm Pool required the following query and associated metadata:


Prior discussions on Standards Developments in Paleoclimatology

We welcome any summaries of prior discussions on data standards you may have had at meetings, workshops. To do so, either link to a document that you have uploaded on the wiki or create a new page and list it below. Sign and data using the following notation: 
~~~~

- PMIP3 Workshop in Corvallis (December 2013) Deborah Khider (talk) 17:00, 30 September 2016 (PDT)

Cross-Archive Metadata

This section is dedicated to the discussion of metadata that would apply for all the paleoclimate archives. For discussion on a specific archive, see the archive working group.

How this section is organized

The section is structured around polls to gather community votes on whether a particular metadata property should be considered essential, required, or desired metadata (for a definition of these terms, see this page. The polling is divided around two "types" of datasets: New Datasets and Legacy Datasets.

The subsections are organized around the categories available on the wiki.

Click on the links to see the current definition of the term. If you disagree on the definition, please use the Discussion page on the term.

If you think a metadata property is missing, add a poll directly in the appropriate section (don't forget to add the poll for both new and legacy datasets!)

If the page freezes and you're unable to vote, refresh the page!

Just a few questions to get you started. These concern both legacy and new datasets:


In answering this question, remember that all the datasets on the wiki are public. The LinkedEarth team is considering adding a feature where a dataset could be uploaded and kept private until publication for use with codes and softwares but this feature is not yet available.

Should the LinkedEarth wiki contain datasets:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 12 votes since the poll was created on 19:18, 6 October 2016.
poll-id 08538E02A7A5FB47FF6F9EDF0F120D99

What type of datasets should be considered "legacy"
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 6 votes since the poll was created on 21:26, 7 November 2016.
poll-id 69B1FF54AECE1662C63EDBA771C4A2FE

This poll was also put on Twitter on November 7 2016.

Comments:

  • Simon Goring: "I would think that legacy data would be any data contributed that doesn't meet up with "new" standards." Twitter link
  • Kaustubh Thirumalai: "In the current stage of LinkedEarth - pre-digitization IMO. e.g. "Legacy Seismic" = data on tapes" Twitter link

New Datasets

Contributor

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

Location

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

Longitude
For new datasets, should longitude be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 8 votes since the poll was created on 23:30, 5 October 2016.
poll-id 25DC86785487AB0C0AAD46303264E94C

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

Publication

Authors
For new datasets, should authors be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 7 votes since the poll was created on 23:30, 5 October 2016.
poll-id 1EE66E9C49D3988DB92F6E6424BFA124

Publication Year
For new datasets, should publication year be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 7 votes since the poll was created on 23:30, 5 October 2016.
poll-id 607C45D8DFAE1DD7C58AF0221B5B9670

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

doi
For new datasets, should doi be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 7 votes since the poll was created on 23:31, 5 October 2016.
poll-id 95C86A93787F7006B1AF107860CEB157

Funding

Principal Investigator
For new datasets, should principal investigator be:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 7 votes since the poll was created on 23:31, 5 October 2016.
poll-id 7932DB8E6E50AF24756744AF222C4E39

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

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

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

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 new records, 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 5 votes since the poll was created on 19:02, 6 October 2016.
poll-id 782F49FF9A11ACB2A0F500780D2A0ACC

Depth vs age

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

For new datasets, should PaleoData depth 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 20:30, 6 October 2016.
poll-id 7BDBEB57F6140BCEF04271EF58F146C1

For new 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 5 votes since the poll was created on 19:41, 6 October 2016.
poll-id 35AD5310CEE089603740F8B57A784608

Variables
For new 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 6 votes since the poll was created on 19:41, 6 October 2016.
poll-id BDE51209E3D0C055A40718D5DF095C05

For new 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 6 votes since the poll was created on 20:29, 6 October 2016.
poll-id 942851E9C3C792651485D0899796A89F

Interpretation
For new 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 5 votes since the poll was created on 20:29, 6 October 2016.
poll-id 41530C8BEC218A9110186706746A763F

calibration
For new 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 5 votes since the poll was created on 20:29, 6 October 2016.
poll-id 3630FC9EA7F3350069E66C484594774B

uncertainty
For new 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 5 votes since the poll was created on 20:29, 6 October 2016.
poll-id 585C76571B3602214EA780057B9CB6B1

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 new 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 6 votes since the poll was created on 20:49, 6 October 2016.
poll-id 2D41F92772AC4741B52137EFCE0AB9BB

For new 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 6 votes since the poll was created on 20:49, 6 October 2016.
poll-id B7033353907D550AF924EF11DF2BA57A

Variables
For new 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 6 votes since the poll was created on 20:49, 6 October 2016.
poll-id 609C48EDC05EB970F93000BDE7FB4909

For new 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 6 votes since the poll was created on 20:49, 6 October 2016.
poll-id A9E0FE4D8B2624F038EAAF196412AD30

Interpretation
For new 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 6 votes since the poll was created on 20:49, 6 October 2016.
poll-id 819AC0DF728985865AD6C70C5F1E7BC2

uncertainty
For new 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 6 votes since the poll was created on 20:50, 6 October 2016.
poll-id A8B56AA5FEF4306BE5F8772B6081DFF0

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

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.

C

O


Retrieved from "https://wiki.linked.earth/wiki/index.php?title=Category:Working_Group&oldid=14655"