Pedigree CRUD

[robinandeer]

Är det inte bäst att dela upp pedigree-filen i en del som är allmän för familjen samt att man lägger till en person i taget?

This is where we would put general information. Like analysis status. GET /families - list all families GET /families/ - get family by ID POST /families - create a new family PUT /families/ - Update a family DELETE /families/ - Delete a family

Fields: id, started_at, finished_at, sanger_at, confirmed_at (dates) + pedigree stuff The clinicians have to decide if they want to track multiple Sanger orders or just the latest etc. Also how this is connected to the family log comments. They should almost always update the same time.

Updating the pedigree file. Update by individual member or all at once? GET /families//members - list all family members GET /families//members/ - get family member by ID POST /families//members - create a new family member PUT /families//members/ - Update a family member DELETE /families//members/ - Delete a family member

Fields: family_id/fdn [foreign key, new], idn, sample_id etc.

[MatsDahlberg]

I don't think you will be able to POST to 'create' a new family. A new family will always be created by importing a new data set into the database.

I will come back with questions if there are any.

[MatsDahlberg]

You have sanger_at and confirmed_at in the fields list.

They don't belong here do they? I think those should be on variants and not on the family?

[robinandeer]

Sure, that would be a better idea.