# Termination events **URL:** \ **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:** 2
**Author:** ![Symbioquine](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/symbioquine/32/284_2.png) [@Symbioquine](https://farmos.discourse.group/u/Symbioquine)\ **Post date:** [January 16, 2023, 4:32pm UTC](https://farmos.discourse.group/t/termination-events/1476/2 "2023-01-16T16:32:53Z")
Archiving does have a date, but the date just isn’t shown the UI (and can’t be set by the user) at the moment. Obviously, it is also already possible to provide a revision comment as part of the asset update that archives it. So the simplest change might just be to expose the archived date in the UI. More broadly though, I think something like this could be useful when there is additional (structured) data that needs to be associated with the transition of an asset to the archived state. I think @Farmer-Ed has some log types like this for his animals. This also reminds me a bit of what I was alluding to with the “axioms” I wrote out in [this post](https://farmos.discourse.group/t/creating-a-standard-interpretation-layer-on-top-of-core-farmos-schema/533/2). > [@Creating a standard 'interpretation' layer on top of core farmOS schema](https://farmos.discourse.group/t/creating-a-standard-interpretation-layer-on-top-of-core-farmos-schema/533/2): > > - Data-fields of assets ~~and areas~~ are modeled via logs which reference that asset thereby providing both the current value and a history of the values of those data fields. > - The manner in which the logs for an asset ~~or area~~ are combined to determine its current data-fields is defined on a field-by-field basis - i.e. some fields might just take the most recent log value for that field whereas others might be the sum of the log values for that field. i.e. the concept that more fields on assets could (in theory) be generalized to be the result of the associated logs - just like inventory, group membership, and location/geometry are today. I’m a little less sold on that generalization making sense for all fields now (given how much complexity the existing cases already hold and that asset versioning is on by default in farmOS), but perhaps archived date is a special case. --- _[View the full topic](https://farmos.discourse.group/t/termination-events/1476)._