OpenRefine / OpenRefine/openrefine.org
Create OpenRefine Operation Manual
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
This ticket follows this forum thread and focuses on the first playbook named: OpenRefine Operation Manual.
This ticket is currently a placeholder to request feedback. An early draft of the playbook structure is available in this public Google Document (only section 3 OpenRefine Operation Manual). I do not plan to open a PR until the content is more advanced in Google Docs.
I will open separate tickets and PRs for the two other handbooks.
You can provide your feedback on this ticket, in the forum thread, or in the Google Doc as it suits you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with section 3, “OpenRefine Operation Manual,” in the linked Google Document, then review the related forum thread for requested feedback. Done means the playbook content is advanced beyond the draft, feedback has been addressed, and a pull request can be opened; this ticket says that work is not yet ready for a PR.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100