Consider support for exporting data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 1
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 142
Description
We've had many requests to add an "export as csv" button for data. I'm quite hesitant about this because of the reproducibility story; only having the data and no provenance from where it came from is concerning to me.
My first thought when I read this feedback is usually "what do you want to do with that data? What's your reaction to doing that in commons instead?" That's likely not workable long-term. One option is to export a project directory with a source script and a README in addition to the csv, maybe with a share link to the conversation in the README.
I do think this will all get easier once Artifacts (#71) and Conversation Sharing is implemented, too. If it's mostly about "I want to share this with someone", then implementing that first should help.
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
No implementation files or tests are named. Start by reviewing Artifacts (#71) and Conversation Sharing, then clarify whether export should provide only CSV data or a project directory with source, README, and conversation link. Done requires an agreed export design that preserves data provenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100