Increase maximum number of items one can attach to a reservation

unlimited is scary

are your users making reservations as well?

i wonder if there would be a need to have separate limits for users versus staff / admin

or whether that adds more complexity than is needed

I would like to suggest admins being able to grant certain roles permission to add the new max number of reservable items. At PhillyCAM there are certain certified producers who create reservations with large number of items. We would certainly like them to be able to add all the required items on one reservation form. It would be great not to have to process multiple forms for what is one reservation request.

I was originally thinking that "unlimited" would be applied at the content type level, but that wouldn't support limiting the number per role.... which makes sense. The biggest issue with allowing 36 items is the UI that would result if several conflicts occurred over several days, but if that type of reservation is limited to staff and more savvy producers, there's less of an issue. Because of how things are already configured, it will be easiest to control the number in increments of 3.

i talked to @kreynen about this and other things.

I'm fine adding flexibility to this system

@synchlayer...where did this issue end up? Have been searching through commits but don't see a commit tied to this issue #. Am wondering if the relevant code is http://drupalcode.org/project/reservations.git/commit/f436e9a and http://drupalcode.org/project/reservations.git/commit/2c049f7?

Both of those reference a view called RESERVATIONS_AVAILABLE_BUCKET_ITEM_OVERRIDE_VIEW. Doesn't look like the view itself comes with the install as I don't see that code added in the commits I've searched, but maybe I'm missing something?

If I'm barking up the right tree, can you share the export of your view? Is there a reason this view couldn't be included in the install?

If I'm barking up the wrong tree, can you let me know what happened with this issue?

removing from cm-beta5, to fix this correctly (basically having ot refactor all the javascript) would take a while, so it has been delayed

emilyf: To answer your question, the RESERVATIONS_AVAILABLE_BUCKET_ITEM_OVERRIDE_VIEW is not required for the module to work. If the view is in place, what happens is when you are checkign out, the list of items for a particular type can display more than just the item name. In MNN's case it also shows a field called "Inventory Number" which is on the reservable item content type.

The view is quite simple, i''ll upload the export of the view to this issue so you can see how MNN uses it. For other use cases, any fields can be added to it.

I'm really curious what the structure of bookings are for people. We regularly have shoots go out with 40+ items. This includes duplicate items, like C Stands (10-15 is common). A typical sign out might look include these items:

camera
mattebox
tripod
follow focus
power kit (I haven't broken out the batteries)
lens kit (same as above)
card reader
data dump station
raincoat
timecode gen
light meter
slate

colour chart / grey card
audio recorder
shotgun mic
wireless mic x 2
stereo mic kit
xlr 25' x 6
xlr 15' x 6

That's 30 individual items and I haven't even gotten to lighting yet.