Schema mobility data
The different analytical lenses of the mobility data, follow a common data schema. This page describes this schema in detail.
The basis of every datum is an event, which is related to a person and a place. Hence, we group the columns the following categories, and prefix them accordingly:
- related to the event itself, prefix:
event_
- related to the primary person of that event, prefix:
person_
- related to place the event is assigned to:
place_
Event related columns (prefix: event_
)
event_id
Description
Unique identifier for the event.
Every datum in the DigiKAR project gets a unique identifier for the event. This identifiers are prefixed. For example, stud2715
is a unique identifier for a student event.
WARNING
Is the prefix actually necessary? If so do we still need the event_analytical_lens
?
Examples
stud2715
123456
event_date
Description
Used if exact event date is known, mostly in YYYY-DD-MM format.
INFO
Explain here why this is a simple string, and not consistent
Examples
1684-08-03
1732
1737-12-10
event_date_start
Description
Used if the start point of an event is known
This datatype is not yet described
event_date_end
Description
Used if the end point of an event is known
This datatype is not yet described
event_date_before
Description
Used if it is known that the event happened before a certain date
This datatype is not yet described
event_date_after
Description
Used if it is known that the event happened after a certain date
This datatype is not yet described
event_type
Description
No short description provided.
This datatype is not yet described
event_value
Description
flexible, research-dependent categorisation of events to foster a user-friendly visualisation
This datatype is not yet described
event_editorial_comment
Description
Any editorial comments on the event
This datatype is not yet described
event_histogriographical_comment
Description
Any histogriographical comments on the event
This datatype is not yet described
event_source
Description
The source of the event
This datatype is not yet described
event_source_comment
Description
No short description provided.
This datatype is not yet described
event_source_criticism
Description
No short description provided.
This datatype is not yet described
event_source_quotations
Description
No short description provided.
This datatype is not yet described
event_related_persons
Description
No short description provided.
This datatype is not yet described
event_analytical_lens
Description
Specifies from which analytical lense this event originates.
The “analytical lens” is a project-defined focus and reflects the research context in which the data were initially collected.
To get a better idea of the different types of ecclesiastical, academic, and political agents active in Electoral Mainz between the 16th and 18th centuries, our historians have manually collected biographic data relating to the Mainz government in the Eastern German exclave of Erfurt, Mainz officials represented at imperial institutions such as Reichstag (Imperial Diet), Reichshofrat and Reichskammergericht, and the organisation of the electoral court in Mainz itself. In addition, we have used XML data (harvested via API) and OCR technology to semi-automatically gather information on professors and students active at the early modern university of Mainz.
Examples
Statecalendar Jahns
Matriculations Mainz
Person related columns (prefix: person_
)
person_id
Description
No short description provided.
This datatype is not yet described
person_name
Description
No short description provided.
This datatype is not yet described
person_name_variants
Description
No short description provided.
This datatype is not yet described
person_function
Description
No short description provided.
This datatype is not yet described
person_title
Description
No short description provided.
This datatype is not yet described
Place related columns (prefix: place_
)
place_geonames_id
Description
No short description provided.
This datatype is not yet described
place_geonames_latitude
Description
No short description provided.
This datatype is not yet described
place_geonames_longitude
Description
No short description provided.
This datatype is not yet described
place_name
Description
No short description provided.
This datatype is not yet described
place_name_variants
Description
No short description provided.
This datatype is not yet described
place_type
Description
No short description provided.
This datatype is not yet described
Additional columns
institution_name
Description
No short description provided.
This datatype is not yet described