Issue 14920

Data records collected with consistent sampling methodologies can be identified

14920
Reporter: ahahn
Type: Story
Summary: Data records collected with consistent sampling methodologies can be identified
Priority: Blocker
Status: ToDo
Created: 2014-01-23 12:28:59.715
Updated: 2015-12-14 17:49:00.118
        
Description: Enable identification of data records which have been collected as part of a project/campaign with consistent sampling methodologies, to allow use of this criterion to discover and download data.

This can be achieved by including information in the data set metadata (see other stories under Epic GBIF-13 for another method where the DwC record itself contains a reference to a sampling method, e.g. using a new term such as samplingProtocolIdentifier).

1.	Prepare controlled vocabulary of the names of sampling methodology techniques (could use the samplingProtocolIdentifier URI values described later); user selects an item from this vocabulary and it is included in the metadata as a keyword. Note that while EML has both methods and protocols modules, neither provide a simple, single element for the name of a method or protocol.
2.	As a less precise alternative to above, just include textual description in abstract and/or methods  description sections and retrieve using free text search.

*Tasks*
1.	Get community input on list of sampling protocols.
2.	Provide access to list of methods in IPT so a user preparing metadata can easily select a method (as a keyword).
3.	Review data sets in GBIF index to see if any can be tagged with sampling method name.
4.	Demonstrate search and retrieval based on keyword or free text search.

*Concerns*
1.	It may be difficult to get consensus on a short list of sampling protocols.
2.	Is the name of a sampling protocol sufficient for those intending to merge data? EML distinguishes between “sampling protocol” and “sampling method” recognising that the former is the ideal, text book procedure which, in practice, may not be followed in the field due to various constraints.
]]>