We noticed that a good number of XML deposits contain two license_ref data as part of the crossmark custom_metadata XML, but one usually appears in the api.crossref.org.works API.
Can you take a look to see if the XML deposits contained the appropriate data?
Here are some examples where only one license data appears when two should.
api crossref org/works/10.1103/PhysRevA.111.012619
api crossref org/works/10.1103/PhysRevA.111.013711
api crossref org/works/10.1103/PhysRevA.111.013109
api crossref org/works/10.1103/PhysRevB.111.014311
These were submitted in 2025.
api crossref org/works/10.1103/PhysRevA.107.L040601 showed 1 license and then I regenerated the XML, verified it generated two license data and submitted it. Today I verified that both license information shows as expected.
Wondering if this is a known issue as it seems to come and go as I examine data between 2023 and 2025.
Thanks for all your help.
P.S. Being able to include links would be very useful
The REST API can take up to 24 hours to index after a successful registration. The XML API, because it does not have to convert the input XML to JSON, usually indexes a record in two to three afters after registration.
I see both licenses for DOI 10.1103/6cm6-s6g7 in the XML API. That update may not be indexed by the REST API until tomorrow: