-
Notifications
You must be signed in to change notification settings - Fork 367
New author system UI changes #6824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mjpost
merged 63 commits into
master-new-author-system
from
master-new-author-system-ui
Jan 12, 2026
Merged
Changes from 47 commits
Commits
Show all changes
63 commits
Select commit
Hold shift + click to select a range
e1c9939
Export orcid in hugo data
mjpost 2c68ced
Move ORCID icon
mjpost 1308c3d
Remove ORCID itself
mjpost d650dee
Add question mark for unverified authors
mjpost a95873c
Add verification page stub
mjpost 5307d68
black
mjpost ed41c0d
Ensmallen; use fontawesome for both
mjpost 67f4f8f
Bump fontawesome version 5.7.2 -> 5.11.0
mjpost 50bfb33
Icon sizing
mjpost 07ce0b3
Update checksum
mjpost 54ba165
Use fontawesome kit
mjpost ac57e3b
black
mjpost 2dbb39b
Contra all docs everywhere, you need "fab"
mjpost 2eb7946
Switch back to stylesheet
mjpost c37d7b1
fa-solid -> fas
mjpost 675b6b7
Relativize link and lighten question mark
mjpost 9083f2b
Set opacity for unverified people
mjpost c516654
reference syntax
mjpost b46429a
fontawesome hash
nschneid 57e9cfb
Merge branch 'master-new-author-system' into master-new-author-system-ui
mbollmann 52f6d40
Update bulk metadata form
mjpost e311b02
Merge branch 'master-new-author-system' into master-new-author-system-ui
mbollmann fe2cb90
First pass at documentation
mjpost 4e5fb9b
Add note about name variants
mjpost 589f149
Stub page for names
mjpost bdced7f
Update orcid.md
nschneid d0f9745
Merge pull request #6965 from acl-org/nschneid-orcid-info
mjpost d8ed9ee
black
mjpost 85e6d15
Addressing weird hugo error
mjpost d6012da
names.yml: blank lines
nschneid c7f6db3
orcid.md: date
nschneid 8b59e4c
Rename names.yml to names.md
nschneid bdaa993
Partial commit
mjpost 98782b8
Add "Verifying your account" section"
mjpost 636ea83
single.html: source line break led to space before comma
nschneid a73c095
orcid.md: no space in OpenReview
nschneid da1bb1b
verification.md: no space in OpenReview
nschneid 22223c5
corrections.md: no space in OpenReview
nschneid b6012b6
Add three-way verification display
mjpost 5d54bcd
with -> if
mjpost 7fe19b9
Make icon a light green
mjpost 955ebca
Fiddling with color, size, opacity
mjpost afcd7ca
Handle links to verified & unverified pages separately
mbollmann 70f143f
Merge branch 'master-new-author-system' into master-new-author-system-ui
mbollmann 8506353
Refactor verified check on author page template
mbollmann 900e86e
Refactor and update icon styling
mbollmann 3625997
Spacing: add some daylight between the name and the icon so it doesn'…
nschneid ce7741f
bootstrap class to set icon margin
nschneid d297b22
verification.md: a bit more detail on the icons and what verification…
nschneid 10b99e0
header_navbar.html "GitHub" capitalization
nschneid 5139fe4
verification.md: steps for verifying - we want an ORCID iD regardless…
nschneid c7709ef
orcid.md: OpenReview is one word
nschneid 0fcdc4b
verification.md: fix icons
nschneid abde567
verification.md: rephrase part about unverified page for ambiguous names
nschneid 893ca21
author page template: no checkmark icon for verification, just ORCID …
nschneid 84063f9
No ? for verified accounts
mjpost a2c9fd9
Revert "No ? for verified accounts"
mjpost 3d9bc64
Revert "author page template: no checkmark icon for verification, jus…
mjpost e3d7106
Make question mark green
mjpost 20b83be
Restore paper verification notice in tooltip
mjpost cea36bd
ORCID iD isn't recorded
mjpost 3f312cc
accidental </a>
nschneid d2a8772
for author's full display name, only include script variants if verified
nschneid File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -50,7 +50,7 @@ Please pay careful attention to the following steps. | |
| 1. **Ensure that each name is correct**. We treat the information on the PDF as authoritative; this means that the metadata should reflect exactly what is printed on the PDF. A common situation is that the name recorded in Anthology metadata (e.g., John P. Hancock) will not match what is displayed on the PDF (John Hancock). This needs to be corrected first. Please review your papers and [follow the steps here](#metadata-corrections) to correct any discrepancies. Sometimes, this will resolve the split pages. | ||
| 2. Obtain [an ORCID](https://orcid.org). This is required to help with matching of future papers. | ||
| 3. Fill out [an author page correction](https://github.com/acl-org/acl-anthology/issues/new?template=02-name-correction.yml). A Github issue is our preferred mechanism, but you can also email [the Anthology director](mailto:[email protected]). | ||
| 4. Finally, to avoid issues in the future, ensure that the name you use on papers is properly recorded in your profile in publication management systems such as [Open Review](https://openreview.net), [Softconf](https://softconf.com), [EasyChair](https://easychair.org), and so on. | ||
| 4. Finally, to avoid issues in the future, ensure that the name you use on papers is properly recorded in your profile in publication management systems such as [OpenReview](https://openreview.net), [Softconf](https://softconf.com), [EasyChair](https://easychair.org), and so on. | ||
|
|
||
| Anthology staff will address your issue as quickly as possible. | ||
| An example merged author profile is [Aravand Joshi](https://aclanthology.org/people/aravind-joshi). | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| Title: Names in the ACL Anthology | ||
| linktitle: Names | ||
| subtitle: How the Anthology deals with names | ||
| date: "2025-12-29" | ||
| --- | ||
| _This page is a stub. It should describe how the Anthology deals with names, including the following._ | ||
|
|
||
| - PDF metadata and the formation of name slugs | ||
| - Creating author pages | ||
| - Disambiguating names and merging name variants | ||
| - How papers are matched to authors | ||
|
|
||
| It can and should refer to other documentation spread around, but this could be a piece of central information. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| --- | ||
| Title: ORCID iDs in the ACL Anthology | ||
| linktitle: ORCID iDs | ||
| subtitle: Best practices for ensuring your papers are correctly linked | ||
| date: "2025-12-29" | ||
| --- | ||
|
|
||
| An [ORCID iD](https://orcid.org) is a persistent digital identifier that distinguishes you from other researchers and links your research outputs and activities to your identity. | ||
| When these iDs are present on ingested papers, it removes the ambiguity that sometimes arises with popular names and name variants. | ||
|
|
||
| We urge every author who is actively publishing papers to create an ORCID iD, and to supply this ID to publication systems such as OpenReview.[^1] In creating or editing your ORCID iD profile, please consider the following tips to help match your papers to your Anthology page: | ||
|
|
||
| [^1]: Visit the [edit page link at OpenReview](https://openreview.net/profile/edit) and add your ORCID iD under the "Personal Links" section. | ||
|
|
||
| - **Add name variants**: This is most important. In your ORCID iD profile, you can set your given and family names, your published name, and any name variants you have published under (e.g., with or without middle initials, maiden names, etc.). https://orcid.org/0000-0002-1831-3457 is a good example. Make sure you have at least one Latin variant of your name. This helps the Anthology match your publications even if they are listed under different names. | ||
| - **Make sure your name is visible**: Ensure that your name is set to be visible to everyone in your ORCID iD profile settings. If your name is private, the Anthology may not be able to access it for matching. | ||
| - **Register at least one personal email address**: This can be kept private but ensures permanent access so that you can update your ORCID record in the future. | ||
|
|
||
| In addition, the following information can help us improve matching, should we need to manually disambiguate authors. | ||
|
|
||
| - **Add a few representative publications**: You can add your publications to your ORCID iD profile. This is less important for matching in the Anthology, but it is a good practice to keep your ORCID iD profile complete. Many Anthology papers have DOIs, which simplifies the process. | ||
| - **Add educational history and affiliations**: Adding your educational background and current affiliations can help further distinguish you from other researchers with similar names. It is especially helpful for us to know the institution from which you receive (or expect to receive) your highest degree, since we use this information when disambiguating authors. | ||
|
|
||
| In addition to this, make sure that the name you enter into submission mangagement systems (such as Softconf or Open Review) matches one of the ORCID variants, ideally the published name. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| --- | ||
| Title: Verified authors | ||
| linktitle: Verification | ||
| subtitle: How the ACL Anthology verifies authors | ||
| date: "2025-12-29" | ||
| --- | ||
| Every author appearing on a paper in the Anthology is given an author page. The ACL Anthology distinguishes between verified and unverified authors. | ||
|
|
||
| A _verified_ author is one for whom we have an explicit entry in our names database. | ||
| This can happen either automatically or manually. Entries are created automatically when a paper is ingested with ORCID iD information attached to the papers author(s). We also create entries manually when we intervene to disambiguate authors with similar names or who publish under multiple names. We include a link to the ORCID profile from each verified author's page. | ||
|
|
||
| An _unverified_ author is one for whom we do not have an explicit entry in our names database. Unverified pages have `/unverified/` appended to the URL. These pages are created automatically when a paper is ingested without ORCID iD information attached to the authors. Unverified author pages do not include a link to an ORCID profile, but instead include a question mark icon next to the author's name. | ||
|
|
||
| ### Verifying your account | ||
|
|
||
| 1. Create an ORCID iD and populate it. | ||
|
|
||
| We urge every author to create an [ORCID iD](https://orcid.org), and to supply this ID to publication systems such as OpenReview. The reason is that we use this information at ingestion time to match appers to an author. This is increasingly important as the size of the global scientific community increases, and ambiguous names proliferate. Please see our simple [ORCID iD guide]({{< ref "/info/orcid">}}) for information that will help match your papers to your Anthology page. | ||
|
|
||
| 2. File an issue on Github. | ||
|
|
||
| Navigate to your author page in the Anthology. If you are unverified, the URL will contain `/unverified/`. Click the "Fix author" link at the bottom of the links on the righthand side of the page to create an issue from our template. Provide your ORCID iD along with other relevant information. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m confused about this. When/how are we planning to use name variants recorded on an ORCID profile? This is the first I hear about this, as we have so far only ever talked about using ORCID iDs as they are recorded in the ingestion material. Do we plan to query the ORCID API as part of every ingestion?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understood it to mean, when we manually verify author page requests it helps to see name matches on orcid.org. And we may add screening checks at ingestion time to flag totally wrong ORCIDs: #7055