The standard protocol currently says that 'Age_calculated' is based on 'RingAge' from the individual table, which is a bit misleading as both 'Age_calculated' and 'RingAge' are derived from 'Age_observed'. It makes sense that 'Calculated_age' isn't based on 'RingAge' since information in the Individual data table shouldn't be needed to derive something in the Capture data.
To make this clearer, I think the documentation just needs to be modified to say that 'Age_calculated' is based on the 'RingSeason' and 'BreedingSeason' and that an exact age is only calculated for individuals banded as chicks.
The standard protocol currently says that 'Age_calculated' is based on 'RingAge' from the individual table, which is a bit misleading as both 'Age_calculated' and 'RingAge' are derived from 'Age_observed'. It makes sense that 'Calculated_age' isn't based on 'RingAge' since information in the Individual data table shouldn't be needed to derive something in the Capture data.
To make this clearer, I think the documentation just needs to be modified to say that 'Age_calculated' is based on the 'RingSeason' and 'BreedingSeason' and that an exact age is only calculated for individuals banded as chicks.