Feature #1215
Updated by Stefan Eichert almost 4 years ago
In addition to files and external references for types, it would be beneficial to also be able to store temporal information with a type. Just the way we do it with other entities. E.g. a certain type of a find "Crescent Shaped Temple Ring" that occurs between 850 and 1050 should include this temporal information.
*Update*
To implement there are 2 prerequisites:
* Defining for which types
* Writing an English explanation text for the manual
To the questions of which types, it wouldn't make sense at e.g. actor actor relation. Since this is a very specific archeological use case I would prefer to only have it in some defined standard types and not in custom/value types. Otherwise we would have to think about some toggle option for specific projects.
*Update2*
These timespans should only apply to custom types. One solution could be to turn this option on when creating a new custom type. Another could be to create a new type-type like the value type.
Or we create a system type like "actor actor relation" for this, then all type trees of this would be under one hood.
However if you have other ideas, we can of course discuss them.
Regarding the manual text, here a first proposal:
<pre>
Typochronology types:
These types allow to define a timespan (earliest/latest begin and earliest/latest end) for each entry. This mostly applies to archaeological or art history respectively architectural types.
One example would be chronological groups for certain archaeological material cultures. Enamelled disc brooches for example would be linked to a type "Carantanian C3" This type would have the timespan from 900 to 1000.
Another example would be to link an E22 Sword to the type "Petersen X" that would have a timespan 900 to 1000.
This way objects (physical things E18 or E22) that do not have their own timespan defined can be traced chronologically via these chronological types.
</pre>