softconf2aclpub: read author ORCIDs from .orc side files#215
Conversation
When converting from ACLPUB format, read the sibling .orc side file for each paper and attach ORCIDs to authors by 1-based index, mirroring the .orc side-loading in the ACL Anthology's bin/ingest.py. ORCIDs land in the lowercase 'orcid' author field expected downstream. No-op when no .orc file is present, so existing workflows are unaffected.
|
Thanks, this looks useful and the no-op behavior when no Before approving, I’d like to clarify two things:
The code itself looks reasonable to me, but I think the expected input layout should be documented so users know how to make use of it. |
|
|
Actually, looking at this code in more detail, it doesn't work the way I expected. I assumed that the conversion happened offline after downloading full, completed proceedings from ACLPUB, but that does not appear to be the case. |
|
Thanks, that makes sense. I’m wondering whether we should avoid making For aclpub2, it seems cleaner to have Would it make more sense to treat |
What
When converting from ACLPUB format,
softconf2aclpub.pynow reads theACLPUB
.orcORCID side files and attaches each author's ORCID to thegenerated
papers.yml.This mirrors the
.orcside-loading the ACL Anthology does inbin/ingest.py.Converting from ACLPUB format isn't necessary (the Anthology can ingest
ACLPUB directly), but some people do it anyway, and previously the
converted
papers.ymldropped author ORCIDs..orcformatACLPUB writes one
.orcfile next to each paper's.bib, with one entryper author (1-based index, matching the paper's author order):
Behavior
value are skipped.
orcidauthor field (the same fieldthe program-committee export and downstream ingestion already use).
cdrom/bib/,bib/,attachments/, and...orcfile is present, soexisting scrape-only workflows are unaffected.
Note for reviewers
The side-file lookup directories / key (Submission ID) are a best-effort
default; happy to adjust the search path or matching key to whatever
location your build places the
.orcfiles in.