You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest using the broader and more unambiguous: dnaSequenceID - it also indicates the connetion to the field (DNA_sequence) from which the value is derived.
Reasoning: "ASV" is strictly speaking a DNA sequence resulting from only some particular sequencing and bioinformatic processing pipelines, not all. BOLD sequences (e.g.) are for the major part Sanger sequences (not ASVs). Currently we do not identify and separate DNA sequences of different "types" or from different sources (environmental DNA or specimens etc) to handle them differently. Thus, we need a more accommodating term than asvID, I think.
thomasstjerne
changed the title
New multivalue field asvID
New multivalue field dnaSequenceID
Nov 7, 2024
dnaSequenceID
in the ES indexDNA_sequence
, populatednaSequenceID
as follows:DNA_sequence
/[^ACGTURYSWKMBDHVN]/g
dnaSequenceID
We want this to be a multivalue field because some occurrences may have multiple lines in DNA derived data extension.
The text was updated successfully, but these errors were encountered: