Add builtin farm animal activities to automatically manage the status of animals

[fedjo]

In a (cattle) livestock farm, there are many movements of animal, in and out.
In movements are : birth (B) / purchase (P) / loan (or boarding) (L)
Out movements are : death (D) / sale (S) / return of loan (or boarding) (R)

When the in movement is recorded, then the status becomes “valid”. In the opposite, when it’s out, status becomes invalid.
In this way, It could be relevant to have specific module (and appropriate tables in the data model) to manage properly in and out movements.
With this kind of management, it would make possible to edit different kind of reports for a given period of time (sales report, born calves list, active animals list, …)
This is the way that work the herd management software for cattle. Usually data models, there is always a animals table and a movement table

The table/form for the in-movement use these data fields :

National ID | Date (of entry) | Code | Previous holder (previous holding farm number or name of the seller) -- | -- | -- | -- FR 35 1234 5678 | 13/03/2025 | P | FR 35 647 985 FR 56 6541 9999 | 14/03/2025 | L | Cattle trading Martin cie required | required | required | required

Birth is a special in-movement that is automatically generated (in movement table) when a new born animal is created (in animal table)

The application for the out-movement use these data fields :

National ID | Date (of leaving) | Code | Next holder (following holding farm number or name of the buyer) -- | -- | -- | -- FR 35 1234 5555 | 13/03/2025 | S | FR 22 987 654 FR 35 1234 5555 | 14/03/2025 | D | ATM knackery required | required | required | required

An out-movement for Death cause is a special out movement (in movement table) that automatically generates a modification of the animal animal status (to inactive)

Note: Ask SIP2 what other activities are supported on the group level