1.1 --- a/docs/wiki/Administration Fri Jan 29 22:17:47 2016 +0100
1.2 +++ b/docs/wiki/Administration Fri Jan 29 22:25:02 2016 +0100
1.3 @@ -16,6 +16,8 @@
1.4 In the background, imip-agent uses and updates information as described in the
1.5 [[../FilesystemUsage|filesystem usage guide]].
1.6
1.7 +<<TableOfContents(2,3)>>
1.8 +
1.9 == Initialising the System ==
1.10
1.11 As described in the [[../GettingStarted|getting started guide]], the system is
1.12 @@ -61,7 +63,7 @@
1.13 be "handed over" at regular intervals.
1.14
1.15 The `freebusy_offers` setting, together with the `scheduling_function` setting,
1.16 -would allow different kinds of resources to "keep open" tentatively-suggested
1.17 +allows different kinds of resources to "keep open" tentatively-suggested
1.18 periods for different lengths of time, allowing frequently-requested resources
1.19 to respond to scheduling requests in a timely fashion, whilst also allowing
1.20 other resources to give more time to event organisers to respond to their
1.21 @@ -108,3 +110,20 @@
1.22 from being routed via imip-agent. This is as simple as either not listing the
1.23 identity in [[../MailIntegration/Simple|lists of addresses]] or by adjusting
1.24 [[../MailIntegration/LDAP|queries yielding calendar users]].
1.25 +
1.26 +== Adding Scheduling Functions ==
1.27 +
1.28 +The `scheduling_function` setting employs functions that reside within modules in
1.29 +the `imiptools.handlers.scheduling` package. Extra modules can be installed in
1.30 +this package by adding files to the `scheduling` directory within the software
1.31 +installation.
1.32 +
1.33 +After adding modules, a tool must be run to register the new modules:
1.34 +
1.35 +{{{
1.36 +tools/update_scheduling_modules.py
1.37 +}}}
1.38 +
1.39 +It is envisaged that the installation of additional scheduling modules and the
1.40 +use of this tool will be performed by the packaging system provided by an
1.41 +operating system distribution.