nest_excavations can come from TNE or AE. Either have species.
Currently, WAStD joins plain Encounter details to the nest excavations API serializer.
wastdr::download_wastd_turtledata then joins TNE (which brings species and other columns), but does not join AE.
Nest excavations / egg counts coming from tagging (AE + tnexcav) therefore do not have species information.
Simply joining AE and TNE to nest excav would duplicate species and other columns.
We need to combine (bind_rows) tracks and animals before joining to Observations with plain Encounter serializers.
nest_excavations can come from TNE or AE. Either have species.
Currently, WAStD joins plain Encounter details to the nest excavations API serializer.
wastdr::download_wastd_turtledatathen joins TNE (which brings species and other columns), but does not join AE. Nest excavations / egg counts coming from tagging (AE + tnexcav) therefore do not have species information. Simply joining AE and TNE to nest excav would duplicate species and other columns. We need to combine (bind_rows) tracks and animals before joining to Observations with plain Encounter serializers.