owncloud / calendar

Calendar app for ownCloud
GNU Affero General Public License v3.0
121 stars 43 forks source link

RFE: freebusy and selfbooking web interface #1034

Open herrdeh opened 5 years ago

herrdeh commented 5 years ago

We had considerable discussion on the freebusy issue (#582, #25169, #696), as well it happens at nextcloud. After some consideration I came to the opinion that this issue should be solved together with a selfbooking feature. So I tried to write down necessary characteristics which hopefully help the discussion to get forward. If things are working well, I will condense my starting point and additional thoughts to set up a bounty for that feature. These are my thoughts:

Freebusy and selfbooking module

The idea of this module is to enable my customers to do booking of appointments with me (the operator of the cloud) on their own. For that

Do do so, that module has to run on the cloud server and needs to provide two web interfaces:

The result should be a browser interpretable calendar view, which can be integrated to a web page - as well as CalDAV client readable output.

Config interface needs at least these controls:

User interface therefore needs these entries:

Optional:

mokkin commented 5 years ago

This feature would be my dream! We are also willing to spent money for it.

Acutally we are using a proprietary plugin for self booking for our clients but it doesn't not have CalDAV-Support. Almost no booking software has CalDAV-Support. Usually they only support Google Calendar.

Here is an OpenSource attempt for a booking Software, but includes also only Google for syncing: https://github.com/alextselegidis/easyappointments

herrdeh commented 5 years ago

Thank you for your comment. Could you please have a close look where my description needs corrections or additions?

wiredone commented 5 years ago

Thank you for writing up your discussion and enumerating this description. My idealised request is that other, multiple contexts beyond 'a customer' are considered. Punter and Operator want to meet. Operator configures and sends link to Punter with a unique calendar of availability and Punter makes 'booking' and Operator is alerted. The availability would ideally be union or not of various calendars. E.g. If its a client, then availability must be when I am not with my child. If it is a play date or family, then my child must be present.

herrdeh commented 5 years ago

Sorry for my delayed reply. First about words: I wrote "customer", in my mind this not necessarily has to have a commercial context. I'm not a native English speaker, so can we find a better word? - What about "interested person"? The first hit for "Punter" in my translator is "customer of a prostitute", so I'm not sure whether this is the best choice.

Did I get your point right that your idea can be regarded as an extension to the sketch above? My sketch: publish a general calendar of availability, allow interested persons to directly book Your idea: Send an individualized calendar of availability on request, interested person can book on this answer

So your idea is the same as my sketch, but contains one more step: operator individualizes the calendar of availability. If so - can we agree on adding this as an option?

wiredone commented 5 years ago

Thank you for reply. My sincere apologies for not checking the etymology of my colloquialism, I am grateful for the learning! In its modern use, 'punter' does not have the sexual connotation, it is much more generic, like a visitor to a fair ground stall, music gig or other paying event! I enjoyed your sketch above. (I was sad not to be at the conference.) I am grateful for your complete comprehension of my request, I agree.

herrdeh commented 5 years ago

Allright. I updated my initial post and replaced "customer" by "punter". Hope you did not fool me... ((-;

herrdeh commented 5 years ago

I opened the bounty and put an initial 100 USD into it. It's my first bounty, so please tell me if I made a mistake. And of course - feel free to follow.... @