Hello Team,
I am facing an issue from 8 August 2025. In this issue the content which are registered by DOI are not showing in ResearchGate / Semantic Scholar.
Please can you confirm me the reason behind this. I am worry about it.
Thanks
Hi Rahul,
This is likely due to some issues we’ve had getting new content indexed in our REST API over the past few weeks. Our technical team is aware of the problem and working on getting everything re-pushed for indexing now. You can follow updates on that issue on our status page - Crossref Status - Some indexing of metadata failing at the REST API (starting 8 July and continuing today)
1 Like
Hello Shayn,
Thanks for your positive reply.
Please still, my articles are not showing in the ReserachGate / Semantic Scholar. Can i know estimated time for this ?
Thanks
1 Like
Hello @rahul ,
Our technical team is actively working on a fix. Repairing this indexing bug is our technical team’s highest priority at the moment. Can you provide us with a couple of example DOIs so we can investigate further?
-Isaac
Hello Ifarley,
I am attaching a single DOI. Zero trust network access enforcement for securing multislice architectures in 5g private enterprise deployments| International Journal of Innovative Science and Research Technology
Like this i have lots of DOI which are not indexed with Semantic Scholar / ResearchGate. From 8 August 2025 my all designed DOI are not getting indexed there.
Thanks
Thank you @rahul . As you may know, there are normal lags in our indexing processes. When we are free of bugs in our system/processes, our own internal indexing process can take 24 hours to run. That is, it can take our system 24 hours to index new registrations from the time of submission processing completion (where we verify and register the input XML) to where we completely index that DOI and record (convert the input XML to JSON). From there, third-parties, like Semantic Scholar / ResearchGate, can retrieve the metadata in our APIs, but they may have lags in their systems and processes as well.
What I can tell you is that DOI 10.38124/ijisrt/25aug323 was successfully registered with us on 2025-August-08 at 12:18:59 UTC. But, when our system went to index that work in our REST API (convert it from XML to JSON), the process failed. That process has been failing for a fraction of records registered with us since 8 July when we migrated our data center to the cloud. And, it is continuing to fail for a small percentage of registrations each day. We’re working on fixing that and will be manually re-pushing records to our API a couple of times per week until we fix the bug.
Our technical team manually re-pushed DOI 10.38124/ijisrt/25aug323 and nearly 1.4 million other records registered between 3 and 14 August on 14 and 15 August. DOI 10.38124/ijisrt/25aug323 is now present in all of our APIs. Here it is in our REST API: https://api.crossref.org/works/10.38124/ijisrt/25aug323
You can see it was indexed on 15 August. You can also confirm that DOIs and their full records are in our system by using our search interface at search.crossref.org, like this: Crossref Metadata Search
At this stage, all third-party systems should be able to retrieve and use the metadata associated with DOI 10.38124/ijisrt/25aug323.
Apologies for the delay,
Isaac
1 Like