We believe it'd be helpful if there was an option for the Back-end Calendar to display events that occur at locations alternative to the main location, and an option to create rooms that are viewable by patrons but not are not actually bookable.

Our library occassionally hosts programs in open spaces within the building, such as the open space in the children's department or a small nook in the YA area. We've found difficultly properly displaying these events on both the back- & front-end calendars for staff and users, as the options currently available for such events either don't equivalently display for both or aren't clear enough for users.

Creating a custom location provides clarity to users on the front-end calendar, as the name of that location is clearly displayed in the "Where" area of the event screen. However, events hosted in a location other than the main one (the library itself) don't appear on the back-end calendar for staff, as this calendar appears to only display events that occur within a primary location and there doesn't seem to be an option to include other locations nor cycle between them. This makes preparing non-room based events in a more specific manner difficult, as any bookign made in a different location means the booking must be looked up via the Booking Search since it no longer appears on the back-end calendar. We're aware this is technically not how the Locations are intended to be used, but the only other options we have aren't ideal and that still doesn't account for the odd inability to easily see on the back-end what events are legitimately occuring at an off-site Location.

Attempting to create a new room doesn't work either, as there's no option to create a room that cannot receive booking applications but still remains visible to the public. The only available way to prevent users from booking a room is by making it invisible to the public, but this, in turn, means any event hosted in that room will not appear on the front-end calendar. Were an option added to keep it visible but simply un-bookable by users, this would easily solve the problem in a way that doesn't require us to use other Locations in an odd manner (though the above option would, again, still be useful to account for events actually occurring at an offsite location).

The only other option we'd found to handle this is to simply create an event at the primary location and specify that no room is required. This avoids the issues of the event not appearing on either the front- or back-end, but we find it's far less clear for users. Yes, the actual location can be included in the description, but many users have still reported difficulty determining this since it's nowhere near as clear as a clearly defined room or a Location specifically noted in the "Where" area of the event screen.