-
Notifications
You must be signed in to change notification settings - Fork 297
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Updated list of volunteers, removed very old sponsors * Removed defunct front page link to submit presentations (closes #1401) * Changed ingestion instructions to point to a Github issue * Updated link to copyright PDF * Updated Anthology ID information * Reorganized some blog-style links under `posts/` * Minor corrections to install documentation
- Loading branch information
Showing
14 changed files
with
103 additions
and
114 deletions.
There are no files selected for viewing
This file contains 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 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 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 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 |
|---|---|---|
|
|
@@ -7,4 +7,4 @@ We welcome your contributions! | |
| In fact, since the Anthology is run entirely on volunteer energy, we need them. | ||
| The best way to contribute is to browse our [Github issues](https://github.com/acl-org/acl-anthology/issues) page (we suggest starting with the ["help wanted"](https://github.com/acl-org/acl-anthology/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) tag, and see what needs to be done that overlaps with your interests or skills. | ||
| Please also feel free to email the director, [email protected]. | ||
| You might also be interested in our [call for volunteers]({{< relref "/info/volunteer.md" >}}). | ||
| You might also be interested in our [developer documentation]({{< relref "/info/development.md" >}}). | ||
This file contains 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 |
|---|---|---|
|
|
@@ -2,14 +2,16 @@ | |
| Title: Information for Submitters | ||
| linktitle: Submitting | ||
| subtitle: General information on submitting proceedings to the ACL Anthology (for event chairs) | ||
| date: "2020-10-30" | ||
| date: "2021-04-18" | ||
| --- | ||
|
|
||
| This page contains general information about submitting the proceedings of a conference to the ACL Anthology. | ||
| (For information about the complete conference management process, particularly for ACL conference publications chairs, please refer to [the official documentation](https://acl-org.github.io/ACLPUB/).) | ||
| It is intended for publication chairs of main conferences and standalone events, who have the responsibility of delivering the proceedings for all main conference and workshop volumes to the Anthology director. | ||
| Chairs of workshops attached to a larger conference should also read this page, but should work through their main conference publication chair instead of directly with the Anthology. | ||
|
|
||
| Please note that chairs of workshops colocated with a larger conference should work through their conference publication chair instead of directly with the Anthology. | ||
|
|
||
| ### Overview of the Submission Process | ||
|
|
||
| Please note the following important dates. | ||
|
|
@@ -45,44 +47,50 @@ Please note the following important dates. | |
| </tbody> | ||
| </table> | ||
|
|
||
|
|
||
|
|
||
|
|
||
| ### Register your meeting | ||
|
|
||
| If you are a conference publications chair, you must register your intention to submit your proceedings. | ||
| This step requires you to send (a) the complete list of volumes that will be published in the Anthology (main conference volumes and workshops) and (b) the desired publication date. | ||
| This information should be assembled in a spreadsheet and then commmunicated to [the Anthology Director](mailto:[email protected]) in a single email. | ||
| Please do this as early as possible, ideally well before the submission deadline. | ||
| An template for this spreadsheet [can be found here](https://docs.google.com/spreadsheets/d/13F1XhnT4PsiN-ZXcpv6QUp5A2qlr6-W9MoDgCkBOw9w/edit#gid=0). | ||
| Your proceedings will be due no later than **two weeks** prior to this negotiated date. | ||
|
|
||
| This information should be submitted to us [via a Github issue](https://github.com/acl-org/acl-anthology/issues/new?assignees=mjpost&labels=ingestion&template=ingestion-request.md&title=Ingestion+request) | ||
| **Please do this as early as possible**, ideally well before the submission deadline. | ||
| This will allow us to do a quick sanity check of the metadata. | ||
| As noted above, if you are the chair of a workshop that is colocated with a larger event, please work with your main conference publication chair instead of directly with the Anthology. | ||
|
|
||
| The following information in the spreadsheet is especially important: | ||
| Your Github issue should contain the following information for each volume. | ||
|
|
||
| - **Venue identifiers**. Each venue (conference or workshop) has a venue identifier. | ||
| - **Venue identifier**. Each venue (conference or workshop) has a [venue identifier]({{< relref "ids.md" >}}). | ||
| Its basic form is the conference acronym, such as ACL, NAACL, JEP/TALN/RECITAL, and so on. | ||
| A [slugified](https://en.wikipedia.org/wiki/Clean_URL#Slug) version of this acronym, containing only numerals and lowercase ASCII letters, is used in the URL for the venue's page on the Anthology (e.g., [ACL → acl](https://aclanthology.org/venues/acl), [JEP/TALN/RECITAL → jeptalnrecital](https://aclanthology.org/venues/jeptalnrecital)), and also forms a component of the [Anthology ID]({{< relref "ids.md" >}}). | ||
| For existing venues, be sure to look up [the venue's existing identifier](https://aclanthology.org/venues/). | ||
| New venues must have their venue identifier confirmed by the Anthology director. | ||
| Note: a common mistake is to include the year in the venue identifier, e.g., ACL2020 (perhaps in part because Softconf often uses this). | ||
| New venues must have their venue identifier confirmed by the Anthology director (see subsection below). | ||
| Note: a common mistake is to include the year in the venue identifier, e.g., ACL2020. | ||
| This confuses a *meeting* of a venue with the venue itself. | ||
| The identifier should not have the year or meeting number in it. | ||
| - **Venue name**. Each venue has a name. | ||
| These names are attached to the venue identifier and stored in [our database](https://github.com/acl-org/acl-anthology/blob/master/data/yaml/venues.yaml). | ||
| If your venue is new, please enter the venue name. | ||
| Note: similar to the caveat about about the venue identifier, this is the name of the venue, not a particular meeting of the venue. | ||
| When submitting a new venue to the Anthology, please make sure *not* to put the year or meeting number in the venue name. | ||
| - **Volume titles**. These are the titles of the volumes that will be published, e.g., *Proceedings of the...*. | ||
| - **Volume title**. This is the title of the volume book that will be published, e.g., *Proceedings of the...*. | ||
| We recommend you choose a name consistent with your prior years' volumes. | ||
| The full titles should not contain abbreviations, except parenthetically. | ||
| The full title should not contain abbreviations, except parenthetically. | ||
| For example, "Proceedings of EMNLP 2019" is not a good title, but "Proceedings of the 2019 Meeting of the Conference on Empirical Methods in Natural Language Processing (EMNLP)" is a great one. | ||
| If you have sub-volumes (e.g., long papers, short papers, demonstrations, tutorial abstracts), we suggest you append them after the full volume name. | ||
| If you have sub-volumes (e.g., long papers, short papers, demonstrations, tutorial abstracts), we suggest you append descriptors after the full volume name. | ||
| For example, "Proceedings of the 2019 Meeting of the Conference on Empirical Methods in Natural Language Processing (EMNLP): Tutorial Abstracts". | ||
| You should also seek consistency with the names of your volumes from prior years. | ||
| You may find [this naming guide](https://docs.google.com/document/d/1-4I8w-ckyy3oF2XMbkjAaq14EOyWSoSUW0dpCTtprm8/edit?usp=sharing) helpful. | ||
| But above all, you should also seek consistency with the names of your volumes from prior years. | ||
|
|
||
| If you are chairing a meeting attached as a satellite of a main conference (e.g., ACL or EMNLP), please work with the main conference publication chair, rather than directly with the Anthology staff. | ||
|
|
||
| #### New venues | ||
|
|
||
| If your venue is appearing for the first time in the Anthology, we need to assign it a venue identifier, as described above. | ||
| You can choose one yourself, but it will require confirmation from the Anthology director. | ||
| If you are submitting a new venue, please be sure to also include the following information: | ||
|
|
||
| By default, the publication of papers associated with an event in the Anthology will be on the first day of the event (inclusive of workshops or tutorials). | ||
| If you prefer to have it published on a different date, please inform us when you register. | ||
| - **Venue name**. Each venue has a name. | ||
| These names are attached to the venue identifier and stored in [our database](https://github.com/acl-org/acl-anthology/blob/master/data/yaml/venues.yaml). | ||
| If your venue is new, please enter the venue name. | ||
| Note: similar to the caveat about about the venue identifier, this is the name of the venue, not a particular meeting of the venue. | ||
| When submitting a new venue to the Anthology, please make sure *not* to put the year or meeting number in the venue name. | ||
| - **Website**. The website of the venue. | ||
| Ideally this is a website of the venue itself (e.g., [https://naacl.org](https://naacl.org)), and not a particular meeting of the venue. | ||
|
|
||
| ### Submit your data | ||
|
|
||
|
|
@@ -102,7 +110,7 @@ If you are using the START system, this process is handled as part of the camera | |
|
|
||
| Otherwise, for copyright transfers, please use the form at: | ||
|
|
||
| + https://github.com/acl-org/ACLPUB/blob/master/doc/authors/ACL-copyright-form.pdf | ||
| + https://github.com/acl-org/ACLPUB/blob/master/templates/copyright/acl-copyright-transfer-2021.pdf | ||
|
|
||
| Forms should be signed by authors and saved using the ACL Anthology identifiers as names. | ||
| Please place these into a folder (e.g., `copyright-transfers/P11-1001.pdf`) and then deliver them in bulk to the Anthology Editor when submitting the proceedings. | ||
|
|
||
This file contains 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 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.