Reservation Flags

[esoterik]

2015-10-03

Merged in #1314, consolidating to-do list:

Required:

• Define fixed set of flags to assign to Reservations (see Reservation Status Overhaul #462)
  • Don't forget the fined flag
• Add UX during check-in and archive for assigning flags (drop-down?)
• Add methods to API to set multiple flags simultaneously (see Expand Reservation flags API #1314)

If possible:

• Allow admins to define custom flags (will likely require us to re-work how flags are defined since they're currently hard-coded in the model)
• Add page / filter for searching for flagged Reservations

---

ORIGINAL

#462 implemented a bitmask for miscellaneous boolean values for reservations, which is currently used to flag requests and for an email task. This should be used to mark any issues with the reservation; for example, if it is lost or broken, the reservation should be flagged as such.

This also means adding checkboxes to the check-in form and the archive JS pop up to set these flags.

See here and here for more information on bitmasks.

[orenyk]

This can be thought of as addressing the original impetus for #462; namely, the ability to flag reservations with different attribute (such as equipment broken) for more classification options. Note that we might want to figure out a way to generate an "ad-hoc" scope for reservations that match a particular bitmask attribute.

[esoterik]

The fined flag also needs to be implemented.

[esoterik]

Oh, there's also information in our wiki about the flags: see here

[esoterik]

And we have a scope that returns reservations with a particular flag as of #462, so that is no longer necessary for this issue