recurring: Unexpected Data Format during capturing Instagram Data

[bodilvreugdenhil]

Hi!

It seems as though this exact problem has come up again:

https://github.com/digitalmethodsinitiative/zeeschuimer/issues/27

I experienced the same error as this user when trying to capture data from Instagram. I did make sure that 4CAT and Zeeschuimer were completely up to date. Perhaps Instagram changed their data structure again recently.

Thanks in advance!

[dale-wahl]

Could you check the dataset log in 4CAT. Is the error the same as in this part: Unable to map item: KeyError-'full_name'? Or are you receiving the unexpected data format warning for a different key name?

[bodilvreugdenhil]

Yes, it is exactly that error. Unable to map item: KeyError-'full_name'

[dale-wahl]

Ah, the fix did not make the 1.40 release, but is available in the master version of 4CAT (https://github.com/digitalmethodsinitiative/4cat/commit/fa3be93bafef17e95881207604efa1212d562d9e).

You can use the “latest” Docker tag in the .env file to use the most current version of 4cat which I checked and includes the above fix. After updating 4cat, the status message of the Dataset will not update (unless you re-import the data), but all processors will use the author_fullname field appropriately.