# Cited-by Service Question: Citation Not Linking Between Articles

**URL:** https://community.crossref.org/t/cited-by-service-question-citation-not-linking-between-articles/12754
**Category:** Cited-by
**Tags:** cited-by, references, stored\_query, reference-matching, deposit\_support
**Created:** [6 December 2024 14:25 UTC](https://community.crossref.org/t/cited-by-service-question-citation-not-linking-between-articles/12754 "2024-12-06T14:25:31Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ksakai](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ksakai/32/1816_2.png) [@ksakai](https://community.crossref.org/u/ksakai)
#### Post date: [6 December 2024 14:25 UTC](https://community.crossref.org/t/cited-by-service-question-citation-not-linking-between-articles/12754/1 "2024-12-06T14:25:31Z")

</div>

Hello Crossref Support and Community,

I have a question regarding the Cited-by service.

I am responsible for system development at the Japan Link Center (JaLC), which is a Crossref member. We register Crossref DOIs for articles, and each article is included in the Cited-by service.

However, we have encountered an issue (and I apologize if this is a recurring question) where the citation data seems to be incorrect for a particular case.

“Citing” Article A: `10.3130/aija.72.25_4`  
“Cited” Article B: `10.3130/aijt.5.99_1`

Article A includes Article B in its reference list, but when checking the citation data for Article B (e.g., via Cited By Links), the citation count is 0.

We are trying to identify the cause of this discrepancy.

We have come up with the following possible reasons. Could you confirm if one of these is the actual cause, or if there might be a different reason?

- The Cited-by system has not yet processed the data.  
We assume that Crossref processes metadata deposited in the Cited-by system periodically.  
Since the reference metadata for Article A was recently updated, this might simply be a case of the data not yet being processed by the Cited-by system.

- Insufficient metadata in the reference list of Article A.  
The metadata for Article B included in the reference list of Article A is as follows:

- Metadata for Article B is incomplete.  
The metadata for Article B, as retrieved from the Crossref API, is here: [https://api.crossref.org/works/10.3130/aijt.5.99\_1](https://api.crossref.org/works/10.3130/aijt.5.99_1)  
There may be an issue on this side, but the ISSN, issue, and page numbers seem to be correctly deposited.

Our system relies heavily on the Cited-by service, and we want to fully understand how it works to ensure accurate citation data.

We would greatly appreciate your guidance and support in resolving this issue.

Thank you in advance for your assistance!

---

<div class="post-metadata">

### Author: ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)
#### Post date: [6 December 2024 20:58 UTC](https://community.crossref.org/t/cited-by-service-question-citation-not-linking-between-articles/12754/3 "2024-12-06T20:58:21Z")

</div>

Hello @ksakai ,

Thanks for your message. There is a lag between when you register the references of the citing DOI and when we establish the Cited-by connection or count to the cited article in our APIs. For our XML API, that lag is two to three hours. For our REST API, that lag is up to 24 hours.

In your example, we’re looking at days since the registration of the references of the citing DOI to the cited article, so if the connection was successful you would see an increase of the cited-by count to DOI `10.3130/aijt.5.99_1`, which we do not see in the [XML API results](https://doi.crossref.org/search/doi?pid=support@crossref.org&format=unixsd&doi=10.3130%2Faijt.5.99_1):

 ![Screenshot 2024-12-06 at 2.47.24 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/d/d23cc202325cc428016dcf93ab4b7e2981d3a727.png)

You can also determine if a cited-by connection/count has been established is in the submission log when you register the references of the citing article, since we establish those connections/counts at the time of registration, like this. We email this submission log to you, but you can also retrieve it in our admin tool: [https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1658579031](https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1658579031)

 ![Screenshot 2024-12-06 at 2.50.26 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/7/7342d6c54273c39a0a03d31960ee2df70f2620ef.png)

As you can see, we only successfully matched the 9th citation. In this thread, you are asking about the 16th citation. The status of that citation is: `stored_query` meaning we did not successfully match and establish a cited-by connection/count between the two DOIs.

**So, why did we do that?**

I think it is because the metadata of `10.3130/aijt.5.99_1` is not as complete as the metadata in the reference/citation itself. As you predicted in your message, I am going to tell you that if you know what the DOIs is that you are citing, put it in the citation list. If you give us that, and the DOI has been registered, the reference will be resolved (i.e., the cited-by connection/count will be established).

Warm regards,  
Isaac

---

<div class="post-metadata">

### Author: ![ksakai](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ksakai/32/1816_2.png) [@ksakai](https://community.crossref.org/u/ksakai)
#### Post date: [17 December 2024 16:00 UTC](https://community.crossref.org/t/cited-by-service-question-citation-not-linking-between-articles/12754/5 "2024-12-17T16:00:51Z")

</div>

Dear @ifarley ,

Thank you for your detailed explanation and for clarifying the reason behind the issue.  
The information on checking whether a Cited-by connection has been established, including the use of submission logs, was particularly helpful. I have shared this with our technical team.

I now understand that the missing Cited-by connection is due to the incomplete metadata for Article B and the importance of including the DOI in the reference list when it is available.  
We will encourage publishers to include DOIs in the references of their articles whenever possible.

Thank you again for your valuable support and detailed guidance.

Best regards,  
Kohei
