New Pattern: Samples

[pbuttigieg]

Working with the Sampling Nature RCN, and leveraging work done by Open Context on JSON-LD exchange of sample (meta)data (e.g. this record), we should create a pattern for samples using schema.org semantics and test it against some of the examples gathered during the RCN meetings.

First instinct - develop from the Product type and nest domain-level semantics in additionalProperty keys.
We've alraedy done the groundwork for this here, so it's a question of adapting this to some sample examples from OpenContext

xref #309 #125

[pbuttigieg]

The exchange of some sample metadata will be subject to a wide range of license and restriction clauses. Be prepared for CARE alignment and more advanced provenance tracking in this pattern, which can be generalised across others

[pbuttigieg]

@fils should the PR target the thematics in the book directory or is the new publishing flow instantiated? Where should I create the pattern for the PR?

[ekansa]

For archaeological materials from Open Context (https://opencontext.org), we want to make sure that aggregators (search engines, ecommerce players) DO NOT interpret archaeological materials as items involved in commerce. We actively want to work AGAINST archaeological materials circulating in commerce (the antiquities trade is very destructive), so there needs to be some clear signal in the metadata that such materials are not commercially appropriate.

[pbuttigieg]

For archaeological materials from Open Context (https://opencontext.org), we want to make sure that aggregators (search engines, ecommerce players) DO NOT interpret archaeological materials as items involved in commerce. We actively want to work AGAINST archaeological materials circulating in commerce (the antiquities trade is very destructive), so there needs to be some clear signal in the metadata that such materials are not commercially appropriate.

@ekansa many thanks - there are properties where conditions of access and usage parameters can be defined.

What sort of statement or link would you like as the value of such a field?

[smrgeoinfo]

there's a proposed schema.org implementation of the iSamples metadata scheme, its in a branch in our metadata Github repo: https://github.com/isamplesorg/metadata/tree/develop/notes/schemaOrg. Its based on schema:Thing, and uses properties from a variety of entities, so the validator throws some warnings, but no errors.

[smrgeoinfo]

the mapping is also documented here: https://docs.google.com/document/d/1EZDeulvglKVphlo8cHkZAQ4xYr7-yWMF

[pbuttigieg]

@datadavev - tagging you for the iSamples federation, see also #388

[ekansa]

@pbuttigieg is there anything you'd like from me to update with Open Context itself?

[smrgeoinfo]

nudging this along, I reviewed the sdo:product template that @pbuttigieg pointed to in #376 (comment). Here are some note comparing to the current iSamples schema.org material sample record implementation draft with that template:

Product properties irrelevant to material samples

• "aggregateRating":
• "audience": {
• "award": [
• "brand":
• "model": {
• "mpn": "text to state the Manufacturer Part Number (MPN)
• "negativeNotes":
• "nsn": "Text to state the NATO stock number
• "positiveNotes": {
• "purchaseDate":
• "review": {
• "sku": "
• "slogan":
• "url":

Properties in product template that might be useful,

but are not used or defined differently in iSamples ...

• "disambiguatingDescription": ?? not in iSamples scheme, not clear how its supposed to be used in this context

• "productionDate": in iSamples this is startDate, endDate for sampling event

• "releaseDate": This is the subjectOf/sdDatePublished in iSamples draft

• these size related properties were considered but too rarely recorded, and decision was to not include in base metadata scheme; proposal was to use in an additionalProperty element, but iSamples does not currently implement.
  -- "size":
  -- "weight":
  -- "width":

• "image": iSamples related link, with linkRelationship like "image of sample"

• "mainEntityOfPage": iSamples relatedLink

• "subjectOf" iSample relatedLink

• "sameAs": alternate identifiers are listed in the isamples identifier array.

• "additionalProperty": Considered in early model development, but not implemented yet.

properties used in iSamples and in the product template

• "name": --the iSamples label
• "category" -- isamples used DefinedTerm for controlled vocab classifiers
• "additionalType" -- a string (term or uri) that identifies a more granular type for the described resource. Recommendation is use on of the terms from iSample Material Sample Object Type
• "identifier": -- Use schema.org PropertyValue object to represent an identifier; use for identifiers that are not URIs, and for alternate identifiers. Preferred identifier should be in id;
• "description"

Keys in sdo:Thing used by iSamples, not in 'Product' template

• "keywords"
• "relatedLink" iSamples link to related resource with relationship property to indicate nature of connection. Target should be identifier for a resource.
• "ethicsPolicy" iSamples: list of policies, recommendations, best practices (etc.) that have been followed in the acquisition and curation of the sample . If any special protocols were followed, they should be documented here.
• "event" object that documents the sampling event--who, where, when the material sample was obtained. Implements iSamples SamplingEvent object that implements schema.org Event type. sampling location is a property of the SamplingEvent. SamplingEvent includes another iSamples defined property "authorized_by"
• "geo" geopatial location of sampling event site; required default is WGS84 latitude, longitude in decimal degrees. Elevation as a string with number, unit of measure, and datum."
• "subjectOf" iSamples uses property to link the material sample node to a node recording information about the sample metadata registration, publisher, update dates.

property added in iSamples, not in schema.org

• "curation" -- documentation of preservation, preparation, loans, any modification to original sample after accession into repository. Events before assesion to repository should be documented as part of the samplingEvent
• "authorized_by" property of SamplingEvent, a list of permits or other formal permission documents under which the sample was collected. Use to cite legal documents authorizing sample collection. Can't find a suitable schema.org property. Value could be sdo:Permit

one DublinCore term used:

• "dcterms:conformsTo" is used to indicate specifications and profiles that a data conforms to or that the metadata conformsTo, depending on the context.

iSamples scheme uses

sdo:Thing, sdo:DefinedTerm, sdo:DefinedTermSet,sdo:CreativeWork, sdo:Event, sdo:DigitalDocument, sdo:Role, sdo:PropertyValue, sdo:GeoCoordinates, sdo:LinkRole, sdo:EntryPoint

[pbuttigieg]

Pull request created here: iodepo/odis-in#31

[pbuttigieg]

"dcterms:conformsTo" is used to indicate specifications and profiles that a data conforms to or that the metadata conformsTo, depending on the context.

This will be moved to a JSON-LD file (J2) that describes the JSON-LD file about the sample itself (J1).

We can link to J2 from J1 using "subjectOf" in J1.