Missing data in alltags when tag detection occurs outside deployment dates

Analysis and Data
1

When I call up alltags for my dataset, I’ve noticed that there are quite a lot of rows that don’t have data on speciesID, tagDeployStart, tagDeployEnd, and other columns, despite having tag data. This is not due to a lack of deployment metadata entered on the website, as that has been entered for some time, and there are separate rows for the same tag that DO have this information.

It was a little tricky to analyze (precisely because alltags is missing this information), but it appears to happen when the tag detection occurs outside of the tag deployment start and end dates. I had some detections that might be plausible (and I knew about them because they showed up on the public website), but the data kept getting filtered out in my code because the alltags view is missing these data for these rows.

For my needs, I have found a way to stich the required data back in as necessary. But I was just wondering, Is this expected behavior? I’m not sure why the view would work this way

2

Hi Eddy, If I understand you correctly, the deployment metadata is correct on the website, but when viewed in R, the same tag detections do not have any deployment metadata associated with them? Is that’s correct? Are you able to provide some examples and/or screenshots?

3

image
image1342×514 20.7 KB

Thanks for following up; I hope I can explain myself here.

This screen shot shows a filter of the AllTags table my the SQL file for my project (928) looking just at motusTag 76727 (ID 62565) in Feb 2026. As you can see, there is no data for tagDeployID, tagDeployStart, .End, tagDepLat, tagDet Lon, speciesID, etc. However, the data should (in my mind) be there, because the motusTagID is there and should be connected to these other columns. If I look at other dates (prior to the tagDeployEnd date for this tag), I indeed find the expected data in these columns for those detections.

This came up because we saw on the website a detection for this bird in Rio Grande EPEIM (Tierra del Fuego) on the website map, so we went to investigate. (Spoiler, it appears to be a ghost detection). But it was hard to even investigate because these detections kept getting inadvertantly filtered out because I filtered on species, and these detections do not have data for species.

I guess this just seems like unexpected behavior to me, but maybe this is normal.