Added if statement to check if metadata already exists.

Added if statement to copy-absolutes to check if metadata already exists before upload. If it does, the upload will be skipped. I could make this a separate function but not sure if it is necessary.

I have tested this thoroughly for 2023 data in production and it always works as expected. However, this often does not work correctly in staging due to the nature of the staging database. The MetadataFactory query will always return empty readings if they exist in the staging database which is bizarre. Empty readings should not exist in production but perhaps the MetadataFactory queries should be tested more in a separate issue.

requested review from @erigler

assigned to @awernle

Can you elaborate on what you mean by "nature of the staging database"? If the staging readings which are causing trouble are literally empty, maybe we can perform a simple check here, and circle back to add more robust validation to the MetadataFactory in a separate issue.

Here is an empty BOU set as an example. This was probably made when I tested ignoring empty readings, some metadata is filled out but the starttime and endtime are null (because webabsolutes requires 4 sets even if some are empty). The prior_metadata request will always return this reading instead of the one below it with a proper starttime and endtime. Thankfully, these do not exist in production.

resolved all threads

approved this merge request

marked this merge request as ready

mentioned in commit ad79c7b0

merged

mentioned in issue #71 (closed)