I'm not sure this is an issue, but I wanted to raise it for agreement.
Apparently crossref really requires surnames on authors, even though they know they are culturally inappropriate in some cases. They depend upon it for matching bibliographic references with machine learning.
We already have support for this in iacrcc.cls with the surname option on \addauthor, but if an author omits this we have two choices:
use the python post processing with nameparser.HumanName to extract a surname and supply that to crossref. This mostly works for western names, and will even recognize von Neumann as a surname. By showing it to authors in the server, we can
in the event that the parser fails, we can simply take the last token from the name and supply that.
I don't think we need to make surname a required option on \addauthor because that's just following the cultural insensitivity of crossref.
I'm not sure this is an issue, but I wanted to raise it for agreement.
Apparently crossref really requires surnames on authors, even though they know they are culturally inappropriate in some cases. They depend upon it for matching bibliographic references with machine learning.
We already have support for this in
iacrcc.cls
with thesurname
option on\addauthor
, but if an author omits this we have two choices:nameparser.HumanName
to extract a surname and supply that to crossref. This mostly works for western names, and will even recognizevon Neumann
as a surname. By showing it to authors in the server, we canI don't think we need to make
surname
a required option on\addauthor
because that's just following the cultural insensitivity of crossref.