search

codeforIATI / iati-data-bugtracker

🐛 A public log of issues with IATI data and metadata
https://bugtracker.codeforiati.org
3 stars 0 forks source link

[BUG] United Nations Office for Project Services (UNOPS) 404 status code response #12

Closed notshi closed 2 years ago

notshi commented 3 years ago

Explanation of the bug

Since 27 February 2021, UNOPS servers hosting IATI data have been responding with a 404 status code.

As per the d-portal example below, this url returns an error https://iati-content.unops.org/data/iati/20210226/iati-activities/iati_activity_KR.xml

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
</Error>

However, if you look at the root directory, there are a bunch of urls that are similar but the date is different.

If you then change the date in the url, there is now IATI xml https://iati-content.unops.org/data/iati/20190712/iati-activities/iati_activity_KR.xml

URLs / screenshots

http://d-portal.org/ctrack.html?#view=dash_sluglog&slug=unops-kr Screenshot-20210301212054-784x182

https://iatiregistry.org/publisher/unops Screenshot-20210301211236-725x398

Does the publisher know?

Have you contacted the publisher, and/or IATI Support?

Yes, I have contacted them via their IATI Registry contact and also IATI Support email.

notshi commented 3 years ago

Am currently in contact with UNOPS and they are getting fixes online. Majority of the files are no longer getting 404 errors apart from just these 2 datasets.

andylolz commented 3 years ago

Yes! I spotted that earlier, in the IATI data dump error diff. That’s great news!

Btw thanks for looping back and updating the issue here! I think we should set up a reminder bot, to encourage issue creators on this repo to routinely check back and see if the problem has been resolved.

andylolz commented 3 years ago

apart from just these 2 datasets.

It’s a revelation to me that error messages get indexed by registry search! That’s an amazing easter egg.

notshi commented 3 years ago

Honestly, I didn't think it was going to work so was surprised it did :}

notshi commented 3 years ago

UNOPS was recently (270421) nudged by the tech team about the remaining errors but have yet to respond.

notshi commented 3 years ago

Looks like 1 of the two files have been fixed. https://iatiregistry.org/dataset/unops-multi is still getting 404.

notshi commented 3 years ago

It seems that IATI Support closed the issue before it was solved (unsure why) so I have requested a follow up with a screenshot of the file above getting a 404 error. Screenshot-20210521142633-727x256

codeforIATIbot commented 3 years ago

Hello! There has been no activity on this issue in the last 30 days. I wonder if it has now been resolved?

If you’re reading this, would you mind checking to see if the issue is still applicable?

Thank you!

markbrough commented 3 years ago

There's still an issue, the above linked file is now showing a certificates warning and an access denied message

notshi commented 3 years ago

Have nudged the UNOPS contact and IATI support again. Hopefully something comes through.

notshi commented 3 years ago

Have nudged UNOPS again earlier and they have responded that they are in the midst of fixing this as well as a duplicate identifier issue (unrelated to this thread). However, it is leave season so will take a while.

Will update back when something happens.

notshi commented 2 years ago

Have yet to get a response from the publisher so have nudged them again.

notshi commented 2 years ago

Publisher has responded that they are still waiting on an update from their technical colleague.

codeforIATIbot commented 2 years ago

Hello! There has been no activity on this issue in the last 30 days. I wonder if it has now been resolved?

If you’re reading this, would you mind checking to see if the issue is still applicable?

Thank you!

notshi commented 2 years ago

Have nudged the publisher again.

notshi commented 2 years ago

As of 10 minutes ago, they were able to remove the problem dataset from the Registry.

andylolz commented 2 years ago

Oh I see – sounds like there was a registry issue here?

notshi commented 2 years ago

The publisher said it was a url that previously pointed to a file that is now distributed to individual country files so is no longer updated/used but they were waiting for a confirmation from their tech colleague to delete it.

So the delay was the response and confirmation from that colleague for them to action it on the Registry.

andylolz commented 2 years ago

Excellent – thanks for your multiple followups to get this resolved! đŸ™đŸ»