Drupal Inception: what if entities knew about time?

The applications for managing resources over time within Drupal are both obvious and limitless: editorial calendars, booking meeting rooms, invoicing, and so on. Over the years, many modules have sprung up to meet specific use cases: rooms for hotel bookings, resource conflict for equipment bookings, room reservations for study room bookings, and so on. However, the clear limitation of each of these modules is its specificity - a specific use case may be served, but many others are difficult or impossible. After a year of dealing with these issues at Roomify, we took a step back and created BAT - think of it as “nodes for resource management”.

Just as site builders who are new to Drupal experience a sometimes precipitous learning curve, BAT’s flexibility can lead to a paralysis of choice. We will begin by mapping real-world concepts to BAT terminology, and continue by building an example application for booking meeting rooms.

Who should come: anyone who wishes to solve resource allocation and booking problems in Drupal. (optionally with pricing) Where appropriate, we will discuss entry points for customization, but anyone who can build sites with Drupal can use BAT to build booking applications.