# Termination events

**URL:** <https://farmos.discourse.group/t/termination-events/1476>\
**Category:** Development\
**Created:** [January 16, 2023, 2:36pm UTC](https://farmos.discourse.group/t/termination-events/1476 "2023-01-16T14:36:40Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [January 16, 2023, 4:56pm UTC](https://farmos.discourse.group/t/termination-events/1476/4 "2023-01-16T16:56:48Z")

</div>

Here are some other threads on this topic:

- [https://www.drupal.org/project/farm/issues/2630218](https://www.drupal.org/project/farm/issues/2630218)
- [https://www.drupal.org/project/farm/issues/2401525](https://www.drupal.org/project/farm/issues/2401525)
- [Log Type request: Death · Issue #197 · farmOS/farmOS · GitHub](https://github.com/farmOS/farmOS/issues/197)
- [Loss of Product Event](https://farmos.discourse.group/t/loss-of-product-event/652)
- [Livestock management workflow (birth / death / sale / ...)](https://farmos.discourse.group/t/livestock-management-workflow-birth-death-sale/800)
- [Animal Management](https://farmos.discourse.group/t/animal-management/192)

In almost all of those, I point back to the top one as the “canonical” idea for solving it: [https://www.drupal.org/project/farm/issues/2630218](https://www.drupal.org/project/farm/issues/2630218)

> Add a concept of “lifespan” to assets, similar to “location”, “group membership”, etc - and allow it to be tracked via logs. So one log can define the start of an asset’s life, and one can define the end.

---

_[View the full topic](https://farmos.discourse.group/t/termination-events/1476)._