| 1 |
= Resource Conflict =
|
| 2 |
|
| 3 |
This module allows for users to book resources for use during events. For
|
| 4 |
example, a student can book a microscope for use within their lab.
|
| 5 |
|
| 6 |
== Requirements ==
|
| 7 |
|
| 8 |
CCK and it's nodereference module: http://drupal.org/project/cck
|
| 9 |
Event: http://drupal.org/project/event
|
| 10 |
|
| 11 |
== How does Resource Conflict work? ==
|
| 12 |
|
| 13 |
Resource Conflict requires three things to be set up within a content type. The
|
| 14 |
content type must have at least one nodereference field. The content type must
|
| 15 |
be event-enabled. The resource conflict option must be enabled, and at least
|
| 16 |
one nodereference field must be selected. These will be the resources which will
|
| 17 |
be checked for conflicts.
|
| 18 |
|
| 19 |
If there is a pre-existing event which conflicts in both time and resource, a
|
| 20 |
form error is set and the user is forced to either book a different resource or
|
| 21 |
change the event times.
|
| 22 |
|
| 23 |
== Contact ==
|
| 24 |
This module was developed by Andrew Berry (andrewberry@sentex.net) for use at
|
| 25 |
the Protein Dynamics lab at the University of Guelph.
|
| 26 |
Project Page: http://drupal.org/project/resource_conflict
|
Parent Directory
| 
Revision Log
| 
Revision Graph