Vanderbot does not find some image names in the data sent back from the API

[baskaufs]

In these cases, the record was successfully written to the API and the rest of the metadata (except for the associated references) is written to the CSV file. However, if the CSV is used to write again, duplicate claims will be made since the UUIDs and hashes aren't recorded in the table. So they have to be manually copied out of the returned JSON and pasted into the CSV.

Q111821575
transformed image URL:
http://commons.wikimedia.org/wiki/Special:FilePath/%22Accusing%20Finger%20of%20Conscience...God%20and%20Conscience%20Witness%20Every%20Action...The%20Authorities%20Ask%20That%20You%20Save%20Fats...Reli%20-%20NARA%20-%20512560.jpg
API value:
Accusing Finger of Conscience...God and Conscience Witness Every Action...The Authorities Ask That You Save Fats...Reli - NARA - 512560.jpg

Q111821677
transformed image URL:
http://commons.wikimedia.org/wiki/Special:FilePath/Henry%20Dunant%20apocalypse%20diagram%20.JPG
API value:
Henry Dunant apocalypse diagram.JPG

In this case it looks like the API stripped off a trailing space before the file extension.

Q111822239
transformed image URL:
http://commons.wikimedia.org/wiki/Special:FilePath/Simon%20Bening%20%28Flemish%20-%20Villagers%20on%20Their%20Way%20to%20Church%20-%20Google%20Art%20Project.jpg
API value:
Simon Bening - Villagers on Their Way to Church - Google Art Project.jpg

[baskaufs]

In the case of Q111842021, the name was changed from Coffeepalestine.jpg to Palestinian women grinding coffee beans.jpg, I guess through a redirect. So the API response had a different image URL for P18 than what was sent. This seems to be an uncommon edge case, but at least it should be noted in the error log.

Actually, this isn't such an edge case; it happened like 5 times out of 600 items uploaded.