I would like to propose an evolution in tch so that the information concerning dates could be more powerful and versatile in different contexts of data entry. A portal for 'other dates' should work for tch1 and tch2, where lines with different kinds of chronological information could be added when needed. That portal only needs a field for the date and another field for its explanation.
I also wonder if another solution is to implement an annotated data model for dates (as happens with uncertainty)
In the case of the Museum of Prehistory of Valencia we need, for example, to set the find date of a specific object and it does not seem useful to create a field just for that purpose. Take into account there's another 'specific' field for dates. The 'use dating' field (tch236) that could perhaps also disappear and become part of the above mentioned portal.
Is this a viable idea? Is it useful to specify other chronological information contexts?
'Other dates' component
5 days later
I think that implement a flexible portal for dates could be a good idea, as the measure portal, a neutral portal to add any kind of date, with date and remark as you say, but I think will need to expand it with the typologyof the date to ensure that this date is calibrate date, or other posibilites.
Another thing to think about is that this portal will overlap with the chronological thesaurus, because if you want to define some dates as periods the right way is to use the chronological thesaurus. So a portal for different dates could be fine, but I think you need a "context of use" for the users. And current date fields will still be needed as well.
Best