Make reservations requests friendlier

[squidgetx]

• figure out how to add a review button to the requested items column without getting it too wide
• mass approval of all requests that do not fail any validations
• on review page, be able to see the same information for all requests in the time span
• on review page, be able to approve all selected requests (like checkin checkout!!! oh sweet jesus)
• also have an 'approve all' button for fast approval
• this information needs to include the availability for that time frame
• reservation denial should prompt for a reason which should be sent to the patron. this could be easily hacked in via appending notes
• look at the filters for reservations in admin and patron views and adjust accordingly. admins should be able to easily view all pending reservations and those reservations should not be included in the reserved category. patrons should be able to do the same, but just for themselves of course.

[squidgetx]

dgoerger:

When reviewing a patron's Reservations page, it lists all reservations, including requested extended reservations, under Future Reservations when viewing as admin and checkout person. I noticed that as a patron, their information is separated and categorized, especially the new "requested", "approved", and "denied" tabs. I think it would be better to indicate (in the admin and checkout view) for Future Reservations which ones are actually reserved and which ones are requested. If not separated (i.e. Future Reservations only for actual reservations and then Pending Reservations for ones under review), then can there be an extra column indicating the status of the reservation (i.e. Reserved, Pending/Under Review, Denied).

I'm pretty sure this is at the URL http://development.reservations.yale.edu/bmec/reservations/current/[:user_id]. We should make sure the current action in the Reservations controller uses the correct scopes for future / requests. We might need to add another table to the views for Requests.

[squidgetx]

In patron view at reservations/current/userid I can only see reservations that are auto or approved (on development). I think we should have two tabs here, active/finalized, requested, and denied.

[squidgetx]

We should definitely add availability counts to the review page for sure. We should also make sure that it's easy to view and approve all of a patron's requests for the same time span on the review page. Reservations sort of does this already but it's not really enough information.

[orenyk]

Bumping this to v4.1 so we can push v4.0 to DEV once v3.4.3 has been deployed to PROD

[orenyk]

Just realized that I've created some new issues for functionality that was included in this one; merging them into here.

[orenyk]

Copied from #941:

---

As per #911, we would like admins to be able to review all reservation requests on a per-user basis. I'm thinking that a UI similar to our checkin/checkout page would serve nicely, although it should be a separate page. Each request should display the following information (e.g. in the well):

• Equipment model (with link to show page)
• Equipment model availability for requested time period
• Failed validations
• Request notes
• Approval button

Other things that must be done:

• Approve all button
• Relevant links in the other user views
• Relevant routes