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