https://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112019-11-27T15:49:02ZRedmineOpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=55732019-11-27T15:49:02ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Assigned</i></li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=70622021-04-16T16:02:59ZStefan Eichertstefan.eichert@univie.ac.at
<ul></ul><p>Did some work on this and implemented radiocarbon dates in the THANADOS frontend using <a class="external" href="https://codeberg.org/steko/iosacal">https://codeberg.org/steko/iosacal</a> this python library.<br />In order to make it work properly with OpenAtlas we would need to store certain values: Date, Range and SampleNr<br />We created a value type for this that stores year and range separated by comma. <br />Maybe we discuss this in the next meeting. One idea would be value types, that also allow for strings, so the sample Number can also be stored.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=70962021-04-24T09:57:13ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/7096/diff?detail_id=9215">diff</a>)</li></ul><p>Added IOSACal suggestion from Stefan</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=71452021-05-10T13:20:48ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Target version</strong> changed from <i>Wishlist</i> to <i>7.4.0</i></li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=79542022-04-25T15:43:30ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul></ul><p>Just discussed it with Nina. Basically we could use a similar strategy like with sex estimation (make a new OpenAtlas class based on E55).<br />We should still discuss how the UI implementation and the result should be displayed. <br />Using IOSACal could be implemented in a next step.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=79832022-05-04T14:05:32ZBernhard Koschiček-Krombholz
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/7983/diff?detail_id=10377">diff</a>)</li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=79842022-05-04T14:07:55ZBernhard Koschiček-Krombholz
<ul></ul><p>Stefan will describe the model. (E59)</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=80082022-05-13T13:59:02ZStefan Eichertstefan.eichert@univie.ac.at
<ul></ul><p>For the conceptual implementation in OpenAtlas and to keep it as generic as possible I suggest:<br />1. define a new OpenAtlas class e.g. "string type" <br />2. allow for each of these type hierarchies to define parts of the string with possible validation E.g. <br /><pre><code class="javascript syntaxhl" data-language="javascript"><span class="p">{</span><span class="dl">"</span><span class="s2">labId</span><span class="dl">"</span><span class="p">:</span> <span class="dl">"</span><span class="s2">string</span><span class="dl">"</span><span class="p">,</span> <span class="dl">"</span><span class="s2">specId</span><span class="dl">"</span><span class="p">:</span> <span class="dl">"</span><span class="s2">string</span><span class="dl">"</span><span class="p">,</span> <span class="dl">"</span><span class="s2">radiocarbon year</span><span class="dl">"</span><span class="p">:</span> <span class="dl">"</span><span class="s2">integer</span><span class="dl">"</span><span class="p">,</span> <span class="dl">"</span><span class="s2">error</span><span class="dl">"</span><span class="p">:</span> <span class="dl">"</span><span class="s2">integer</span><span class="dl">"</span><span class="p">}</span></code></pre><br />3. Map it respectively resolve it the following way: E1 (every class in our system that can have a type) - has note P3 - E62 String "{"labId": "VERA", "specId": "23432A", "radiocarbon year": 2040, "error": 30}" - has type P3.1 - E55 radiocarbon dating "string type"</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=80352022-05-20T14:34:55ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Assignee</strong> changed from <i>Stefan Eichert</i> to <i>Alexander Watzinger</i></li></ul><p>Nina and I took a look at your suggestions and we like it.</p>
<p>So we would link <b>E?</b> -> <b>P3 has note</b> -> <b>E62 String</b><br />The last part with the type connection we would skip and instead write into the String itself that it is about radiocarbon dating e.g. <br /><pre><code class="java syntaxhl" data-language="java"><span class="o">{</span><span class="s">"analysis"</span><span class="o">:</span> <span class="s">"radiocarbon dating"</span><span class="o">,</span> <span class="s">"labId"</span><span class="o">:</span> <span class="s">"string"</span><span class="o">,</span> <span class="s">"specId"</span><span class="o">:</span> <span class="s">"string"</span><span class="o">,</span> <span class="s">"radiocarbon year"</span><span class="o">:</span> <span class="s">"integer"</span><span class="o">,</span> <span class="s">"error"</span><span class="o">:</span> <span class="s">"integer"</span><span class="o">}</span>
</code></pre><br />That way we could use it very generic for other analyses and also don't run into problems with already used types.</p>
<p>Thank you for your input Stefan, assigning to me now.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=80462022-05-21T14:28:29ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>Alexander Watzinger</i> to <i>Nina Richards</i></li></ul><p>Assigning to Nina, we will work together on it anyway but she is the specialist for this issue.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=80542022-05-23T09:34:27ZStefan Eichertstefan.eichert@univie.ac.at
<ul></ul><p>Alexander Watzinger wrote:</p>
<blockquote>
<p>Nina and I took a look at your suggestions and we like it.</p>
<p>So we would link <b>E?</b> -> <b>P3 has note</b> -> <b>E62 String</b><br />The last part with the type connection we would skip and instead write into the String itself that it is about radiocarbon dating e.g. <br />[...]<br />That way we could use it very generic for other analyses and also don't run into problems with already used types.</p>
<p>Thank you for your input Stefan, assigning to me now.</p>
</blockquote>
<p>I would prefer to keep the type connection, so it stays aligned with the CRM model and from within the database one can query for the type. If we implement this similar to previous type links and just add the string to the description, this can probably easily be accomplished. We however should document how to resolve this in the CRM.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=80552022-05-23T09:41:37ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul></ul><p>Sorry, but I'm a little confused. I was thinking we make a link between some entity to a <strong>E62</strong> entity and write the text into the description of the <strong>E62</strong> entity.<br />So we would have multiple <strong>E62</strong> entities with different descriptions and wouldn't need to write into link descriptions. Did I miss something?</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=81222022-06-03T14:27:09ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul></ul><p>I think I may have figured out why you want a type attached. Although we track what kind of text it is in the text itself, it could be cumbersome to e.g. find all texts that are related to radiocarbon dating because we would have to look at every text. Adding a type to these texts would solve this. In this case I too think we should use a link to a type instead of writing it to a link description.</p>
<p>Is this what you meant?</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=81292022-06-06T10:46:08ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Target version</strong> changed from <i>7.4.0</i> to <i>7.5.0</i></li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=81612022-06-08T14:13:01ZStefan Eichertstefan.eichert@univie.ac.at
<ul></ul><p>Obviously the redmine mails have been blocked as spam. Sorry for the late response. What you wrote is exactly what I mean. This way it can be resolved and further similar types we add can be distinguished better.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=81662022-06-08T15:56:29ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul></ul><p>Thanks for the feedback and no worries about the delay. Maybe it was a good thing, to let me figure it out myself :)</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=82772022-07-27T13:13:30ZStefan Eichertstefan.eichert@univie.ac.at
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-7 priority-4 priority-default" href="/issues/1748">Feature #1748</a>: Extended Value Types</i> added</li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=82992022-08-05T10:21:27ZNina Richards
<ul><li><strong>Target version</strong> changed from <i>7.5.0</i> to <i>7.7.0</i></li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=83792022-08-22T13:50:20ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/8379/diff?detail_id=10840">diff</a>)</li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=83802022-08-22T14:06:02ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/8380/diff?detail_id=10841">diff</a>)</li></ul><p>We updated the description and further specified the model and related information.<br /><a class="user active user-mention" href="https://redmine.openatlas.eu/users/16">@Stefan Eichert</a>, you might want to take a look at it because the model suggestions differs a little from what was described in <a class="issue tracker-2 status-7 priority-4 priority-default" title="Feature: Extended Value Types (Acknowledged)" href="https://redmine.openatlas.eu/issues/1748">#1748</a>. I like this model implementation more because it is "more" CIDOC conform because not using a link type.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=84882022-09-29T16:51:53ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Target version</strong> changed from <i>7.7.0</i> to <i>7.8.0</i></li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=86992022-11-09T15:37:52ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Target version</strong> changed from <i>7.8.0</i> to <i>7.12.0</i></li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=87032022-11-09T15:43:53ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Precedes</strong> <i><a class="issue tracker-2 status-7 priority-4 priority-default" href="/issues/1660">Feature #1660</a>: Tool: Age estimation</i> added</li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=90642023-01-11T13:06:18ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/9064/diff?detail_id=11647">diff</a>)</li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=90742023-01-12T12:55:09ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/9074/diff?detail_id=11658">diff</a>)</li></ul><p>Updated the model implementation after discussing it with Nina and Stefan.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=90892023-01-15T10:47:16ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Assignee</strong> changed from <i>Nina Richards</i> to <i>Alexander Watzinger</i></li><li><strong>Target version</strong> changed from <i>7.12.0</i> to <i>7.10.0</i></li></ul><p>I'm taking over this one after having implemented the main functionality with Nina.</p> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=90912023-01-15T10:50:40ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Precedes</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/1932">Feature #1932</a>: Manual: radiocarbon dating</i> added</li></ul> OpenAtlas - Feature #1090: Radiocarbon Datinghttps://redmine.openatlas.eu/issues/1090?journal_id=91232023-01-17T16:59:22ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul>