Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event automatically activated by another event activation #296

Open
kazemar opened this issue Aug 17, 2021 · 2 comments
Open

Event automatically activated by another event activation #296

kazemar opened this issue Aug 17, 2021 · 2 comments

Comments

@kazemar
Copy link
Contributor

kazemar commented Aug 17, 2021

Scenario example :
I have 6 sites I want to check when there is a heavy raining alert : rivers, stormwater drainage...

Tool :
I want to create 6 event models (one for each site) that would be activated by an automatic or manual event (flood or heavy rain alert), so I can send my team members to this sites to get a situation report.

See also https://github.com/kalisio/kdk/issues/453 for geographic located event models

@claustres claustres transferred this issue from kalisio/kdk Aug 31, 2021
@claustres
Copy link
Member

Same remark as in #295.

However I think that we should work on a way to easily create a batch of events by eg selecting a layer or features in a map. But this raises potential problems like: what to do if the features are changed after the event has been created ? do you want to send all events to the same participants or will you have to select which person will be assigned to which task ? etc.

Maybe we could create something like a todo list or list of tasks assigned to different people in an event or make possible to link child events to a parent event. We still need to clarify the need and workflow to be implemented.

@kazemar
Copy link
Contributor Author

kazemar commented Aug 31, 2021

However I think that we should work on a way to easily create a batch of events by eg selecting a layer or features in a map. But this raises potential problems like: what to do if the features are changed after the event has been created ?

For me, two solutions :

Case 1
When editing a layer used by an event :

  • show an information message telling that the layer is used
  • after modification, show a reminder on the event (even maybe on the user frontpage, by the link telling that you have X events), mentioning the source layer modification

Case 2
Needs to add the possibility to deactivate an event (like a draft)

  • locking the layer, with a message inviting to first deactivate the event
  • after this, a message inviting to reedit the event before activate it

do you want to send all events to the same participants or will you have to select which person will be assigned to which task ?

A page can show the list (one line for each "under" event), with checkboxes, giving the choice to assign one group/tag/member for all, or giving the possibility through a text field to select the participants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants