Datasets:

sil-ai

/

bloom-vist

like 3

Well let's just say that this has been a real mess. aba078ab6ee8373d3c08b04b90555ff65f1f1f18 is the last version that "worked".

Weird stuff going on with duplicates.

jq .stories data/bloom_vist_june15_deduped_june21_langfiltered_june22_with_storylets_licenseupdated.json|grep --context=6 266a9fcf-4e32-4c4b-aae2-b04bc39a29e9

There are 33 images with this album ID in the latest JSON.
There are 22 annotations with this album ID
There are 2 stories with this album ID
The album itself claims to have 11 photos
searching the duplicate_ids_list shows
"266a9fcf-4e32-4c4b-aae2-b04bc39a29e9": [
"49287e44-4ed1-4edb-a543-2245550c9173",
"2047903f-49b6-4a8a-8aed-2e776313b0e6"
],

Is this a problem that can be fixed in parsing, or do we need to go back upstream in the pipeline?

jq .albums data/bloom_vist_june15.json|grep --context=6 266a9fcf-4e32-4c4b-aae2-b04bc39a29e9 
      }
    }
  },
  {
    "title": "Зёрнышко  История Вангари Маатай",
    "photos": "11",
    "id": "266a9fcf-4e32-4c4b-aae2-b04bc39a29e9",
    "license": "cc-by",
    "metadata_from_original_json": {

$ jq .annotations data/bloom_vist_june15.json|grep --context=6 266a9fcf-4e32-4c4b-aae2-b04bc39a29e9 |grep story_id|sort|uniq
      "story_id": "dbcc37ad-14bd-44dc-af55-06a5c8e65367",
      "story_id": "ec408574-e4f1-4e69-a94d-168aeb38ae41",

In data/bloom_vist_june15.json we see just one album with this id.
We do in fact see two sets of 11 annotations with this ID. story IDs are dbcc37ad-14bd-44dc-af55-06a5c8e65367 with 11 annotations in en and ec408574-e4f1-4e69-a94d-168aeb38ae41 with 11 annotations in ru.
We see exactly 11 images with this album ID. One of them is "Зёрнышко История Вангари Маатай/ASP_151_A_Tiny_Seed_The_Story_of_Wangari_Maathai_Page_13_Image_0001.png"

How did we go from

• images: 11
• annotations: two stories each with 11 annotations.
• stories: 2 unique IDs

To

• images: 33
• annotations: 22
• stories: still 2?