OpenCloning / OpenCloning/OpenCloning_backend
Handling incorrect information from source
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 11
- Avg merge
- 14m
- Merged PRs (30d)
- 5
Description
Hi @manulera!
I wonder what would be the best way to modify a DNA source when it comes with any sort of error. I'll explain:
Let's say I get a plasmid from AddGene, but I discover my aliquot has a point mutation. I could simply edit this in my favorite tool and import the plasmid file to SYC. However, I would be missing key information in my cloning history, since the plasmid is not any plasmid, but one that I got from a specific source/database/repository. Instead of an error in the sequence, it could also be an error in the annotation (e.g. I just found a promoter which was annotated in reverse...).
Do you think it could be possible to allow the user to add changes to the imported source within SYC in a way that could be tracked in the cloning history? How do you see this integrating with the current data model?
Let me know!
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 files, tests, or entry points are named. Start by reviewing the current data model and cloning-history handling, then determine how imported source changes and annotation corrections could be represented and tracked; done means an agreed design with clear history and validation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100