# HG changeset patch # User Paul Boddie # Date 1446817718 -3600 # Node ID fbe00dd6f9712620c6c509e209df18e1ced975c7 # Parent 8eedcceeb483dff76cc1dde83897e075a8fba36e Improved the management interface and free/busy publishing documents. diff -r 8eedcceeb483 -r fbe00dd6f971 docs/wiki/CalendarManager --- a/docs/wiki/CalendarManager Fri Nov 06 13:54:34 2015 +0100 +++ b/docs/wiki/CalendarManager Fri Nov 06 14:48:38 2015 +0100 @@ -37,25 +37,35 @@ * The calendar itself, featuring events, and possibly featuring a column containing requests and invitations +=== Group Scheduling === + Adding scheduling participants, specifying their e-mail address, results in a new schedule column being added for each new participant in the calendar. When creating an event, all scheduling participants are automatically added as attendees. +=== Hiding and Showing Days === + The calendar is divided into days, and these are divided into periods depending on the nature of any events that feature in the calendar. Days for which no events are recorded are hidden by default; such days can be shown if desired. +=== Selecting Periods and Creating Events === + Whole days can be chosen by selecting day headings in the calendar. Similarly, individual periods can be chosen either by selecting period headings along the side of the calendar or by selecting cells in the calendar. Upon selecting periods, controls will appear for the creation of a new event, and if all periods are deselected, such controls will disappear. +=== Event Periods === + Events appear in the calendar as filled regions, and their labels correspond to the summary information defined for each event. These labels link to the event details unless a request has updated the event: in which case, the request label will link to the updated event details. +=== Requests and Invitations === + Requests/invitations appear alongside events in a separate column in the calendar, and their label links to the details of the request (and thus updated event). Such items disappear from the calendar once processed by the user. @@ -105,3 +115,32 @@ if the user has the organiser role, with controls to process these items * Periods that conflict with the event's own periods + +=== Organiser and Attendee Roles === + +Changes can be made to events in both the organiser and attendee roles. As +organiser, any changes will incorporated into the event, and the new version +will be sent to attendees on choosing to update the event. As attendee, +changes are incorporated into counter-proposals that are sent back to the +organiser for approval or rejection. + +=== Editing Event Details === + +Only organisers can edit the core details of an event. They may add and remove +attendees, and they may also add and remove periods associated with the event. + +The removal of existing attendees will not cause such attendees to be +instantly deleted from the event details. Instead, such attendees will +initially be marked as removed and, after editing is complete, have +cancellation messages sent to them informing them that their attendance is no +longer required. + +Attendees themselves can suggest other attendees by adding them, and they may +also remove those suggested attendees. However, they may not remove existing +attendees. + +Attendees can also redefine event periods, but these modifications will merely +be sent back to the organiser for review. Any acceptance of such changes will +occur if the organiser chooses to send out a revised version of the event +featuring those changes. Otherwise, an explicit message declining such changes +may be received. diff -r 8eedcceeb483 -r fbe00dd6f971 docs/wiki/FreeBusyPublishing --- a/docs/wiki/FreeBusyPublishing Fri Nov 06 13:54:34 2015 +0100 +++ b/docs/wiki/FreeBusyPublishing Fri Nov 06 14:48:38 2015 +0100 @@ -22,3 +22,26 @@ Users can enable sharing and publishing themselves by accessing their profile in the [[../CalendarManager|management interface]]. + +Depending on the [[../WebServerIntegration|Web server configuration]], resources are +made available at a location resembling the following: + +{{{ +https://webserver.example.com/freebusy/ +}}} + +Individual user data is published in locations like this: + +{{{ +https://webserver.example.com/freebusy/mailto%3Avincent.vole%40example.com/freebusy +}}} + +Here, the `mailto:vincent.vole@example.com` identity has been URL-encoded. Web +browsers and mail programs may perform such encoding on a location given more +informally as follows: + +{{{ +https://webserver.example.com/freebusy/mailto:vincent.vole@example.com/freebusy +}}} + +However, the properly-encoded version is regarded as the definitive version.