<h1 class="title">Resources Calendar</h1> <p><a class="reference external" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a></p> <p>This module adds new features to facilitate resource management with meetings:</p> <ul class="simple"> <li>To attach resources to a meeting, go to <cite>Calendar</cite> =&gt; Click on a meeting =&gt; <cite>Edit</cite> =&gt; <cite>Edit</cite> =&gt; add any related resources.</li> <li>To edit or add a resource, go to <cite>Calendar</cite> =&gt; <cite>Resources</cite> =&gt; <cite>Resources</cite>.</li> <li>This module can also prevent resources from being double-booked. Go to a resource and disable or enable <cite>Allow Double Booking</cite> (this is disabled by default). As a note, the same resource in a meeting that ends at 5pm and in a meeting that starts at 5pm on the same day would not not be considered double-booked.</li> <li>You can restrict resources to certain calendar types. In the Resources form view, edit the <cite>Event Types</cite> field. The resource can then be added to events only of those types.</li> <li>Resources cannot be added to events when they're not available, either because they're on leave or because the event time is outside their working time.</li> <li>If you have an event selected as <cite>allday</cite>, only if there are no working times available on 1 or more of the days in that event will an error be raised. For example, if you set an event to <cite>allday</cite> on a Saturday and there are no working times at all that Saturday for a particular resource, then an error will be raised. However, if there is at least 1 working time interval for that resource on the Saturday, regardless of how long or short that working time is, the day will be considered covered by that working time. If the event is not <cite>allday</cite>, any time the resource is not available during the event, regardless of the time of day, will cause an error to be raised.</li> <li>To stop leaves and working time validations on a resource when adding to an event, set the resource's <cite>Working Time</cite> field to blank in the resource form view.</li> </ul> <p><strong>Table of contents</strong></p> <div class="contents local topic" id="contents"> <ul class="simple"> <li><a class="reference internal" href="#known-issues-roadmap" id="id1">Known issues / Roadmap</a></li> <li><a class="reference internal" href="#credits" id="id2">Credits</a><ul> <li><a class="reference internal" href="#authors" id="id3">Authors</a></li> <li><a class="reference internal" href="#maintainers" id="id4">Maintainers</a></li> </ul> </li> </ul> </div> <a name="known-issues-roadmap"></a> <h2><a class="toc-backref" href="#id1">Known issues / Roadmap</a></h2> <ul class="simple"> <li>Abstract out logic from _check_resource_ids_working_times into separate methods in resource.calendar.</li> </ul> <a name="credits"></a> <h2><a class="toc-backref" href="#id2">Credits</a></h2> <a name="authors"></a> <h3><a class="toc-backref" href="#id3">Authors</a></h3> <ul class="simple"> <li>Savoir-faire Linux</li> <li>LasLabs</li> </ul> <a name="maintainers"></a> <h3><a class="toc-backref" href="#id4">Maintainers</a></h3> <p>This module is maintained by Savoir-Faire Linux and it also exists on OCA as <a class="reference external" href="https://github.com/OCA/calendar/tree/11.0/calendar_resource">https://github.com/OCA/calendar/tree/11.0/calendar_resource</a>.</p>