Date interval based on innermost and outermost tree-ring dates

[MattiasSealander]

With the new data from living trees there are now also innermost tree-ring dates submitted with the data. It seems that the innermost and outermost tree-ring dates could be combined in tbl_dendro_dates, with the innermost date in the age_older field and outermost date in the age_younger field, forming an interval for the tree date.

This is not how it is managed currently, as feedback is required from the dendrochronology labs regarding whether this is appropriate. The question is also how this affects the lookups (value_class/dendro_lookup) and naming of these. Currently they are separated into types named the same (innermost/outermost), but if both are combined and recorded in the age_younger/older fields, then there will only be one lookup needed, and what should this lookup be named? "Tree date interval"? At this point it is the domain specific understanding and logic that identifies the age_younger field as the innermost tree-ring date and vice versa. Which somehow needs to be recorded for future safeguards and understanding of the data.

Ultimately, feedback is required from the dendrochronologists on whether this is suitable, as well as how they want to see and use the data.