acl-org / acl-org/acl-anthology

Ingestion Request: ROCLING 2026

Open
#8,880 9 comments 0 reactions 1 assignee Claimed by @mjpost View on GitHub
ingestion
Dominant language
Python
Stars
797
Forks
408
Avg merge
3d 19h
Merged PRs (30d)
36

Description

### General information about this request

- [x] I confirm that I have read the [Information for Submitters](https://aclanthology.org/info/contrib/).
- [ ] I am submitting a request for a **new venue** that does not exist in the ACL Anthology yet.

### Venue Identifier

rocling

### ACL SIG(s) sponsoring or endorsing the whole venue

_No response_

### Volume Title

Proceedings of the 38th Conference on Computational Linguistics and Speech Processing (ROCLING 2026)

### Venue Name (only if you are submitting a new venue)

_No response_

### Venue Website (only if you are submitting a new venue)

_No response_

### Date of Publication

2026-11-02

### Location

Hsinchu, Taiwan

### Supporting Information

Dear Anthology Director,

I am Fernando H. Calderon, one of the publication chairs of [ROCLING 2026](https://rocling2026.github.io/NTHU_rocling_2026/)

We would like to register the proceedings of ROCLING 2026 with the ACL Anthology. Please find the required information below:

(a) The complete list of volumes:

Proceedings of the 38th Conference on Computational Linguistics and Speech Processing (ROCLING 2026)

(b) The desired publication date: 02 November 2026 (four days before the conference date)

Sincerely,
Fernando H. Calderon
Publication Chair, ROCLING 2026
[fhcalderon87@gmail.com](mailto:fhcalderon87@gmail.com)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue provides only ingestion metadata (volume title, date, location, identifier) and names no files or tests. Start by finding prior venue/volume ingestion examples and the project’s documented ingestion workflow, then add a ROCLING 2026 record in the same structure. If the repo has a metadata validation or import check, run it after the change. The work is done when the new proceedings entry is present and properly formatted like existing entries.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.