cortex-lab / cortex-lab/alyx

Enhancements: more editing abilities and calendar reminder system

Open
#647 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
52
Forks
12
Avg merge
1d 11h
Merged PRs (30d)
4

Description

My user has the following questions/requests:

  1. The only blank field in these records is the end date, however, I cannot edit this. I only have the option to delete the breeding pair, which I do not want to do. Is there a way to mark crosses as inactive?

  2. I also want the ability to edit the litter information, as I will not know the genotyping information until 1-3 weeks after the litter is born.

  3. Are there plans to add a calendar/reminder system to Alyx? I have listed some reminders related to Breeding Pairs/ Litters that would be particularly helpful for me:
    3a) Remove father reminder (yes/no) If yes, set reminder to 14 days after animals are crossed.

3b) Mating confirmation (optional field, date format). Here the researcher will note the date that a plug is detected in the female if that information is relevant.

3c) Experimental reminder (yes/no). If yes, add fields for reminder date and short description. (For instance, if a mother must be injected IP with BrdU or tamoxifen for developmental studies).

3d) Check for litter (automatic, 21 days after initial cross date)
Birthdate Confirmation (yes/no). Sometimes the birthdate is approximate, but for developmental studies it is important to confirm whether the birthdate is exact.

3e) Collect genotyping sample (Optional, yes/no). If yes, add fields for sample collection age (for instance, a number can be entered "7" and that will automatically set a reminder to collect genotyping samples 7 days after the litter is born.

3f) Wean litter (automatic, 21 days after litter is born)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. First narrow the many editing and reminder requests into a defined scope, then identify the relevant breeding-pair and litter models and interfaces; done should include agreed behavior for each selected request.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
backend, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.