Skip to content
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

tracking annotation/reviewing progress #36

Open
bwaldon opened this issue Aug 14, 2024 · 1 comment
Open

tracking annotation/reviewing progress #36

bwaldon opened this issue Aug 14, 2024 · 1 comment

Comments

@bwaldon
Copy link
Collaborator

bwaldon commented Aug 14, 2024

I'm currently using a Google Sheet to track annotations (e.g., has a stub been created, has an annotator been assigned, has a PR been opened, has the tree been added to the main branch, etc.). It won't be super easy to keep that sheet in sync with the repo: one has to manually compare it against the list of open/closed PRs and the list of dataset files.

Idea 1: restructure the repo: one subdir. for in-progress trees, one subdir. for completed trees. Would make it easier to keep track of things, but then files will have to be moved between subdirectories when they've been approved. (Can you even do this on GitHub? There's git mv in the command line, but one of the virtues of the current workflow is that everything post-annotation is happening in the GitHub web interface).

Idea 2: github action w/ Google Sheets API call. fancy, and less manual work for project admins, but could be more trouble than it's worth.

@nschneid
Copy link
Contributor

I think a spreadsheet is going to be helpful regardless of how the repo is structured.

Can stub creation and annotator assignment happen at the same time? You could update the spreadsheet twice for each sentence: once when created/assigned and once after merging the PR. And then just monitor PRs to see which ones are ready for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants