LiamDBailey
commented
3 years ago @zuzulaz I've removed the comment about 'D14' as these aren't fake dates (we know they were captured 14 days after hatching).
I also don't think it's appropriate to include fake dates for 'HatchDate_observed', but I'll add more detail about this to the code review.
For several registers in the primary data, the Date is missing. Majority of those registers contain relevant information regarding the brood or individual data, therefore in order to preserve that information we input fake dates as Capture_date in several ocassions. Those are:
CaptureDate: For several adult individuals, where the capture date was missing and the record corresponded to the only capture (observation) of the individual in the breeding season, a fake date was input ("breeding season-06-01", 1st of June of the corresponding breeding season). For several adult individuals, where the capture data was missing and the capture method indicated that the capture happened during the incubation period, the fake date was input ("breeding season, 04-01", 1st of April of the corresponding breeding season).
Reason for the missing date as explained by the data owner: "That is partly because we gathered information about that bird via other methods (like an ID through the RFID system), or because information about the partner added. In the cases where exact dates are missing, we did not actually caught the bird (except for 2015!! there the dates are just missing while birds were truly caught). These dateless entry were made because it might be relevant in some of our further analyses."
HatchDate_observed: For several broods the hatch date was not provided. When neither hatch date nor capture date were provided, we input fake date ("breeding season-06-01", 1st of June of the corresponding breeding season).