[dev] Proposal for Resource booking extension for Kronolith

[Jan Schneider]

Stephane Pointu wrote:
> 
> Hi all,
> 
> Below is our proposal for implementing resources management in Horde.
> It will be based on Kronolith.
> 
> The principle:
> When creating/editing an event, the user will be allowed to select a
> resource to be added to the event. If the resource is available, it will
> be booked (for recurrent events, only the 1st occurence is checked). If
> not, the user will be allowed to update the event to match a period
> where the resource is available, or remove the resource from the event.
> A view link is added next to each resource for the user to be able to
> view the free-busy information for the resource.
> 
> Optionnally, for recurrent events, we can ask the users to confirm their
> next booking just after the previous event to make sure a booked
> resource is really used. The resource will be freed if the user does not
> confirm after x days.
> 
> Optionnaly again, old bookings can be deleted automatically after a
> defined period of 1 month, 3 months, 6 months, 1 year.
> 
> 
> Database table to be created:
> events_resources
> + event_id -> Taken from events table
>   resources_names
>   event_date -> confirmed booking
>   next_event_date -> next event to be confirmed
> 
> Below are 2 screenshots that will help to better understand our proposal.
> 
> Please comment on this.
> 

You are working against the release version of Kronolith, but you need to
work against CVS HEAD if you want your patches to be accepted.

Why don't you "userless admin shares" like proposed by Chuck?

Specifying resources in the configuration seems too inflexible to me. If
using shares you could attach real names, descriptions, resource types etc.
to the resources.

I don't quite understand the recurrence functionality yet.
-- 
View this message in context: http://www.nabble.com/Proposal-for-Resource-booking-extension-for-Kronolith-tf3605255.html#a10073215
Sent from the Horde - Dev mailing list archive at Nabble.com.