First off, awesome program. I have version 1.2 on my yahoo webserver with no issues. I am like a few others I've read on here that use the program to manage equipment checkouts. I work at a university film program and we have an AV cage with various cameras, lighting gear, grip gear etc... A couple things that I think might help those of us that manage equipment versus rooms would be having permissions setup on the accessories too. In my case I have different levels of courses and in those students can checkout different levels of gear. So a basic production class might just be a camera, light kit and Microphone and Boom. Other than the camera, which I setup as a resource, the other gear I would prefer to have as an accessory. But I don't want my basic students to have access to all of the accessories, which could include more advanced lighting kits and grip gear like c-stands, clamps, etc...If I could use the new group permissions in version 2, I could create a basic class group and then assign both the resources and the accessories they have access to.
Yes, I could setup everything in our cage as a resource to solve this, but with the amount of stuff we have, it gets messy in the scheduling. Easier to add most of the little things on as accessories. Plus this makes the reservation so much cleaner looking if we print them out. Just one or two resources and a listing of all the accessories. Also, thank you for adding the option to specify how many of one accessory in the reservation - awesome!
Second thing I was thinking about it having a way to limit the next available reservation time. Right now the program allows users to book back to back schedules on resources. So if Conference room A is booked from 11-12, another user can come in and book the room right at 12. So in this case there may not be time to clean and reset the room. In my case with equipment I wish I could buffer the time when the equipment is ready to be reserved again so I have time to check it for damage. So maybe a setting of, "Minimum amount of time before resource can be scheduled again." Then offering an hour/min field? Could be per resource or global option under blackout times?
Final thing, and this may not fit with the overall goal of the program, but having some sort of check in/check out function...this way I could easily see who is late on picking up or returning. Not sure how that would be implemented in this current form, but I know those of us that do equipment often need to track down late returns.
Seriously though, awesome work...this has been a life saver, especially in my academic environment where money is not there to buy a commercial solution. Thank you!