https://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112020-04-24T09:38:08ZRedmineOpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59632020-04-24T09:38:08ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/1091">Feature #1091</a>: Reference systems for types</i> added</li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59652020-04-24T09:38:19ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/991">Feature #991</a>: Images/Files for Types</i> added</li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59682020-04-24T10:24:27ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/991">Feature #991</a>: Images/Files for Types</i>)</li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59692020-04-24T13:06:54ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5969/diff?detail_id=7811">diff</a>)</li><li><strong>Category</strong> set to <i>Backend</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Acknowledged</i></li><li><strong>Assignee</strong> set to <i>Stefan Eichert</i></li><li><strong>Target version</strong> set to <i>6.0.0</i></li></ul><p>@ Stefan, thank you for reporting and explaining it to me. As soon as prerequisites are fulfilled (please put both in the description) you can remove yourself as assignee and leave assignee empty.</p> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59702020-04-24T13:25:47ZStefan Eichertstefan.eichert@univie.ac.at
<ul></ul><p>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. However if you have other ideas, we can of course discuss them.</p>
<p>Regarding the manual text, here a first proposal:</p>
<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> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59712020-04-24T13:26:57ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5971/diff?detail_id=7816">diff</a>)</li><li><strong>Assignee</strong> deleted (<del><i>Stefan Eichert</i></del>)</li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59722020-04-24T13:29:34ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5972/diff?detail_id=7818">diff</a>)</li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=59772020-04-24T17:41:31ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Subject</strong> changed from <i>Timespans for types</i> to <i>Time spans for types</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5977/diff?detail_id=7827">diff</a>)</li></ul><p>That they are only meant for custom types changes everything (maybe I missed it). In that case I think the suggestion for an option (default off) at creating/updating a custom type hierarchy would be most suitable. For now we could implement it like the <strong>multiple</strong> option: once set it cannot be removed. Hopefully a meeting will be possible soon so that we can discuss it shortly in person.</p>
<p>Thanks for the manual text proposal.</p> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=64922020-09-30T10:50:50ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/6492/diff?detail_id=8445">diff</a>)</li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=68792021-02-18T15:44:44ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Target version</strong> changed from <i>6.0.0</i> to <i>6.2.0</i></li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=69822021-03-19T15:01:46ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Target version</strong> changed from <i>6.2.0</i> to <i>6.1.0</i></li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=69832021-03-20T10:59:12ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>Acknowledged</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>Alexander Watzinger</i></li></ul> OpenAtlas - Feature #1215: Time spans for typeshttps://redmine.openatlas.eu/issues/1215?journal_id=70102021-04-01T11:06:44ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>I implemented types for dates and it will be released with 6.1.0.<br />Depending on how far we get with adapting API and Discovery for newest changes I may push the development version to THANADOS already this weekend and will send out newsletter if I do.</p>