{"id":550,"date":"2021-06-16T18:25:14","date_gmt":"2021-06-16T18:25:14","guid":{"rendered":"http:\/\/hnr2021.historicalnetworkresearch.org\/?page_id=550"},"modified":"2021-06-21T12:34:04","modified_gmt":"2021-06-21T12:34:04","slug":"historical-dates-as-networks-introducing-chronology-statements-for-nodegoat","status":"publish","type":"page","link":"http:\/\/hnr2021.historicalnetworkresearch.org\/?page_id=550","title":{"rendered":"Historical Dates as Networks: Introducing Chronology Statements for nodegoat"},"content":{"rendered":"\n

Pim van Bree <\/em>and Geert Kessels<\/h2>\n\n\n\n

Place and Time:<\/strong> Friday, 02.07., 14:40\u201315:00, Room 1
Session:<\/strong> Software Demos<\/p>\n\n\n\n

Keywords:<\/strong> Time; chronology; uncertainty; vagueness; data; visualisation<\/p>\n\n\n\n

The open-source software nodegoat (https:\/\/nodegoat.net\/<\/a>) is a research environment that allows\u00a0 scholars to create, analyse, and visualise datasets that are temporally and spatially attributed. Due\u00a0 to its focus on time, space, and relationality nodegoat is used by many scholars for historical\u00a0 network research projects.[1]<\/p>\n\n\n\n

nodegoat has been expanded with a ‚Chronology Statements‘ functionality to allow for vague and\u00a0 relational date statements. Our paper demonstrates how this works and how it can be used for\u00a0 historical network research purposes.\u00a0<\/p>\n\n\n\n

In database software date statements have to be precise and complete. To store incomplete and\u00a0 imprecise dates the EDTF format (ISO 8601-2:2019) has been developed.[2] Although EDTF is a\u00a0 step in the right direction, the format is less suitable for historical research as it lacks options for\u00a0 relational date statements (e.g. ‚X happened 10 weeks before Y‘) and it is not open for self-defined\u00a0 cycles (‚X happened during the „Sommersemester“ of 1766‘).<\/p>\n\n\n\n

nodegoat already provided the functionality to store incomplete dates or periods (e.g. ‚7-1788‘, or\u00a0 ‚1656 – 8-1657‘). By using the new Chronology Statements functionality a scholar can now make\u00a0 imprecise date statements in which the level of imprecision is defined by the scholar. The self defined imprecision quantifies the vagueness of the date and makes the statement suitable for\u00a0 computation. This approach, in contrast to qualitative statements like ‚circa‘ or ‚around‘ and the\u00a0 EDTF qualification characters ‚?‘, ‚~‘, ‚%‘, produces date statements that can be used for filtering,\u00a0 analysis, and visualisation purposes.<\/p>\n\n\n\n

The self-defined imprecision works as follows: instead of stating ‚around 1800‘, a scholar makes a\u00a0 Chronology Statement that reads as ‚the date point is between 10 years before the begin of 1800\u00a0 and 10 years after the end of 1800‘. In the nodegoat interface, the form to input this statement looks like:<\/p>\n\n\n\n

\"\"<\/a><\/figure><\/div>\n\n\n\n

Chronology Statements can both be expressed by scholars and understood by computation. To  compute this statement it is translated into JSON, for which the ChronoJSON format has been  developed: <\/p>\n\n\n\n

\"\"<\/a><\/figure><\/div>\n\n\n\n

The offset amount, the offset value, and the operators can be defined by the scholar. Chronology\u00a0 Statements can also be applied to periods with two, three, or four single statements.<\/p>\n\n\n\n

To store relational dates, the date value can be replaced by a reference to a Chronology Statement\u00a0 stored in another object. Unimodal relational dating can be used to position an object of a type in\u00a0 relation to one or more objects of the same type, e.g. ‚letter X was sent after letter Y and before\u00a0 letter Z‘. Multimodal relational dating can be used to position an object of a type in relation to one\u00a0 or more objects of another type, e.g. ‚event X was held after the begin of the reign of emperor Y\u00a0 and before the death of person Z‘.[3]\u00a0<\/p>\n\n\n\n

Reoccurring time spans can be stored as ‚Cycles‘. These cycles (e.g. ‚winter‘, ‚Sommer Semester‘)\u00a0 can be used in a Chronology Statement to state that a person lived in a city between the end of\u00a0the summer of 1848 and the beginning of spring of 1854 (i.e. from 21-09-1848 until 20-03- 1854).[4]\u00a0<\/p>\n\n\n\n

The operators that are applied within the statements are similar to Allen operators and are in line\u00a0 with the computational efficiency of, for instance, temporal relational primitives.[5]\u00a0\u00a0\u00a0<\/p>\n\n\n\n

References<\/strong><\/p>\n\n\n\n

[1] Ingeborg van Vugt, ‚Using Multi-Layered Networks to Disclose Books in the Republic of Letters‘,  Journal of Historical Network Research 1 (2017) 25-51. Toby Burrows, ‚The History and Provenance  of Manuscripts in the Collection of Sir Thomas Phillipps: New Approaches to Digital  Representation‘, Speculum 92 (2017) 39-64. D\u2019haeninck, Thomas, Randeraad Nico, and Christophe  Verbruggen, ‚Visualizing Longitudinal Data: Rooted Cosmopolitans in the Low Countries, 1850- 1914.‘ CEUR Workshop Proceedings. Ed. Serge Ter Braake et al. Vol. 1399. Aachen: CEUR WS,  2015. 116\u2013121. For more examples see: zotero.org\/lab1100\/tags\/nodegoat<\/a>.  <\/p>\n\n\n\n

[2] https:\/\/www.loc.gov\/standards\/datetime\/<\/a>  <\/p>\n\n\n\n

[3] https:\/\/nodegoat.net\/guides\/relationalchronologystatements<\/a>  <\/p>\n\n\n\n

[4] https:\/\/nodegoat.net\/guides\/cycles<\/a>  <\/p>\n\n\n\n

[5] J.F. Allen, ‚Maintaining knowledge about temporal intervals‘, Communication of ACM (1983)  832-843, http:\/\/www.cidoc-crm.org\/sites\/default\/files\/CIDOC%20CRM_v6.2.7_Definition_esIP.pdf<\/a>, Papadakis, Emmanuel and  Martin Doerr. \u201cTemporal Primitives, an Alternative to Allen Operators.\u201d EMF-CRM@TPDL (2015).<\/p>\n","protected":false},"excerpt":{"rendered":"

Pim van Bree and Geert Kessels Place and Time: Friday, 02.07., 14:40\u201315:00, Room 1Session: Software Demos Keywords: Time; chronology; uncertainty; vagueness; data; visualisation The open-source software nodegoat (https:\/\/nodegoat.net\/) is a research environment that allows\u00a0 scholars to create, analyse, and visualise datasets that are temporally and spatially attributed. Due\u00a0 to its focus on time, space, and relationality nodegoat is used by<\/p>\n

Weiterlesen<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":98,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/pages\/550"}],"collection":[{"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=550"}],"version-history":[{"count":5,"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/pages\/550\/revisions"}],"predecessor-version":[{"id":635,"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/pages\/550\/revisions\/635"}],"up":[{"embeddable":true,"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=\/wp\/v2\/pages\/98"}],"wp:attachment":[{"href":"http:\/\/hnr2021.historicalnetworkresearch.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}