Im building a first responder availability app and I want to use ES as the backend, however I want to make sure its the best fit. Im totally new to Es and one of the reasons im keen to give it a go.
The app consists of 3 types of people: -
A commander can be a team leader and member, and a leader can be a member, but a member is just a member.
There are around 30 people on the team, on call 24/7 and as everyone is a volunteer they currently book off in hourly segments. So we can see what type of availability we have for any hour. ES seems to handle dates OK, but would it work for hourly blocks and if so, what way would you go about storing each hour the person is either available, not available or delayed availability.
Ideally we would use this to provide a number of views within the app
1 - A list of all people with their availability shown for the day/week/month (im still working on how this will look)
2 - A persons availability singular for a day/week/month
When someone 'books off' I would also like to analyse the time they have booked off for pinch points. This would be when we have very low cover, we would need at least 4 team members, 1 leader and 1 commander available at all times.
Being totally new to es im just looking at some pointers of where to start and if there are any built in types that could help. I guess I would store each hour booked off per user as they add it.
One other thing im not clear about is deleting data too, if a user suddenly becomes available they may wish to delete the time they booked off as plans change, is this kind of live updating/deleting possible too?
We would also like to mine the data in the future to try and spot low availability trends etc, but for now im more concerned with keeping a 'live' view of who is and who isnt available.
I hope my initial question is clear enough.
Thanks in advance.