Skip to content

Commit 4f57f09

Browse files
authored
Merge pull request #11 from security-force-monitor/version-3-revision
Migrate Research Handbook to v3 data model
2 parents 7517123 + f419596 commit 4f57f09

File tree

203 files changed

+36637
-15244
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

203 files changed

+36637
-15244
lines changed

.readthedocs.yaml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,6 @@ formats:
3030
# Optional but recommended, declare the Python requirements required
3131
# to build your documentation
3232
# See https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
33-
# python:
34-
# install:
35-
# - requirements: docs/requirements.txt
33+
python:
34+
install:
35+
- requirements: source/requirements.txt

build/doctrees/claims-basic-1.doctree

38.3 KB
Binary file not shown.

build/doctrees/data_integrity.doctree

-38.5 KB
Binary file not shown.
9.72 KB
Binary file not shown.

build/doctrees/environment.pickle

326 KB
Binary file not shown.

build/doctrees/how-dates-work.doctree

67.3 KB
Binary file not shown.

build/doctrees/incidents.doctree

-118 KB
Binary file not shown.
120 KB
Binary file not shown.

build/doctrees/index.doctree

14.8 KB
Binary file not shown.

build/doctrees/introduction.doctree

14.9 KB
Binary file not shown.
7.66 KB
Binary file not shown.
19.5 KB
Binary file not shown.
207 KB
Binary file not shown.

build/doctrees/locations.doctree

-157 KB
Binary file not shown.

build/doctrees/overview.doctree

-7.59 KB
Binary file not shown.

build/doctrees/persons.doctree

-127 KB
Binary file not shown.

build/doctrees/persons_extra.doctree

60.8 KB
Binary file not shown.
88.9 KB
Binary file not shown.
98.2 KB
Binary file not shown.
6.34 KB
Binary file not shown.
31.9 KB
Binary file not shown.
97.6 KB
Binary file not shown.
16.1 KB
Binary file not shown.
Binary file not shown.
107 KB
Binary file not shown.
124 KB
Binary file not shown.

build/doctrees/sources.doctree

771 Bytes
Binary file not shown.
Binary file not shown.
15.3 KB
Binary file not shown.
33.2 KB
Binary file not shown.

build/doctrees/units.doctree

-232 KB
Binary file not shown.

build/doctrees/units_identity.doctree

152 KB
Binary file not shown.
93.8 KB
Binary file not shown.
116 KB
Binary file not shown.
13.8 KB
Binary file not shown.

