Reservations

This documentation is concerning the 2.x version of Reservations.

The Reservations module makes nodes of any content type a list of unique reservable items (like studios) or buckets of interchangeable items (like DV cameras). In its simplest form, the Reservations API prevents these items from being reserved at the same time. By enabling additional sub modules you can extend Reservation API to add user interfaces for checking items in and out, divide items into different inventories, and manage how many reservations a user or group can make with virtual point based budgets.

Reservations is considered Difficult because it requires an understanding of Roles, Permissions, Content Types, Taxonomies, and Views. While you can configure a reservation workflow without customizing the Content Types or Views, the Reservation API is designed to provide a framework that is customizable based on the size of your inventory, whether reservations are being created by staff or end users, and policies about reservations (who can make them, how long, how far in advance, etc).

Creating a Reservations form for a single item like a Studio shouldn't take more than 1 hour. Populating an inventory of hundreds of items of different types that have different policies and can be reserved by hundreds of users based on certifications can take weeks.