Great to have such an international group of participants at today’s @nodegoat workshop for the @IHEID

RT @Inge_vanVugt: The CfP of Historical Networks – Réseaux Historiques – Historische Netzwerke 2021 is out! http://historicalnetworkresearch.org/call-for-papers-historical-networks-reseaux-historiques-historische-netzwerke-2021/ via @hn…

RT @retro_conflicts: Just concluded our third @nodegoat webinar with @LAB1100: this time about database visualisations. Many thanks to our…

RT @FontesLatini: @agata_pal from the @FU_Berlin presents the first results of the "Patterns of Knowledge Circulation" project: #cluster an…

RT @kaspargubler: Nice visualisation out from the hallerNet project (http://www.hallernet.org/)...working for the first time with nodegoat...…

RT @ACUH_UvA: Thursday 29 October, @retro_conflicts hosts a @nodegoat webinar on visualization and the importing and exporting of data. All…

RT @retro_conflicts: 29.10 (10:00-12:30) we will organize the 3rd @nodegoat webinar w/ @LAB1100: focusing on visualisations and importing/e…

RT @johandewittNL: @stadholderswife @Kon_Verz Een hele interessante blog voorzien van een filmpje, gemaakt met behulp van @nodegoat, waarin…

RT @retro_conflicts: Thank you to the @nodegoat team for their clear presentation and to all our participants for their questions and insig…

RT @retro_conflicts: #savethedate 17.09 & 8.10: together w/ @nodegoat, our project is organizing 2 webinars on how to build source database…

@unjapanologist @beavanacker These events are organised by this project: https://premodernconflictmanagement.hcommons.org/. You can check with them to see if any spots are available.

@nodegoat #nodegoat runs on our own hardware, located in The Hague. #oldsouls

Server upgrade went smoothly. http://nodegoat.net is in full operation again since 13:00 CEST. https://twitter.com/nodegoat/status/1285230792705220609

RT @ERC_SKILLNET: Impressive 10min presentation by @HumanitiesUU's student Maiah Letsch. Using @nodegoat she mapped the layered network of…

@Lotte_Kosthorst Treat yourself to a short break tomorrow morning 🙌

Due to server maintenance http://nodegoat.net will be in read-only mode between 09:00 and 13:00 CEST Wednesday 22 July.

Happy to be part of this exciting project! Stay tuned for more linked data ingestion features of @nodegoat https://twitter.com/kaspargubler/status/1276192493030330374

Iterative data modelling 🙌 https://twitter.com/warlux_c2dh/status/1271054532496232449

@bebio_amaro CC: @technetempire

@kgeographer The nodegoat Guides focus on how this can be used in nodegoat, see https://nodegoat.net/guides/chronologystatements and https://nodegoat.net/guides/relationalchronologystatements. Extensive technical documentation for latest features is in the works and will be published here: https://nodegoat.net/documentation. Happy to answer any specific Qs!

Two new #nodegoat use cases added:

'Visualizing Early Nineteenth-Century Foreign Commercial Activity at Pernambuco' https://nodegoat.net/usecase.p/372.m/46/visualizing-early-nineteenth-century-foreign-commercial-activity-at-pernambuco

'FORMAL. Mapping Fountains over Time and Place'
https://nodegoat.net/usecase.p/372.m/47/formal-mapping-fountains-over-time-and-place

Or go to https://nodegoat.net/usecases to explore all use cases.

RT @Inge_vanVugt: So addictive indeed @kaspargubler! Behold the Grand Tour of Cosimo III in the Dutch Republic (1667-1668) @nodegoat #histo…

RT @kaspargubler: Simply integrate historical maps into @nodegoat as background for the visualizations...but beware, the old maps can cause…

RT @Lotte_Kosthorst: Keine Dachterrasse, aber geht auch! 😉
#StayAtHome #covid19italy #Nodegoat #HomeOffice https://twitter.com/centro_tedesco/status/1253275909341265920

How do you store people or locations that share a name, like Hottinger, Hottinger, Hottinger, or Hottinger?

Read this blog post to learn how to deal with ambiguous identities: https://nodegoat.net/blog.s/45/how-to-store-uncertain-data-in-nodegoat-ambiguous-identities (4/4)

How do you store contradictions in your source material, like born "about 1666" or "in 1668/9"?

Read this blog post to learn how to deal with conflicting information: https://nodegoat.net/blog.s/44/how-to-store-uncertain-data-in-nodegoat-conflicting-information (3/4)

How do you store vague or incomplete statements, like: "born about 1666, probably in or near London"?

Read this blog post to learn how to deal with incomplete source material: https://nodegoat.net/blog.s/43/how-to-store-uncertain-data-in-nodegoat-incomplete-source-material (2/4)

Your database for historical data should be able to record various levels of uncertainty. @t_winnerling contributed to the #nodegoat blog to discuss multiple strategies for storing uncertain data: https://nodegoat.net/blog.s/42/how-to-store-uncertain-data-in-nodegoat (1/4)

RT @gerthuskens: My first try at visualizing the @Egyptology_PP @nodegoat data on the evolution of the Belgian diplomatic corps in Egypt be…