Closed tucotuco closed 2 months ago
Our ALA colleagues ask 'What happens if the samplingEffortValue and samplingEffortUnit require multiple values? Eg. “2 hours over 100m2”?'
Comment from YMG: Good point. I have a feeling that this is again related to eMoF https://github.com/gbif/rs.gbif.org/issues/103#issuecomment-1532983566 and https://github.com/gbif/rs.gbif.org/pull/102. Do dwc:sampleSizeValue and dwc:sampleSizeUnit have a similar challenge? If we are to provide recommendation for this, perhaps we should align the practice across other general terms like dwc:sampleSizeValue and dwc:sampleSizeUnit?
Comment from KI: As with other terms where this potential exists, we should recommend using pipe separators, |, where multiple values exist. It would also be prudent to include in the comments/examples that it is recommended that data providers populate dwc:samplingEffort (http://rs.tdwg.org/dwc/terms/samplingEffort) with verbatim sampling effort information.
Dear All,
Thanks Katie for all your efforts to move the ALA questions forward. This is making a big difference.
Regarding this issue separators would work but I would prefer dividing effort this option into three basic components: Space, time and sampling units each with a number and units
Some examples to spur the conversation
for pitfall traps 200 m, 5 days, 10 traps for bird survey 1 km, 30 minutes, 2 people for camera traps 1 hectare, 2 weeks, 14 cameras for eDNA 500 m, , 4 samples for plant survey 200 m transect | 10 m2 plots, 10 hours, 1 person for a drone 6 acres, 1 hour, 1 drone
Rob
On Mon, Oct 23, 2023 at 6:21 AM Kate Ingenloff @.***> wrote:
Our ALA colleagues ask 'What happens if the samplingEffortValue and samplingEffortUnit require multiple values? Eg. “2 hours over 100m2”?'
As with other terms where this potential exists, we should recommend using pipe separators, |, where multiple values exist. It would also be prudent to include in the comments/examples that it is recommended that data providers populate dwc:samplingEffort ( http://rs.tdwg.org/dwc/terms/samplingEffort) with verbatim sampling effort information.
— Reply to this email directly, view it on GitHub https://github.com/tdwg/hc/issues/81#issuecomment-1774882114, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGCKFMOLCXY7XB7PJMIGGZ3YAZAJTAVCNFSM6AAAAAA4KZMR7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZUHA4DEMJRGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Robert D Stevenson Associate Professor Department of Biology UMass Boston
New term
Submitter: Humboldt Extension Task Group
Efficacy Justification (why is this term necessary?): Part of a package of terms in support of biological inventory data.
Demand Justification (name at least two organizations that independently need this term): The Humboldt Extension Task Group proposing this term consists of numerous organizations.
Stability Justification (what concerns are there that this might affect existing implementations?): None
Implications for dwciri: namespace (does this change affect a dwciri term version)?: Needs ecoiri: equivalent. Proposed attributes of the new term:
Term name (in lowerCamelCase for properties, UpperCamelCase for classes): samplingEffortUnit
Term label (English, not normative): Sampling Effort Unit
Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event
Definition of the term (normative): The units associated with the eco:samplingEffortValue.
Usage comments (recommendations regarding content, etc., not normative): Recommended best practice is to use a controlled vocabulary.
Examples (not normative):
trap hours
;person hours
;trap days
Refines (identifier of the broader term this term refines; normative): None
Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): None
ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): not in ABCD