goodog wrote:I think the problem is definiton of turms and usage.
goodog wrote:My understanding is that the scheduler and calendar person is one in the same.
As I look at your posts there definitely is some misunderstanding about terms. When posting in these forums it is best to use the terms used in the LDS.org calendar system as defined in the
calendar help. The calendar help definitions include
rights and roles when talking about people.
Building schedulers are assigned manually to that position by stake administrators. It is not a position made through MLS. These are the building scheduler roles:
- complete control over the events taking place in their locations, regardless of the calendar. They can update the details for any event scheduled in their location.
- reserve locations for wards at specific, recurring times.
- block out the calendar for a specific location, preventing any calendar editor from scheduling it. Blocking the calendar allows the stake or ward to keep the resource free from booking.
- can change details about the resources available at his or her location.
Note what is missing from the list of what a building scheduler can do is the ability to create events. The building scheduler role
cannot create events. That is what editors do.
Editors can add and manage events on a specific calendar. Members become editors when they either create a calendar, and it is approved by an administrator, or they are added as an editor either by calling or by name to a specific calendar.
Administrators have editor rights to all public calendars for their ward. Stake administrators have editor rights to all public stake calendars. I will not list the other administrator rights here.
An individual, through their callings and assignments, may have any combination of roles in the calendar system. So a building scheduler can also be an editor. Some people forget they have multiple roles with the accompanying rights when discussing issues they encounter. A building scheduler who is also an administrator may confuse the administrator rights as being part of the list of building scheduler rights.
Some terms used in the calendar system can create confusion unless the definition found in the calendar help is understood. For example the term "reservation" means something a bit different in the LDS.org calendar than expected. I have added the term "book" to those found in the calendar help to differentiate what reservation does and what an event does.
Reservations are created by a building scheduler to set aside a location or resources at a location for a ward or stake at a specific calendar time slot. Setting aside the location or resources at a location does not "
book" the location or resources. Because the reservation only sets aside the location or resources at the location, any editor of the ward specified in the reservation can book that location or the resources.
There are two types of reservations. The first is a reservation for a ward or stake. The general description in the previous paragraph is this type of reservation. The second type of reservation is a "blocked reservation". When a building scheduler makes a blocked reservation only the building scheduler(s) for that location can schedule events using the resources designated in the reservation during the specified time period.
Events are the only way to "book" a location or resources. Reservations only limit who can book a location or resources. Booking locks the availability of a location or resources for a specific use during a specified time period. While a blocked reservation may limit booking a location or resources to the location's building scheduler(s), it also does not book the location or resources.
A regular reservation or a blocked reservation may appear to editors as though the location or resources are booked because the conflict notice will appear when an event is created during the time period the resources are reserved.
goodog wrote:besides that if you do any thing on the reservation calendar move and event, schedule or block any one with calendaring rights yw, ym, hp, elders, bishop other wards, stake can calendar an event at the same location at the same time with the same resources as the blocked or moved, or reserved resources or event that was moved. In my mind that is double booking to different activity's at the same time in the same place. If you do anything in the reservation calendar this will happen every time.
Just remember that a reservation made by a building scheduler does not book any location or resources. It merely sets aside resources to permit only the editors of the ward designated in the reservation to book those resources. A reservation excludes other wards from booking resources. Because a reservation does not book resources there can be no double booking.
It is easier to understand what a reservation is by an example. This example is very much like the one RussellHltn gave:
A meetinghouse has three wards that meet there. Each ward has a designated night for mutual activities. Let's say Ward A has mutual on Tuesday evenings. To prevent anyone from Ward B or Ward C (or anyone else other than Ward A) from scheduling an event on Tuesday evening between 6:30pm and 8:30 pm in the YM room, the YW room, and the cultural hall the building scheduler would make a reservation on Tuesday evening from 6:30 pm to 8:30 for the YM room, YW room, and the cultural hall. With that reservation made, which could be a repeating reservation, only Ward A calendar editors can create events on Tuesday between 6:30 pm and 8:30 pm using the YM room, YW room, or cultural hall. Everyone else will get an event conflict if they try to create an event that overlaps those times using those rooms at that location.