Further automation for simple verifications

A lot of the author page issues are simply to add an ORCID and degree institution to an existing unverified page, making it verified. I call these simple verification requests. They are identified by ensuring the author page is unverified and that "Verification" is the only checkbox selected in the list of possible changes.

One step that I perform manually for such requests is to check the profile at the supplied OpenReview link and ensure that it has an ORCID link matching the ORCID provided in the form. Occasionally the OpenReview profile lacks an ORCID link, and I respond to the issue requesting that it be added. I also check the preferred name on OpenReview.

It occurs to me that this check could be automated. When the issue is created, it could trigger a GitHub action that calls the OpenReview API to fetch the ORCID information (if present) and preferred name. If the ORCID link is missing, it could respond in the thread to request that it be added. Otherwise it would add a message giving the OpenReview preferred name and stating that Anthology staff will follow up to review the request.

Does this sound worthwhile? I might try vibecoding it in Gemini (don't have access to Claude-Code).

The issue names no files, tests, or existing entry points. First confirm the scope and review how a GitHub Action could identify simple verification requests and query the OpenReview API for ORCID and preferred name; done means it posts the appropriate follow-up message for missing ORCID links or the proposed review notice.

Written by the indexing model from the issue text.