Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate where the requests for <dataset>.ttl and <dataset>.n3 are coming from #236

Closed
3 tasks done
adinuca opened this issue May 2, 2018 · 3 comments
Closed
3 tasks done
Assignees
Labels

Comments

@adinuca
Copy link
Contributor

adinuca commented May 2, 2018

Why

There are Papertrail alerts for with errors caused by requests like http://www.resourcedata.org/dataset/4405ee9c-c84c-4f25-a811-f3b7e9094ded.ttl every day. The requests returns 500.

What

  • It is understood who makes these requests
  • It is understood if the request should return another response, like 404 if it is not a valid request
  • further issues are raised for fixing it

Notes

@adinuca adinuca added the Vitamin label May 2, 2018
@adinuca adinuca self-assigned this May 7, 2018
@adinuca
Copy link
Contributor Author

adinuca commented May 7, 2018

Links to https://www.resourcedata.org/dataset.n3 and https://www.resourcedata.org/dataset/.ttl are available on each dataset page. They represent alternative formats/urlsin which the dataset can be accessed..

@adinuca
Copy link
Contributor Author

adinuca commented May 7, 2018

For this specific dataset, the error is generated because Source or API link is in the wrong format.
When the .ttl and .n3 versions of the dataset are requested, an error occurs because ckan cannot serialize the URL in the n3/Turtle format.

@moman822 , @EricSoroos do you know if it is safe to remove the URL for https://www.resourcedata.org/dataset/4405ee9c-c84c-4f25-a811-f3b7e9094ded or to change it from http://Sahara Reporter to http://saharareporters.com/ ?

@adinuca
Copy link
Contributor Author

adinuca commented Jul 2, 2018

This is an issue for multiple datasets. Raised #244 for fixing it.

@adinuca adinuca closed this as completed Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant