kdkodatajuanmaulana29@gmail.com

evidence · the 2021 column — kodata

Column 2: evidence · the 2021 column

index

Open data, followed all the way down to one person inside it.

Every piece here starts with a public dataset and ends with a story. The numbers can be checked: any figure set in mono opens its own evidence in a column to the right, so you never have to leave the sentence you are reading to find out whether it is true.

open to work

03pieces
271occupations
4,810teenagers
34provinces

work

files

evidence · the 2021 column

Three tests, none of which needs a source outside the file. Indonesian minimum wages are nominally non-decreasing, and in this file no province has a 2020 wage above its 2022 wage — so a 2021 value outside that bracket is not surprising, it is impossible.

test one · which year disagrees with its neighbours

ρ(ump 2020, ump 2022) · the two that skip it
+0.9958
ρ(ump 2020, ump 2021)
+0.6812
ρ(ump 2021, ump 2022)
+0.6723
ρ(ump 2019, ump 2020) · a normal pair, for scale
+0.9944

2020 and 2022 agree almost perfectly with each other while both disagree with 2021. A real year cannot do that: to sit between two years that match, it would have to match them too.

test two and three · which rows, and whose numbers

province20202021 in file2022the value belongs tooff byrow gap
JAMBI2,630,1622,788,8262,698,941GORONTALO 2020exact+24
BENGKULU2,213,6042,460,9962,238,094BANTEN 2020Rp 1+9
KEP. BANGKA BELITUNG3,230,0243,000,8043,264,884KALIMANTAN UTARA 2020exact+15
DKI JAKARTA4,276,3501,765,0004,641,854— matches nothing in the file
JAWA BARAT1,810,3512,630,1621,841,487JAMBI 2020exact-7
DI YOGYAKARTA1,704,6082,215,0001,840,916— matches nothing in the file
BANTEN2,460,9973,230,0232,501,203KEP. BANGKA BELITUNG 2020Rp 1-7
KALIMANTAN BARAT2,399,6991,868,7772,434,328— matches nothing in the file
KALIMANTAN TENGAH2,903,1452,877,4482,922,516KALIMANTAN SELATAN 2020Rp 1+1
KALIMANTAN SELATAN2,877,4492,399,6982,906,473KALIMANTAN BARAT 2020Rp 1-2
KALIMANTAN TIMUR2,981,3792,903,1443,014,497KALIMANTAN TENGAH 2020Rp 1-2
KALIMANTAN UTARA3,000,8042,981,3783,016,738KALIMANTAN TIMUR 2020Rp 1-1
GORONTALO2,788,8264,416,1862,800,580— matches nothing in the file

13 of 34 provinces break the bracket. 9 of them are holding another province’s wage, to within two rupiah.

the obvious explanation, and why it is wrong

A single column that slipped one row is the usual cause of this, and it is the first thing to test. Shifting the whole 2021 column back by one row and re-checking against 2020 makes the agreement worse, not better: +0.2101 against +0.6812 for the file as it stands. The row gaps in the table above are -7, -2, -1, 1, 9, 15, 24 — irregular. This is a scramble, not a shift, and the repair is not available from inside the file.

There is a fingerprint. Several displaced values sit exactly one rupiah from their source, and 2 provinces that otherwise froze their wage are off by exactly one rupiah too (LAMPUNG, SULAWESI TENGGARA). A one-rupiah error is not a typing mistake or a policy decision. It is what a number looks like after a round trip through a floating-point value, which suggests this column reached the file down a different path than the others.

what the year actually was

provinces with a usable 2021 value
21
of those, froze the wage exactly
18

The pandemic freeze. 18 provinces did not move the minimum wage by one rupiah — visible in the file only once the corrupted rows are set aside.

what keeping it would have done

median people per wage, 2021 as published
5.03
its spread (CV), against ~0.22 in every clean year
0.297
its range
2.53 11.33

The median barely moves, which is why this is dangerous: an analysis that reported only medians would have published 2021 without noticing anything at all.