# 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:** 16

<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 17, 2023, 6:17pm UTC](https://farmos.discourse.group/t/termination-events/1476/16 "2023-01-17T18:17:13Z")

</div>

> [@gbathree](#):
>
> Do you think we could have a standard ‘termination’ log which at the core works for animals or plants, but then has categories (similar to `land type` maybe).

Sure could! I would probably recommend starting that in a custom module to experiment with it… as a short-term solution at least. In the same way that @Farmer-Ed created his own “Animal Death” log type. OR: use the existing `harvest` / `activity` log types and just follow your own convention of creating a log with the same timestamp as the `archived` timestamp (via API) and matching them up that way.

It feels like ultimately we should aim for the “asset properties tracked via logs” feature described above (formerly/improperly referred to by me as “traits” 🙂) as the long-term solution. I feel like the _log type_ shouldn’t be the only determining factor for defining “asset lifespan”. It feels artificially constraining - and adds the burden of creating multiple records to signify a single event (eg: 1 `harvest` log + 1 `termination` log). It seems like it would be more elegant to allow _any_ log type to be used to set an asset’s “termination date” property.

Ultimately what we’re talking about here is how to represent termination date in a convention. That convention can change over time, as the features available to us change. So maybe the short term solution is to create a simple convention using the existing types/fields, and plan ahead to migrating that to use the new dynamic asset properties feature when it’s available.

Related: [Documenting conventions](https://farmos.discourse.group/t/documenting-conventions/1263)

---

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