Skip to content
Monika Barget edited this page Apr 17, 2024 · 24 revisions

Welcome to the DigiKAR AP3 data structure wiki!

This wiki explains the data columns used to collect and enrich biographical data from early modern Mainz. Use the collapsible PAGES menu on the right to browse entries alphabetically, or use the SEARCH BOX under PAGES.

The data columns are found in three different types of tables used in AP3:

  1. The event-focused factoid lists contain information on who did what, when and where.
  2. The separate person names list disambiguates people mentioned in the factoids and assigns an ID to each person.
  3. The separate places list specifies historical place names, assigns coordinates, and links them with a Geonames ID.

Not all data columns used in these three types of files were also necessary for data queries and visualisation in the last project phase, which is why the following table outlines which data columns were exported.

The following table describes the harmonized schema for all analytical lenses. It is used to create a database for eventually deriving visualisations.

New Column Name Former Column Name Data Type Null File Origin
analytical_lens none varchar yes not in original data model
event_after_date event_after-date varchar yes factoid lists
event_before_date event_before-date varchar yes factoid lists
event_date event_date varchar yes factoid lists
event_editorial_comment comment varchar yes factoid lists
event_end event_end varchar yes factoid lists
event_historiographical_comment info_dump varchar yes factoid lists
event_id factoid_id varchar no factoid lists
event_related_persons rel_pers varchar? list? yes factoid list
event_source source varchar yes factoid lists
event_source_criticism additional_info varchar yes factoid lists
event_source_quotations source_quotations varchar yes factoid lists
event_start event_start varchar yes factoid lists
event_type event_type varchar no factoid lists
event_value none varchar yes added from separate dictionary
institution_name inst_name varchar yes factoid lists
person_alternative_names alternative_names varchar yes factoid lists
person_function pers_func varchar yes factoid lists
person_id pers_id, pers_id_fs, pers_id_mb varchar no factoid lists, person names list
person_name pers_name varchar no factoid lists, person names list
person_title pers_title varchar yes factoid lists
place_geonames_id place_geonames_id varchar yes places list
place_geonames_latitude (geonames/google)_latitude(s) real yes places list
place_geonames_longitude (geonames/google)_longitude(s) real yes places list
place_name place_name varchar yes factoid lists, places list
place_name_variants merge place_name_old, variant 1, 2 and 3 into one column varchar yes places list
place_type Gebiet Territorium varchar yes places list

Information not included in final data export for visualisation:

New Column Name Former Column Name Data Type Null File Origin
person_editorial_comment editorial_comment varchar yes person list
person_frequency freq varchar yes person list
person_relevance poi varchar yes person list
place_geonames_address geonames_address varchar yes places list
place_community community varchar yes places list
place_continent continent varchar yes places list
place_editorial_comment place_editorial_comment varchar yes places list
place_google_address place_google_address varchar no places list
place_google_latitude place_google_latitude varchar no places list
place_google_longitude place_google_longitude varchar no places list
place_region_1 region_1 varchar yes places list
place_region_2 region_2 varchar yes places list
place_source Source varchar yes places list
place_suffix suffix varchar yes places list

For details, read our background information on the DigiKAR data structure and the modelling decisions behind the column names.

BACK TO DOCUMENTATION HOMEPAGE

Clone this wiki locally