The homepage for the ACLED data project can be found here, but to use this dataset for a DSAN 6000 project, you should use the full, extracted data available in the S3 bucket at the following URI:
s3://dsan6000-data/acled_events.parquet
For this pathway, imagine you have been hired by ACLED and asked to apply your DSAN 6000 skills to a research project aimed towards improving their event-processing pipeline. Their needs are:
Decreased “latency time”, in the sense that more events can be detected and their severity (in terms of civilian impacts) can be estimated in real time, while allowing these severity-levels to update as more news reports stream in
A dashboard of these detected events (and their estimated severity), publicly available for organizations like Médecins Sans Frontières to use in their allocation of medical workers across different regions
An “official” ACLED report drawing on the detected events and derived statistics, that will in turn likely be cited in UN Human Rights Council discussions and reports
As part of this task, you have been given access to ACLED’s OLTP database (described below), and you have been told to “take it from there”: your job, on Questions 1-6 on the Midterm, is to plan out what each step in an OLTP \(\leadsto\) OLAP \(\leadsto\) analytic insights pipeline for this task might look like.
Question 1 Starter: OLTP Structure
For the purposes of the midterm, you should think of the data you worked with in HW4 and HW5 as the form of this data already extracted to OLAP. Meaning, for the midterm you are going a few steps back to the OLTP records that are originally received by ACLED. An example of the OLTP records that might show up in a given period of time is as follows, where you can imagine this as a sample of the most-recently-added rows in an events table (think of the streaming-events OLTP demo from the Week 1 slides!)
Note the complexities that may be involved in turning this OLTP-format stream of events into an analytics-friendly OLAP infrastructure meeting ACLED’s needs (as listed above). For example:
Despite the range in received timestamps (between February 28 and March 29), these reports actually describe two separateincidents from US bombings in Iran earlier this year, which occurred on the same day (February 28)
This range of locations, in turn, means that the pipeline needs to be able to handle reports in several languages (and across many non-standardized platforms like local news sites, X.com, and Telegram): Events in Somalia may be reported in Somali, for example, which can be written in three different scripts, while events in the far northeast of Syria may be reported in Kurmanji, the language widely used by autonomous Kurdish militia groups operating in this “corner” of the country.