Hello @rhiannon-ppl ,
Thanks for your message. There is no limit in the schema on the number of ‘first’ or ‘additional’ authors. While this is an editorial decision, members can signal equal first authorship @boutaleb by including multiple authors as ‘first,’ like in this example: 10.14336/AD.2017.1213
<contributors>
<person_name sequence="first" contributor_role="author">
<given_name>Dimitrios</given_name>
<surname>Cakouros</surname>
</person_name>
<person_name sequence="first" contributor_role="author">
<given_name>Stan</given_name>
<surname>Gronthos</surname>
</person_name>
</contributors>
@rhiannon-ppl I see that in a private message you mentioned that you recently updated the record associated with DOI 10.56367/OAG-051-12579 to include two ‘first’ authors:
<contributors>
<person_name sequence="first" contributor_role="author">
<given_name>Scott D</given_name>
<surname>Pegan</surname>
<affiliation>University of California Riverside</affiliation>
</person_name>
<person_name sequence="first" contributor_role="author">
<given_name>Mohammad M</given_name>
<surname>Sajadi</surname>
<affiliation>University of Maryland School of Medicine</affiliation>
</person_name>
</contributors>
There are indexing lags in our system. After a successful submission - be it a new registration or update - it can take up to 24 hours for those updates to be reflected in our APIs and in search.crossref.org (which is powered by api.crossref.org). I think that was the issue here. I see that the metadata record for this DOI has been updated in our REST API: https://api.crossref.org/works/10.56367/OAG-051-12579
My colleague @pdavis wrote what we call a ‘ticket of the month’ post about this with the various lags in our system a couple of years ago: Ticket of the month - September 2023 - A DOI-namic timeline
Warm regards,
Isaac