AllenInstitute / AllenInstitute/ConnectsCommonConnectivity
Multi-writer data loss in shared scopes (patch-seq associations)
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem: notebooks sharing scope (project_id, dataset_id) silently delete each other's rows — associations shrank 2759 → 520 → 495 across etl_visp_inh_patchseq_01/02/03. Current workaround: inlined read-union-rewrite in the notebooks. Options analysis: planning/multi_writer_scope_design.md.
Fix: resolved by #13 with merge_on (project_id, dataset_id, dataitem_id); remove the inlined workarounds in the same PR. This issue is the user-visible bug record.
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 planning/multi_writer_scope_design.md and the notebooks containing the inlined read-union-rewrite workarounds. Review the resolution in #13 to understand the merge behavior and confirm that shared-scope associations retain each writer's rows; the work is done when the workarounds can be removed without data loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100