build/html/.buildinfo

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
# Sphinx build info version 1
22
# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
3-
config: 4fbedb09362654a15bddd9c35f46ed8e
3+
config: c13dfd177e12598b3c7ea96cf1798990
44
tags: 645f666f9bcd5a90fca523b33c5a78b7
Loading
Loading
62.6 KB
Loading
Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
What is a claim?
2+
################
3+
4+
A claim is an assertion of information evidenced by a source.
5+
6+
The Monitor creates data from publicly available, mostly digital sources. We read and assess each source and turn the data we find in them into claims. Claims keep a piece of data together with the source from which it is derived, and may also tell us the time period for which the data is valid.
7+
8+
For example here is an excerpt from the news story `"Reshuffles in the military, war goes on”, published by the Shan Herald Agency for News (on the Burma News International website) on 10 September 2012 <https://www.bnionline.net/en/shan-herald-agency-for-news/item/13685-reshuffles-in-the-military-war-goes-on-.html>`_:
9+
10+
11+
.. admonition:: Example
12+
13+
Not only the government, but the military has been busy shuffling its commanders since the beginning of September, according to a source close to the War Office on Friday.
14+
15+
At least 5 regional commanders and a number of Bureau of Special Operations (BSO) chiefs and division commanders have been moved to new jobs. They include:
16+
17+
- Maj Gen Zeya Aung - Commander, Northern Region Command-to-Minister, Railway Transport
18+
- Brig Gen Aung Kyaw Zaw - Commander, Northeastern Region Command-to-Commander, Southern Region Command
19+
20+
Their former commands were taken over by Central Eastern Region Command Commander Brig Gen Tun Tun Naung and head of the armed forces technical school Brig Gen Aung Soe respectively.
21+
22+
23+
This source contains a mix of data that tells us something about the units of the Myanmar military and the people that hold positions in those units. The story contains data about the names of four persons:
24+
25+
- Zeya Aung
26+
- Aung Kyaw Zaw
27+
- Tun Tun Naun
28+
- Aung Soe
29+
30+
If we add information about their ranks, we can turn this data into a set of claims:
31+
32+
- The Shan Herald Agency for News claims that since the beginning of September 2012 a person called Zeya Aung had the rank of Maj Gen
33+
- The Shan Herald Agency for News claims that since the beginning of September 2012 a person called Aung Kyaw Zaw had the rank of Brig Gen
34+
- The Shan Herald Agency for News claims that at the beginning of September 2012 a person called Tun Tn Naun had the rank of Brig Gen
35+
- The Shan Herald Agency for News claims that since the beginning of September 2012 a person called Aung Soe had the rank of Brig Gen
36+
37+
The source contains further claims about the military units to which each person has been posted. For example, the source now makes four claims about the person called “Aung Soe”:
38+
39+
- The Shan Herald Agency for News claims that at the beginning of September 2012 a person called Aung Soe has been a commander in the military.
40+
- The Shan Herald Agency for News claims that since the beginning of September 2012 a person called Aung Soe had the rank of Brig Gen.
41+
- The Shan Herald Agency for News claims that since the beginning of September 2012 a person called Aung Soe was head of a unit called the Armed Forces Technical School
42+
- The Shan Herald Agency for News claims that since the beginning of September 2012 a person called Aung Soe became commander of a unit called the Northeastern Region Command
43+
44+
We can begin to express these claims more economically by using a set of standard fields. For example, we store the claimed name of a person in a field called “Person Name”, for example, to store their name:
45+
46+
- “Person Name” “Aung Soe”
47+
- “Date of claim”: “September 2012”
48+
- “Source of claim: ”Shan Herald Agency for News, 10 September 2012.
49+
50+
We can refine this further. In our system, claims have a range of different subjects: claims about the identity of a person, claims about a particular posting that a person has, claims about a unit’s identity or its relationships with others, and so on. Based on the type of information we’re pulling out from a source, we determine the type of claim that the source is making. So, data about a person’s name is a “Person Identity” claim type.
51+
52+
53+
.. csv-table::
54+
:file: _static/example-claim-as-table-A.csv
55+
:header-rows: 1
56+
:delim: tab
57+
58+
59+
The data about the unit to which the person is posted is a “Person Posting” claim type:
60+
61+
62+
.. csv-table::
63+
:file: _static/example-claim-as-table-B.csv
64+
:header-rows: 1
65+
:delim: tab
66+
67+
68+
From this point, we add shorter fieldnames to the claim to make it conform with the various data models we use. For example, a “Person Posting” claim type may include data about a person’s rank, role or title whilst posted to a unit, along with precise (or imprecise) dates for which this data are valid.
69+
70+
We also add additional data about the claim itself, such as an identifier, that allows it to be managed in our technical systems. We also transform how the source is expressed, substituting the text for a specific identity number that cites the page, paragraph, line number (amongst others) in the source. The “look” of claim begins to change a bit, but this simply depends on the tool that is used to manage it. For example, here’s how this claim looks as a row in a spreadsheet:
71+
72+
73+
.. csv-table::
74+
:file: _static/example-claim-as-row.csv
75+
:header-rows: 1
76+
:delim: tab
77+
78+
79+
And here’s how the raw data looks in a database tool:
80+
81+
.. code::
82+
83+
{:range-imprecise/first 1346457600000,
84+
:entity/updated-at 1695045627318,
85+
:meta/sheet-name :persons,
86+
:range/starting? true,
87+
:meta/extracted-by :sfm.data.formats.sheet.v1x/cluster:person:posting,
88+
:entity/short-link "4c9cbf32",
89+
:meta/status "3",
90+
:meta/researcher "TW",
91+
:entity/name "claim-4c9cbf32",
92+
:claim/citation:ids [#uuid "9f01b1c1-563f-4b40-a534-b91c7e1a5062"],
93+
:assertion/posting:unit:id
94+
#uuid "dfe9a709-1a80-4bce-8040-68c6502b4f3e",
95+
:entity/type :claim,
96+
:entity/id #uuid "4c9cbf32-6de6-517b-8e44-e308fd27ad4c",
97+
:claim/citation:refs [{:db/id 17592186130203}],
98+
:assertion/posting:person:id
99+
#uuid "bcce8f1d-8336-466c-be8e-c6074f96cde4",
100+
:assertion/posting:rank "Brigadier General",
101+
:range-imprecise/last 1348963200000,
102+
:meta/latest-row-number 114,
103+
:entity/spec :sfm.data.formats.records.claims.v1/claim,
104+
:db/id 17592186095955,
105+
:assertion/posting:role "Commander",
106+
:claim/type :sfm.data.formats.records.claims.v1/posting,
107+
:claim/about-entity:id #uuid "09a8dc6f-8f69-49cd-87f0-1eb996fb25db",
108+
:entity/created-at 1695045627318,
109+
:meta/spreadsheet-id "1PB3JNxpeCPlSy0GsJnElSiEPedfTzZuXk3AFHvrR58Y",
110+
:range/starting-context "Appointed"}
111+
112+
113+
The claim-based approach favors types of research - like that of Security Force Monitor - that involve the construct of a dataset from a wide range of different sources. In practice, this type of research means pulling data from thousands of different sources. The claim system keeps every single piece of data together with a citation of the specific source that evidence it, providing complete evidential transparency. It gives a two-way view showing all the sources that we have used to make a record about a specific person or unit, and also all the bits of data we have taken from specific sources (and exactly where in that source). It also affords us a fine degree of control over which specific pieces of data are used in any analysis. For example, we can exclude or include specific data points that have only official sources, or are only pulled from specific publications.
114+
115+
After creation, a claim is then aggregated with others into a record about a person, unit or other entity in the data model. In the present example, the data would be pulled together with other data about the person called “Aung Soe” - this could be other names that the person has used, units they were posted to, or incidents they have been involved in. These “aggregates” are then used in a wider analysis of the organization structure, history of commanders of a unit, and - perhaps most importantly - the construction of a command chain.
116+
117+
The most useful things to read next are:
118+
119+
- How are claims aggregated into records?
120+
- :ref:`Claims with dates`: an article explaining the basics of how Security Force Monitor constructs dates and timelines
121+
- What are the rules for entering specific types of data?
122+
- How do Locations work in Security Force Monitor’s data?

0 commit comments

Comments
 (0)