Skip to content
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.

NMDC Sample Metadata Template: currently undefined usage of samp_collect_device #390

Open
Tracked by #587
turbomam opened this issue Jul 26, 2021 · 1 comment
Open
Tracked by #587

Comments

@turbomam
Copy link
Member

turbomam commented Jul 26, 2021

This is one component of issue #375

From mixs.yaml:

name: samp_collec_device
definition_uri: https://w3id.org/mixs/vocab/samp_collec_device
aliases:
- sample collection device
mappings:
- MIXS:0000002
description: The device used to collect an environmental sample. This field accepts
  terms listed under environmental sampling device (http://purl.obolibrary.org/obo/ENVO).
  This field also accepts terms listed under specimen collection device (http://purl.obolibrary.org/obo/GENEPIO_0002094).
comments:
- 'Expected value: device name'
- 'Position: 31.0'
examples:
- value: swab, biopsy, niskin bottle, push core, drag swab [GENEPIO:0002713]
from_schema: http://w3id.org/mixs/terms
exact_mappings:
- 'MIGS:'
is_a: nucleic acid sequence source field
range: string
slot_uri: MIXS:0000002
owner: core
domain_of:
- MIGS eukaryote
- MIGS bacteria
- MIGS plant
- MIGS virus
- MIGS org
- ME
- MIMARKS specimen
- MIMARKS survey
- MISAG
- MIMAG
- MIUVIG
- core
pattern: '{termLabel} {[termID]}|{text}'

I think the MenuTerms tab in the NMDC Sample Metadata Template is implying the following as descendants of the samp_collect_device slot:

  • shovel
  • slide_hammer_core
  • deep_corer
  • russian_corer
  • sipper
  • other-samp_collect_device

All of which would take a string range

Also, double check samp_collect_device vs samp_collec_device

@mslarae13
Copy link

samp_collec_device is used in V6

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants