###New It is now possible to tag an animal with tags from more than one context. This eliminates the necessity to add the same animal more then once. To clearly mark the animals tagged in both contexts a new column was created on the animals tabs "doubled tagged". Doubled tagged is only checked in case the tags of an animal are from different contexts. Scientific names are checked against the WoRMS database <https://www.marinespecies.org/> in order to increase standardization. Upon uploading a bulk file or using the creation form, you will be informed when misspelled or not existing names are being used. The release notes are now available online. ###Improvements The validation rules for the Tag form and bulk upload have been made more stringent. - If tag_type = ID tag AND steps =1 THAN ID tag - IF tag_type = Sensor tag AND steps = 1 --> ID tag + sensor tag - IF tag_type =ID tag AND steps = 2 --> ID tags + step 2 - IF tag_type =ID tag AND steps = 3 --> ID tags + step2 + Step3 - IF tag_type =ID tag AND steps = 4 --> ID tags + step2 + step3 + step4 - IF tag_type =sensor tag AND steps = 2 --> ID tags + sensor tag + step 2 - IF tag_type =sensor tag AND steps =3 --> ID tags + sensor tag + step 2 + Step3 - IF tag_type =sensor tag AND steps= 4 --> ID tags + sensor tag + step 2 + step3 + step4 - IF tag_type =sensor tag AND sensor_type=acceleration AND steps=1 --> ID tags + sensor tags + acellerometer - IF tag_type =sensor tag AND sensor_type=acceleration AND steps=2 --> ID tags + sensor tag + accelerometer + step 2 + STEP2_ACCELERATION_DURATION - IF tag_type =sensor tag AND sensor_type=sensor_type=acceleration AND steps=3 --> ID tags + sensor tag + accelerometer + step 2 + Step3 + STEP2_ACCELERATION_DURATION + STEP3_ACCELERATION_DURATION - IF tag_type =sensor tag AND sensor_type=acceleration AND steps=4 --> ID tags + sensor tag + accelerometer + step 2 + step3 + step4 + STEP2_ACCELERATION_DURATION + STEP3_ACCELERATION_DURATION + STEP4_ACCELERATION_DURATION Introduction of 2 new sensor types for acoustic tags, mortality Alive and mortality dead. Allowed to add upto 4 tags per animal. ###Bug Fixes

###New Allowing for protocols to be configured per deployment. For this functionality we made the link between receivers and models stricter. You can no longer use free text as a model, instead you will need to use the models configured in ETN. When any are missing you can always take up contact with us. You can find the list in the acoustic telemetry context, tab Data->Import metadata. As the possible protocol combination are defined per receiver model, you will now be able to configure a suiting one when editing or creating a deployment. ###Improvements Do Not allow detections to be uploaded 24 hours before the start date of the active deployment. To resolve the issue of having large amounts of detections flagged as outside the deployment period. We will from now on not import detections from 24 hours before the start date of the active deployment. A data clean is being considered, no date is set yet. Compliance naming format of VDAT files from Fathom Mobile. VDAT files uploaded to the cloud, have a different format. Important, it may be necessary to rename your receiver by adding the frequency. ex. your receiver is called VR2W. In the past your filename would look something like this: VR2W_111222_20240422_1.vdat now it may also look like this: VR2W-69 111222 2024-04-22 222333.vdat For the receiver to be matched however it will need to be renamed from VR2W to VR2W-69. Allow for repeated headers in FPOD files. Automated exports can repeat headers in FPOD files, our import scripts can now handle this. Important, it is allowed that you remove all but the first headers from the file or none, nothing in between. Please do not add headers, as this will result in failure of the import. Only allow upload of detections to your projects. It is no longer possible to upload detections to projects of which you are not a member. ###Bug Fixes Memory leak while importing detections for Thelma receiver. Our system had a misconfigured flow for importing detections of Thelma receivers when the auto creation of a new deployment was activated. A fix was introduced with no impact to the users. Fixes to automated changes to receiver status. It has been a struggle to make all flows work in harmony. Because we understand the necessity of a correct configuration of this parameter, we have taken a holistic view at this issue. The system will no longer automatically change statuses of receivers from lost, returned to manufacturer or broken. It is however still possible to upload detections for those receivers (lost, returned, broken), but not with autocreation of a new deployment. You can always set the status of a receiver manually. On any changes to deployments we check if the latest deployment is still active, in this case the receiver stays active, otherwise we set it too available.