see also backend/src/model/enum/life_cycle.rs to get more information about life cycle

@tschawax can you please create an issue/PR of what exactly needs to be done in the backend? (also for #727 and so on)

Ideally, it would be a PR with utopia syntax (doesn't need to compile, though) but it can also be an issue describing in prose text how the API should be changed.

This issue/PR is for @horenso, so that he can quickly start (without discussions/uncertainty what is needed) once he is finished with Opensesame.

@horenso as discussed, @tschawax said it might be enough that when creating a plant the removal date is automatically set depending on life cycle to implement this feature.

@markus2330 I just saw that table plants has the properties life_cycle as an array. For instance
Acinos arvensis and Acinos rotundifolius both have the set {annual,perennial}.

(select unique_name, life_cycle from plants)

What should happen then? Should I just do:

pseudo code:

if life_cycle.includes(biennial): set remove_date two years after add_date
if life_cycle.includes(annual): set remove_date one year after add_date
else: don't set remove_date

I don't fully understand how a set of life_times makes sense when the comments read:

    #[serde(rename = "annual")]
    #[db_rename = "annual"]
    /// on the map for current year
    Annual,

    #[serde(rename = "biennial")]
    #[db_rename = "biennial"]
    /// on the map for current and next year
    Biennial,

    #[serde(rename = "perennial")]
    #[db_rename = "perennial"]
    /// on the map until removed by user
    Perennial,

There are 275 plants that have two life_cycle entries. In these cases, use the longest provided life_cycle. i.e.:

• if perennial -> no remove date
• if biennial -> set remove date to two years after plant date
• if annual -> set removed date to one year after plant date
• else -> no remove date

e.g. in case of Acinos rotundifolius we use perennial, so it should not have a remove date

Please update the code comments.

Thanks for clarifying! PR is incoming shortly 🚀