When we upload data to the server in the Data Processing > Backup Metadata module, we do checks on the Species Table and Individual Table to make sure that we aren’t re-uploading the same data multiple times. It does line by line and if the line of data exists on the server, it is skipped, and it only uploads lines that are not yet on the server.
However, this process doesn’t seem to apply to the Trigger Table, CA or TS Tables (which caused some havoc in https://pantheracorporation.atlassian.net/browse/MAIN-796 when Isaiah and Shannon uploaded the same dataset twice by accident. We need to add this process to the Trigger Table, the CA Table, and the TS Table to ensure that duplicates aren’t uploaded.
When we upload data to the server in the Data Processing > Backup Metadata module, we do checks on the Species Table and Individual Table to make sure that we aren’t re-uploading the same data multiple times. It does line by line and if the line of data exists on the server, it is skipped, and it only uploads lines that are not yet on the server.
However, this process doesn’t seem to apply to the Trigger Table, CA or TS Tables (which caused some havoc in https://pantheracorporation.atlassian.net/browse/MAIN-796 when Isaiah and Shannon uploaded the same dataset twice by accident. We need to add this process to the Trigger Table, the CA Table, and the TS Table to ensure that duplicates aren’t uploaded.
┆Issue is synchronized with this Jira Task by Unito