acl-org / acl-org/acl-anthology

Processing attachments (update documentation, have GitHub template for it?)

未关闭
#7,276 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
797
派生
408
平均合并
3 天 19 小时
30 天内合并 PR
36

描述

Decide on a workflow (e.g. GitHub-based) how attachments should be added when asked for and update documentation accordingly. See related open issues on concrete examples illustrating the need.

> those forms were for bulk ingestion of attachments. We should delete the FAQ entry since we no longer use this form. We could also add a new Github-based form (similar to PDF corrections) to allow uploading of attachments.

_Originally posted by @mjpost in [#7272](https://github.com/acl-org/acl-anthology/issues/7272#issuecomment-3806762956)_

Need to update
- [x] FAQ: https://aclanthology.org/faq/
- [ ] Wiki page: https://github.com/acl-org/acl-anthology/wiki/Processing-attachments-and-corrections

Potentially introduce
- [ ] a new GitHub template
- [ ] a script to handle attachments or update existing script if necessary

Related, still open issues:
- #7272 user would like to add an attachment to their ACL 2025 publication
- #4161 user would like to add an attachment to their (unnamed) ACL 2023 publication, would even offer a PR
- #1773 stating the Microsoft form mentioned in the FAQ is closed
- #493 (this sounds more like bulk ingestions, and it's from 2019)

贡献指南

这个仓库没有索引到贡献指南

调研方向

Start by reading the FAQ entry, the wiki page "Processing attachments and corrections", and the related issues #7272, #4161, #1773, and #493 to understand the attachment cases. The issue asks for a workflow decision before changes, so done means maintainers agree on the GitHub-based process and the FAQ/wiki, template, or script changes match that decision.

由索引模型根据 Issue 内容生成。

评估

技术栈
github, python
领域
documentation, tooling
Issue 类型
文档
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。