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