Planned events / planned samples

[jmckenna]

Based on the below discussion in #158 we'll use this issue here to continue developing patterns for planned events and samples.

@pbuttigieg - I am not sure if this is the right thread to add. In the Island Sampling Day example, we had both planned events and planned samples in GEOME. Is there a place for SampleStatus to indicate planned samples?

@erinmr yes, this is the right PR - see this comment

I think we'd model the planned sample as a planned sampling event, with a "result" that is a material sample (using an ontology class from BCO, perhaps )

If.you have a set of JSON-LD docs we can test against this pattern, let us know!

@pbuttigieg - would you think the json-ld would come from GEOME or iSamples or should we think about creating it separately?

[pbuttigieg]

We perhaps should have another issue for "sample" which would be a schema:Product (until/unless there's something better)

[pbuttigieg]

@erinmr - anticipating the NYC meeting for iSamples:

@pbuttigieg - would you think the json-ld would come from GEOME or iSamples or should we think about creating it separately?

It shoudn't really matter where the JSON-LD would come from, but we should agree on a common usage so we can disambiguate samples themselves (Products) and sampling events (Actions)

[erinmr]

@pbuttigieg @jmckenna - thanks for adding me to this thread. Here are the two csv files that come from the GEOME expedition for Island Sampling Day events and samples: Events_output.csv Samples_output.csv

Expedition Landing page

These would be the fields to start with for JSON-LD.

John has followed Darwin Core for event and material sample. I need to circle back to iSamples on what they are harvesting from GEOME.

[smrgeoinfo]

I generated a schema.org implementation of the iSample schema as a test. Perhaps useful? https://github.com/isamplesorg/metadata/tree/schema.orgTest/notes/schemaOrg