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

500 for query for a DOI #75

Open
yarikoptic opened this issue Dec 18, 2024 · 1 comment
Open

500 for query for a DOI #75

yarikoptic opened this issue Dec 18, 2024 · 1 comment

Comments

@yarikoptic
Copy link

❯ curl --silent https://api.citeas.org/product/https://doi.org/10.34973/vtaw-fm19
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>

@robertoostenveld
Copy link

The DOI URL https://doi.org/10.34973/vtaw-fm19 itself resolves fine to the dataset landing page in our repository at https://data.ru.nl/collections/ru/cls/homed_test_materials_dsc_294. It might be due to the DOI just having been minted: I picked an example from the top of the list, which happens to be published only today (18 Dec 2024) and therefore the metadata might not have propagated yet.

I tried another one from the same Radboud Data Repository https://doi.org/10.34973/fkgz-8d22, and that one works well, see http://citeas.org/cite/10.34973/fkgz-8d22. That one is a few years old. Idem for https://doi.org/10.34973/37n0-yc51.

But https://doi.org/10.34973/s07v-9e02 which is from October 2024 again does not work.

If I try the same datasets in https://datasetsearch.research.google.com, I seem to have the same results, i.e. the old ones are there, but the recent ones not.

I know that the metadata propagation from our repository to "elsewhere" is rather complex and I would not know from the top of my head where things might be stuck. I recall that we mint the DOIs through datacite, but that the metadata takes another path, which first goes to the university specific https://repository.ubn.ru.nl/ repository with all research outputs, and then to a national one, and then somehow through Delft University to datacite...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants