Anticipated tag deployments

Tagging
1

Hi Motus community,

We’re deploying tags next week at a remote site with no cell/wiFi service. I’ve batch deployed all our tags with an anticipated deployment date ahead of when we’ll be tagging so they’ll be ready to be detected. They now appear on our tag management page with the appropriate deployment date listed in red with “unconfirmed” in the field. Is this correct/how it should look ahead of confirming the actual deployments? It seems like everything is right, but it will be a few days until we’re back to service and able to complete the deployment information so I want to ensure that our stations will be able to detect the tags once deployed.

Thanks for any insights you can provide!

Laney

2

Hi Laney, that’s the correct approach. After you actually deploy the tags and update those deployments, the red “unconfirmed” will be resolved.

This way they will at least be present in the database when the first stations detect them.

Changes to metadata after the fact (start time, species, band, etc) should be show up very soon after you update the deployment records.

3

Great, thank you, Josh!

4

The system doesn’t like future deployments. Go back and set the deployment date for today and then you will be fine. If you want, you can always change the date later to be the actual deployment date

David Mathiason Braddock Bay Raptor Research

5

It’s okay to use future deployment dates for tags, but it will nag you to update the metadata once that date has passed.

There’s more info in our docs here:

6

Thanks! Yes, everything went smoothly with updating the metadata after the tags were deployed. I just wasn’t sure from the existing guidance if the “unconfirmed” status would keep Motus from recognizing legitimate pings before I got in there to update everything, but it seems to all have worked as expected. Thanks to everyone for the help.