Skip to content
This repository was archived by the owner on Jul 24, 2020. It is now read-only.
This repository was archived by the owner on Jul 24, 2020. It is now read-only.

Emergency Blackout / Batch Reservation edits #1117

Open
@orenyk

Description

@orenyk

Submitted by BMEC:

This was something the staff thought up because of the recent blizzard, where we had a last minute closure of Bass. It would be awesome if there were a way to take all reservations beginning on a certain date and push them back a day, or take all reservations due on a certain date and pushing them back a day (this one is obviously a little more problematic since it might interfere with existing reservations on the equipment, but the converse seems like it wouldn't create any clerical problems, at least, since the patron would presumably almost always have the equipment reserved the next day too). As it is, we had far too many reservations starting and ending on blizzard day to individually edit each one, and all reservations starting on blizzard day were deleted by the system, while all reservations due on blizzard day became overdue. This created a BUNCH of email work to explain to patrons why their reservations were deleted or that they would not be fined for an overdue reservation.

This is going to create a bunch of problems if you need to extend return dates, as noted above. We might want to implement this in a way that automatically extends all "trivial" Reservations and presents the admin with a list of conflicting Reservations that will have to be updated manually.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions