RT @Inge_vanVugt: So addictive indeed @kaspargubler! Behold the Grand Tour of Cosimo III in the Dutch Republic (1667-1668) @nodegoat #histo…
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…
🗺️ Map from @DavidRumseyMaps: https://www.davidrumsey.com/luna/servlet/s/i52u82
🌐 Georeferenced with @Georeferencer: https://davidrumsey.georeferencer.com/maps/1e7203aa-938c-5771-ac44-649a558c1af7/view
🔎 Explore the interactive #nodegoat visualisation here: http://demo.nodegoat.net/viewer.p/48/1/scenario/12/geo/fullscreen
Learn how to visualise your historical data on a historical map by following this guide: https://nodegoat.net/guides/historicalmap
"FORMAL. Mappare il movimento delle fontane monumentali nel tempo e nello spazio attraverso la geovisualizzazione" shows how #nodegoat can be used for inner city mappings. Presented by P. Palomba, E. Garzia, R. Montanari at #AIUCD2020
RT @geierandrea2017: Falls ihr heute auch 1 schöne Ziege brauchen könnt.
RT @ERC_SKILLNET: There are two new blog posts on our website by Michael Barg and Hester Smit, with analyses of #earlymodern mss. 985 and 9…
#nodegoat internship 👇 https://twitter.com/gzornetta/status/1223160273978253314
RT @joewett: New post: CfP: Data for History 2020: Modelling Time, Space, Agents https://digihum.de/blog/2020/01/31/cfp-data-for-history-2020-modelling-time-space-agents/
RT @kaspargubler: Check out our usecase for the database migration from MS SQL server to nodegoat...👇
https://nodegoat.net/usecase.p/372.m/41/repertorium-academicum-germanicum---the-graduate-scholars-of-the-holy-roman-empire https://t.co…
RT @HNR_org: Out now: Call for papers for the 2020 Historical Network Research Conference at @C2DH_LU in Luxembourg.
We're thrilled to an…
RT @SonjaKmec: Cool graph: Which historical figures have been celebrated by means of portraits on European postage stamps? Using @nodegoat…
@waitmanb @PleiadesProject Yes, please send an email to support@nodegoat.net
To store your own list of locations in nodegoat, create a Type with a single sub-object which you can either fill in manually, by changing 'Location: Reference' to 'Location: Point', or import data into.
@waitmanb @PleiadesProject You can then use these locations in any other Type as location reference (3/3)
@waitmanb @PleiadesProject You can connect these column headings to your data model with an import template in nodegoat. For this to work, your gazetteer Type in nodegoat needs a sub-object that can host these locations (this auto-generates the lat/long elements) (2/3)
@waitmanb Happy to help! To give an example: if you have a CSV file like this sample from a @PleiadesProject dump http://atlantides.org/downloads/pleiades/dumps/ (1/3)
RT @hild_de: Full-day workshop on analyzing historical datasets with @nodegoat @HuygensING Jan 16 - #SNA #DH #digitalhistory https://t.co/h…
RT @hild_de: Full-day workshop on analyzing historical datasets with @nodegoat @HuygensING Jan 16 - #SNA #DH #digitalhistory https://t.co/h…
RT @technetempire: and our project @nodegoat
Thanks to Prof. Rafael Moreira @CentroCham and Prof. Beatriz Bueno for organising the sessio…
RT @abbysgondek: New Developments in Holocaust Studies and the Digital Humanities http://abbysgondek.com/2019/11/18/new-developments-in-holocaust-studies-and-the-digital-humanities/
RT @technetempire: Ongoing now: @nodegoat Workshop provided by @LAB1100 team / a partnership @technetempire project from @CentroCham with L…
RT @ihc_fcsh: O próximo workshop de #HumanidadesDigitais é já na próxima semana, nos dias 5 e 6!
Será dedicado à Plataforma @nodegoat, tend…
RT @RAG_online: RAG-Treffen mit dem Projekt Padova2022 zum Jubiläum @UniPadova 1222-2022. Pierreluigi Terenzi stellt die neue Datenbank des…
Looking for a Google Fusion Tables alternative? In #nodegoat you can define and link multiple tables and run visualisations instantly.
ℹ️ Learn how to work with #nodegoat by following the Guides: https://nodegoat.net/guides/
➡️ Get a #nodegoat account here: https://nodegoat.net/requestaccount https://twitter.com/OpenLinkArtData/status/1183650862599671808