PyRAT compatibility
Open
Nobody has claimed this yet.
enhancement
feature
usability
- Dominant language
- Python
- Stars
- 52
- Forks
- 12
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 4
Description
Several institutions use PyRAT and it takes a lot of time to maintain both databases as there is significant overlap in the colony management. This is discouraging users from adopting Alyx. A simple management command for syncing the two databases would 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
Start by locating Alyx's colony-management models and existing Django management commands, then determine how PyRAT represents the overlapping data. Define the synchronization scope, field mappings, conflict behavior, and completion checks before implementation; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100