The breeding business can be recorded by individuals or groups, and different objects have different management methods. Splitting and merging batches will also change the current relationship. The system should retain the source, quantity and time to avoid being unable to review the original batch after just changing the name.
Management granularity
Different businesses may be managed by individuals, pens or batches, and the system model should be determined based on on-site practices. It cannot be assumed that each object has independent identification information, nor can individual events that need to be tracked be written only in batch notes.
Change records
Transfers, quantity changes and stage adjustments should form event records, indicating the time of occurrence and associated batches. The current quantity is the summary result, and the historical changes are the basis for verification. Both need to be retained.
Information Purpose
Records are used to organize feeding and service processes, and the system should not automatically make diagnosis, treatment or medication decisions. When professional matters are involved, business records and handling instructions confirmed by the appropriate personnel should be retained.
Scenario verification
For example, after two batches are merged and managed, the source and merger time of the new batch should be able to be queried, and the historical matters of the old batch can still be queried. Batch changes are business events and need to be recorded based on rather than just modifying the name.
Specific verification method
Query the source and occurrence time after merging two batches; check the new batch quantity and the remaining quantity of the original batch when splitting; the original batch items can continue to be checked; submit the same split operation again to confirm that there will be no repeated deductions, and abnormal quantities cannot be written without prompts.
Batch changes are saved as business events, which can not only display the current management structure, but also restore the relationship before splitting and merging. Individual information needs to clarify whether it follows batch changes and its applicable scope.
