Linked Paleo Data - Revision history

Jeg: updated links

2021-08-11T03:56:28Z

updated links

Jeg: /* Structuring data : the LiPD Way */

2018-07-12T23:52:55Z

‎Structuring data : the LiPD Way

Khider: Add logo

2017-05-04T01:48:10Z

Add logo

Khider: /* Working with LiPD data */ add LiPD utilities to see also

2017-04-18T03:19:56Z

‎Working with LiPD data: add LiPD utilities to see also

Khider: /* LiPD in LinkedEarth */ Replace ontology external link to a wiki link

2017-04-18T03:18:48Z

‎LiPD in LinkedEarth: Replace ontology external link to a wiki link

Khider: /* Working with LiPD data */ Add see also toward GeoChronR and Pyleoclim

2017-04-18T03:17:52Z

‎Working with LiPD data: Add see also toward GeoChronR and Pyleoclim

Khider: /* Getting your data into LiPD */ add a link to creating a LiPD file.

2017-04-18T03:17:00Z

‎Getting your data into LiPD: add a link to creating a LiPD file.

Khider: fix typo

2017-03-27T17:14:30Z

fix typo

Jeg: /* LiPD in LinkedEarth */

2017-03-23T19:13:53Z

‎LiPD in LinkedEarth

Jeg: /* ChronData Table */ fixed link

2017-03-08T03:24:58Z

‎ChronData Table: fixed link

@@ Line 103: / Line 103: @@
 ===List of utilities and software that read and write LiPD===
-*  [[LiPD Utilities]] in:
+*  [https://github.com/nickmckay/LiPD-utilities LiPD Utilities] in:
 **Matlab
 **Python
 **R
-*[[GeoChronR]], an R package for age-modeling and associated ensemble-based workflows (spectral analysis, PCA, correlations, etc.)
+*[https://nickmckay.github.io/GeoChronR/ GeoChronR], an R package for age-modeling and associated ensemble-based workflows (spectral analysis, PCA, correlations, etc.)
 *[https://www.cs.colorado.edu/~lizb/cscience.html CSciBox], see [http://linked.earth/featured-partnership-cscience-linkedearth/ this post by Liz Bradley on how LiPD changed how they do science]
-*[[Pyleoclim]], a Python package to analyze and visualize paleo data.
+*[https://github.com/LinkedEarth/Pyleoclim_util Pyleoclim], a Python package to analyze and visualize paleo data.
 == Getting your data into LiPD ==

@@ Line 18: / Line 18: @@
 == LiPD components ==
-[[File:Lipd_structure.png|400px|thumb|right|structure of a lipd file]]
+[[File:Lipd_structure.png|400px|thumb|right|structure of a lipd file. For an animated presentation see [http://prezi.com/svmit2ys9_d7/?utm_campaign=share&utm_medium=copy&rc=ex0share this prezi]]]
 There are 6 possible components to a LiPD dataset. To be considered valid,  a LiPD file must observe the structure to the right, and contain basic metadata for at least some of these categories.
@@ Line 114: / Line 114: @@
 {{See also|Creating a LiPD file|label 1= creating a LiPD file}}
-Once data are in LiPD, and the LiPD file is [http://lipd.net/validator valid], everything is [https://www.youtube.com/watch?v=StTqXEQ2l-Y awesome]. At present, a limiting step is to format data into LiPD. There are currently two ways to do this:
+Once data are in LiPD, and the LiPD file is [http://lipd.net/validator valid], everything is [https://www.youtube.com/watch?v=StTqXEQ2l-Y awesome].
-# Create pages manually on the wiki (long, tedious and error-prone), then clicking the "Download LiPD" button on the top of the dataset page
-# Use an Excel template, then apply the [https://github.com/nickmckay/LiPD-utilities/blob/master/Python/lipd/pkg_resources/excel/excel_main.py excel2lipd conversion] in Python (great for Python3.5+ users, not useful to anyone else).
-We are working overtime to create a '''LiPDifier''': a web-based artificial intelligence system taking paleoclimatologists by the hand to create a digital version of their datasets. The LiPDifier will be informed by the [http://linked.earth/ontology/ ontology] and know to ask different questions from speleothem folks than to sediment folks, for instance. It will also make recommendations based on the [[Paleoclimate_Data_Standards|community standards]] generated through LinkedEarth (i.e. if the community said that one cannot create a paleo dataset without giving it geographic coordinates, it will not let someone create a LiPD file unless it contains such coordinates and they pass basic checks).
+How do you get paleo data into LipD, you ask? This is now very easy thanks to the [http://lipd.net/playground LiPD playground], which enabled basic quality checks along the way. Soon LiPD creation will leverage the [[LinkedEarth_Ontology]] and NOAA's controlled vocabulary.  Stay tuned for more updates.

← Older revision		Revision as of 01:48, 4 May 2017
Line 1:		Line 1:
	= LiPD: Linked Paleo Data =		= LiPD: Linked Paleo Data =
		+
		+	[[File:LiPD Logo.jpg \|thumb\|400px\|right]]

	== The LiPD vision ==		== The LiPD vision ==

@@ Line 93: / Line 93: @@
 == Working with LiPD data ==
-{{See also|GeoChronR|Pyleoclim}}
+{{See also|GeoChronR|Pyleoclim|LiPD Utilities}}
 LiPD was designed so that it can capture much richer sets of (meta)data than ASCII or Excel files, and to have a fixed backbone around which scientific codes can be built.

@@ Line 11: / Line 11: @@
 ==  LiPD in LinkedEarth ==
-LiPD is a convenient way to store and exchange paleoclimate format, and provides the backbone of the LinkedEarth edifice. LiPD is closely aligned with the [http://linked.earth/projects/ontology/ LinkedEarth ontology]; changes in one are often reflected in the other (with a small lag).
+LiPD is a convenient way to store and exchange paleoclimate format, and provides the backbone of the LinkedEarth edifice. LiPD is closely aligned with the [[LinkedEarth Ontology]]; changes in one are often reflected in the other (with a small lag).
 = Structuring data : the LiPD Way =

← Older revision		Revision as of 03:17, 18 April 2017
Line 107:		Line 107:

	== Getting your data into LiPD ==		== Getting your data into LiPD ==
		+	{{See also\|Creating a LiPD file\|label 1= creating a LiPD file}}

	Once data are in LiPD, and the LiPD file is [http://lipd.net/validator valid], everything is [https://www.youtube.com/watch?v=StTqXEQ2l-Y awesome]. At present, a limiting step is to format data into LiPD. There are currently two ways to do this:		Once data are in LiPD, and the LiPD file is [http://lipd.net/validator valid], everything is [https://www.youtube.com/watch?v=StTqXEQ2l-Y awesome]. At present, a limiting step is to format data into LiPD. There are currently two ways to do this:

@@ Line 66: / Line 66: @@
 === ChronData Table ===
-This mirrors PaleoData but only includes the data from the study that were used to infer the age of the sequence. This includes:
+This mirrors [[Linked_Paleo_Data#PaleoData_Table | PaleoData]] but only includes the data from the study that were used to infer the age of the sequence. This includes:
 ====Measurement Tables====