Missing license information after XML deposit

Hi Crossref,

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

Hello @mklem ,

First off, I have updated your account here on the forum so you can add links. Sorry about that. I thought you already had those privileges.

As for the license information, you can see what is registered in the XML, by viewing these records in the XML API:

There is only one license in the XML, as you can see from the Crossmark metadata above.

Compare that to DOI 10.1103/PhysRevA.107.L040601

I have reviewed the XML that was sent to us for these DOIs. This XML in the XML API matches what was submitted to us.

Warm regards,
Isaac

Thanks Isaac,

Some what related question. What is the difference between these APIs:
https://api.crossref.org/works/10.1103/6cm6-s6g7
and

This DOI (10.1103/6cm6-s6g7) was submitted today, but https://api.crossref.org/works/10.1103/6cm6-s6g7 shows only 1 license

Properties of states near <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML"> <mml:mrow> <mml:msub> <mml:mi>E</mml:mi> <mml:mi>x</mml:mi> </mml:msub> <mml:mo>=</mml:mo> <mml:mn>6</mml:mn> </mml:mrow> </mml:math> MeV in <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML"> <mml:mmultiscripts> <mml:mi>Ne</mml:mi> <mml:mprescripts /> <mml:none /> <mml:mn>18</mml:mn> </mml:mmultiscripts> </mml:math> through <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML"> <mml:mrow> <mml:mmultiscripts> <mml:mi mathvariant="normal">F</mml:mi> <mml:mprescripts /> <mml:none /> <mml:mn>17</mml:mn> </mml:mmultiscripts> <mml:mo>+</mml:mo> <mml:mi>p</mml:mi> </mml:mrow> </mml:math> scattering shows both licenses

second url is supposed to be
https ://doi.crossref.org/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1103/6cm6-s6g7

(had to put a space it so you can see it).

Hello @mklem ,

https://api.crossref.org/works/10.1103/6cm6-s6g7 is the REST API - results in JSON

https://doi.crossref.org/search/doi?pid=support@crossref.org&format=unixsd&doi=10.1103/6cm6-s6g7 is the XML API - results in XML

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:

Warm regards,
Isaac