Difference between revisions of "Category talk:Speleothem Working Group"

Latest revision as of 17:04, 25 April 2017

Structure of Database and compatibility with SISAL, NOAA etc -- NickScroxton (talk) 09:25, 13 April 2017 (PDT)

In order to not reinvent the wheel its first good to understand the basics. Namely, the LiPD structure under which we will work

LiPD Format:

• Root Metadata: Dataset Name, Investigators, Link to online dataset, LiPD version
• Geographic Metadata: Coordinates, Sitename, Descriptive location (e.g. Country, State, Province, Ocean)
• Publication Metadata: Authors, Title, Journal, DOI, Year, URL
• Funding Metadata: Funding agency, Funding grant
• PaleoData Table: Measurement Tables (Column names, units and descriptions), Interpretation metadata, Calibration metadata, Models (Methodology used to produce the model results, Summary table of model output, Ensemble tables of data produced by the model, Distribution tables of data produced by the model)
• ChronData Table: Measurement Tables (Column names, units and descriptions), Models (Methodology used to produce the model results, Summary table of model output, Ensemble tables of data produced by the model, Distribution tables of data produced by the model)

As a speleothem working group, the largest difference between us and other groups will be Cave Metadata and Speleothem Metadata. Most of the rest will probably be fine with the LiPD standard (though this is a discussion so happy to hear thoughts).

The relevant metadata for the other major data depositories are:

NOAA Format:

• Publication Metadata: Authors, Title, Journal, Year, Volume, Edition, Issue, Pages, Report Number, DOI, Online Resource, Abstract, Alternative citations (for books, theses etc that don't fit above)
• Geographic Metadata: Site name, Location, Country, Northernmost latitude, Southernmost latitude, Easternmost longitude, Westernmost longitude, Elevation
• Data Collection Metadata: Name, Oldest Year, Youngest Year, Time Unit (yr BP etc), Core-length
• Species Metadata: (not relevant here)
• Funding Metadata: Funding Agency, Grant #
• Paleodata Table: relatively freeform with the following metadata: name, what, material (speleothem d18O, speleothem d13C etc), error, units, seasonality, data_type (speleothem), detail (raw, corrected), method, data format (numeric or type), Additional info
• ChronData Table: relatively freeform no additional metadata

SISAL Format:

• Publication Metadata: Citation, DOI
• Geographic Metadata: Cave Name, Latitude, Longitude, Elevation, Geology, Rock Age, Monitoring
• Stalagmite Metadata: Name, Overburden Thickness, Distance from Entrance, Speleothem Type, Drip Type, series of Yes/No for common proxies, Data DOI
• Paleodata Table: Stal Name, Distance from Top, Mineralogy, Composite (Yes/No), Equilibrium, Aragonite Correction, Age, Age Error, Age Model Type, Time Unit (yr BP etc), Annual Laminae Check, 14C deposition check, Sample Thickness, d13C measurement, d18O measurement, d13C precision, d18) precision, Isotope Standards (PDB, VPDB)
• DatingTable: Stal Name, Method, Depth, Thickness, Lab ID, Minimum Sample Weight, Maximum Sample Weight, UnCorr Age, UnCorr Age Error +, UnCorr Age Error -, Date used in age model, 238U, 238UErr, 232Th, 232Therr, 230Th, 230Therr, 230/232, 230/232err, 230/238act, 230/238acterr, Decay constants used, CorrAge, CorrAgeErr, Time Unit (yr BP etc), Year of Chemistry

The SISAL format is understandably a lot more prescriptive than the others as it is focused on speleothems.

My 2c: The LiPD format requires the LiPD Root Metadata. I also like the more detailed, Publication Metadata and Funding Data from LiPD. I would include the SISAL geographic metadata as our starting point, as a "Cave metadata" section. I think the biggest need in our field is for a "stalagmite metadata" section using SISAL as a start. I'd like to hear opinions as to whether we want freeform or prescriptive in the tables. My metadata opinion:

• Root Metadata: Dataset Name, Investigators, Link to online dataset, LiPD version
• Publication Metadata: Authors, Title, Journal, DOI, Year, URL
• Funding Metadata: Funding agency, Funding grant
• Cave Metadata: Cave Name, Latitude, Longitude, Elevation, Geology, Rock Age, Monitoring (Y/N)
• Stalagmite Metadata: Name, Overburden Thickness, Distance from Entrance, Speleothem Type, Drip Type, Data DOI

Re: Structure of Database and compatibility with SISAL, NOAA etc -- Deborah Khider (talk) 13:38, 20 April 2017 (PDT)

Thanks for starting the discussion, I added a few polls for community input in one of the sections.

We also updated the LinkedEarth Ontology and by extension LiPD to add information about the Physical Sample. Perhaps some of the proposed properties specific to speleothems could be moved under this new category? I was thinking specifically about entity name, distance from cave entrance (in m), thickness of overlying bedrock above the speleothem (in m), speleothem type (candlestick stalagmite, stalagmite boss, flowstone), and drip type (seepage, seasonal, mixture, unknown).

Reference (for each speleothem) Deborah Khider (talk) 14:46, 24 April 2017 (PDT)

Is this section supposed to contain the publication information of the study in which the speleothem record(s) appear(s) or is supposed to reference the physical sample itself, for instance through a property like hasIGSN.

Re: Reference (for each speleothem) Deborah Khider (talk) 14:46, 24 April 2017 (PDT) -- NickScroxton (talk) 09:02, 25 April 2017 (PDT)

I believe this would be the reference for the publication in which the speleothem record appears. The property for referencing the physical sample itself would be "entity name".

Re: Re: Reference (for each speleothem) Deborah Khider (talk) 14:46, 24 April 2017 (PDT) -- Deborah Khider (talk) 10:04, 25 April 2017 (PDT)

In the current version of the ontology we have a category for the physical sample in which users can enter the name of the archive (entity name), a specific lab ID if any, where in the world the sample currently is and an IGSN number if any. Let me know if there are other properties that could be useful to the speleothem community.