Clean reference data LBBG_TEXEL

[sannegovaert]

When we download the reference data from UvaBiTS, the data is automatically mapped to the Movebank data format.
Here is the reference data for LBBG_TEXEL in Movebank format.

Tasks for @jshamoun and @sshinne

1. ses.start_date = deploy-on-timestamp and ses.end_date = deploy-off-timestamp

   • Can you confirm that the deploy-on-timestamp and deploy-off-timestamp is correct for alle deployments?

The deployment thus only starts when a bird is tagged and released. And the deployment ends when the bird has died or the tag has been removed. We do not want to publish measurements when the bird is in captivity (eg rehabilisation center) or the tag in somebody's car or office :)

2. ind.remarks = animal-comments and ses.remarks = deployment-comments
   This needs to be cleaned up.

   • 2.1 Remove alle tag serial numbers - this information is already available
   • 2.2 There are measurements in animal-comments that need to formatted so they are mapped to deploy-on-measurements. They need to be formatted in key:value | key:value pairs.
   • 2.3 Some birds were apperently juvenile when they were tagged, while we set animal-life-stage = adult for the whole study.
   • 2.4 Standardize the comments:
     • text related to the deployment (eg malfunction of the tag, bird found dead) belongs in ses.remarks = deployment-comments
     • deduplicate remarks in ind.remarks and ses.remarks
   • 2.5 Preferentially remove personal names (Roos Kentie)
   • 2.6 Rephrase dead logger in ses.remarks = deployment-comments because the presence of the word "dead" now results in deployment-end-type set to "dead".

Be aware that deployment-end-type is filled in based on the presence of 3 words in session remarks. Other values from Movebank vocabulary cannot be consistently derived.

deployment-end-type set to	Session remarks contains the word
dead	dead
equipment failure	defect
equipment failure	malfunction

3. animal-sex
   The sex of many of several birds is unknown.

   • Please update animal-sex if more information is available.

4. tag-mass

   • Add for several records where it is missing

[sshinne]

1 deploy-on-timestamp is always correct for all deployments. Judy will update records where deploy-off-timestamp is blank.

2.1 Judy will clean this up in the database.

2.2 Measurements in animal-comments should not be mapped to deploy-on-measurements. This information should not be included in the uploaded data.

2.3 Any individuals with “chick” or “juvenile” in animal-comments or deployment-comments should not be included in the uploaded dataset.

2.4/2.5 Similar to other issues: animal-comments and deployments-comments should only be used to populate other fields when that makes sense (e.g., to set a value in deployment-end-type), but otherwise these comments should not be passed to ind.remarks or ses.remarks. We need to leave this as is in our database, and the comments should not be uploaded to Movebank remarks fields.

2.6 We are willing to look into this, but we are wondering if you have any suggestions for language we should use to replace it.

3 No more information is available.

4 Tag mass is unknown, we can’t update the database.