Gary_Miller wrote:jdlessley wrote:Building schedulers can, or should be able to, edit and delete events on any calendar scheduled to use a location or rooms/equipment at a location for which they are assigned as a building scheduler.
In the past yes but the principles of the new calendar is for building schedulers only to be able to add reservations.
To what past are you referring? Unless there has been a change in the roles in the past two weeks, the rights of a building scheduler has not changed since the calendar was in beta. The statement that a building scheduler is "only to be able to add reservations" is not supported in experience nor in the documentation nor in need to support the role. Editing events and editing reservations are more than only being able to add reservations.
A primary function of a building scheduler is conflict resolution, whether proactive or reactive. Proactive conflict resolution is accomplished through reservations. Reactive conflict resolution is through communication, editing reservations, and editing events. Editing of either reservations or events includes deleting.
Gary_Miller wrote:A building scheduler being able to to anymore than that defeats the purpose of having editors and administrators.
Having overlapping rights does not defeat the purpose of a role. The nature of the roles will create overlap in rights to function in the capacity intended. Administrators have all the rights of editors since they have ultimate responsibility for unit calendars. It make sense so they can administer the calendar. Building schedulers have some editor rights to be able to manage the building resources and to resolve resource conflicts.
Gary_Miller wrote:Correct and according to the help section they only have rights to update the detail (edit), and I don't understand why they have that right.
To be able to resolve conflicts may require editing an event. Changing rooms scheduled or adjusting event times, to include setup or cleanup times may be necessary. Some situations may require deleting an event.
Gary_Miller wrote:jdlessley wrote:Any change that does not allow building scheduler to delete events using a location and rooms/equipment at a location for which they are a building scheduler is a bug. The capability to delete events is a basic function of a building scheduler rights.
Not according to the documentation. And why should they be able to delete an event in which they did not set up. There is no possible reason for them to be able to do this. If there is a conflict then it should be worked out among the units involved and there should never be a conflict because someone had to book the event first so the other should find a different date, time or location. The only time I could see justifying a change would be because of a funeral.
The documentation may not be clear about what is meant by "edit". But experience as recent as two weeks ago indicates that "edit" includes "delete". In an ideal world conflicts should be handled between those involved. But that is not always the case. The role of building scheduler (The term is not an adequate description of the role and has been discussed in other threads.) includes conflict resolution. To be able to function in this role requires the tools to accomplish this. Most of us will agree that the need for the building scheduler to step in may occur few times when others communicate, or are capable of communicating.
Since I am not certain that the ability to delete an event has changed recently I will continue to assume there is a bug in the programming. We have experienced changes in functions of applications without notice from ICS in the past. Hopefully someone from the Calendar team will comment on this. Until then I am trying to contact my building scheduler to run a few tests.
Gary_Miller wrote:I have refrained from saying this because I think it should have been obvious. However, it seems to not be so obvious for some. So here goes. ITS TIME FOR EVERYONE TO GO AND READ THE HELP SECTION IN THE CALENDAR. Pay particular attention to the section on roles.
The help documentation may have areas of confusion. It is our responsibility to identify this and submit feedback when there is confusion, things are not clear, or not addressed. We have done this in the past and Tom Johnson has made appropriate updates as needed.