Beta calendar enhancement wishlist

inspired by the thread started by JDlessley

jdlessley wrote:I want to get a discussion of things I am finding in the beta calendar before I submit feedback to the developers.

that thread is here:(some of the issues in the thread are already corrected.)

I would like a discussion about enhancements or improvements for the beta version of the calendar, now up and running at https://beta.lds.org/church-calendar.
Sign in with your LDS account.

I'm very excited about this next generation calendar in association with the next generation of LUWS, and hope this is not taken as criticisms, but helpful improvement ideas. That is the purpose for the Beta test, right? I also realize that for the developers of the calendar to receive these issues, we should use the "submit feedback" link on the calendar page, as they may or may not be monitoring this forum. However, this forum allows the community to brainstorm and collaborate on suggestions, and we can reference this dialog when we "submit feedback."

Here is my short wishlist of changes and enhancements for the short time I've used it.

1. The repeating event function doesn't include an option to repeat most days, but exclude some days. Example: bishopric meeting is every tuesday, except the second tuesday. Choir practice is every sunday, except fifth sundays. Temple recommend interviews are signed every Sunday except fast (first) Sunday. You can put them in every day, then manually erase each one that is wrong. Tedious.
2. The increments of time available for scheduling events is 15 minutes, but that may be too long for some events, such as tithing settlement (10 minute) or Home Teaching interviews, (5 or 10 minutes.)
3. It is impossible to see later events in a very fully scheduled day in month view, with no scroll ability. In week view, 30 minute events are difficult to read. A "day" view doesn't exist but would help. It may also help if a "mouse over" of an event brought up at least the full event title.
4. The printed calendar is not detailed enough to be a stand-alone calendar. For example, it probably couldn't be useful in the printed ward newsletter.

What have others found?

kisaac wrote:Here is my short wishlist of changes and enhancements for the short time I've used it.

1. The repeating event function doesn't include an option to repeat most days, but exclude some days. Example: bishopric meeting is every tuesday, except the second tuesday. Choir practice is every sunday, except fifth sundays. Temple recommend interviews are signed every Sunday except fast (first) Sunday. You can put them in every day, then manually erase each one that is wrong. Tedious.
2. The increments of time available for scheduling events is 15 minutes, but that may be too long for some events, such as tithing settlement (10 minute) or Home Teaching interviews, (5 or 10 minutes.)
3. It is impossible to see later events in a very fully scheduled day in month view, with no scroll ability. In week view, 30 minute events are difficult to read. A "day" view doesn't exist but would help. It may also help if a "mouse over" of an event brought up at least the full event title.
4. The printed calendar is not detailed enough to be a stand-alone calendar. For example, it probably couldn't be useful in the printed ward newsletter.

What have others found?

I think your suggestions are "spot on". This whole project has big potential.

It is worth repeating your first suggestion:

The repeating event function doesn't include an option to repeat most days, but exclude some days. Example: bishopric meeting is every tuesday, except the second tuesday. Choir practice is every sunday, except fifth sundays. Temple recommend interviews are signed every Sunday except fast (first) Sunday.

The quotes below are from the beta calendar transitionthread. They follow, but digress from, a post asking if the current LUWS calendar data would move to the beta calendar when it becomes the new LUWS calendar.

RussellHltn made this post:

RussellHltn wrote:As a practical matter, it wouldn't be a good idea to automatically move the data from the LUWS calendar to the beta one. They're structured differently.

The LUWS calendar is one calender for the unit. The new system allows for multiple calendars. Typically I'd expect one calendar per organization in the unit so that members can select what events they see.

Some of the comments that followed were these:

oregonmatt wrote:I'd even go so far as to suggest that you make as many calendars as possible so that each member will be able to see exactly what they are interested in and filter out what they don't.

zaneclark wrote:I wonder about that... One of the many uses of calendars to view and prevent possible conflicts. With everyone having their own calendar, you would have to check several to avoid a running into some elses meeting or activity.

oregonmatt wrote:Identifying conflicts is not really an issue. It takes about 3 seconds to enable viewing of all of the calendars before scheduling an event. Anybody scheduling something would be wise to do so.

After discussing the features of the beta calendar with my bishop he had concerns about deconfliction of events. His primary concern is the number of calendars that can be created and then deconflicting events with such a large number of calendars for a member to have to subscribe to and view, or review, before scheduling an event.

After thinking about it I have the same concern. Requiring a person to subscribe to all the available calendars for your ward and stake to see if there is a conflict before an event is scheduled is going to introduce human error into the process of scheduling events. For those who do it regularly they will do just as oregonmatt envisions with little problem - check, or subscribe to, them all; review the dates and times for conflicts; schedule the event; and then return your subscription list back to the way you had it.

Our (my stake) current experiences with the LUWS ward calendars and resources calendars teach us that errors abound when people have to look in more than one place for information to complete a process.

The multiple layering of calendars in the beta calendars is good. It just needs to include a quick way to permit a calendar editor to view all events within the ward, and even the stake, for deconfliction and then return to their preferred subscription selections. Perhaps adding a button that toggles between the two would meet this need.

jdlessley wrote:The multiple layering of calendars in the beta calendars is good. It just needs to include a quick way to permit a calendar editor to view all events within the ward, and even the stake, for deconfliction and then return to their preferred subscription selections. Perhaps adding a button that toggles between the two would meet this need.

I agree. This is an excellent idea!

jdlessley wrote:The multiple layering of calendars in the beta calendars is good. It just needs to include a quick way to permit a calendar editor to view all events within the ward, and even the stake, for deconfliction and then return to their preferred subscription selections. Perhaps adding a button that toggles between the two would meet this need.

I agree this is a good idea as well. If building deconflicting is what is required, you can always create a "building" calendar that is similar to the current resource calendar.

Actually, this brings up the critical nature of enabling cross-ward calendars. Building scheduling with resource-type calendars is a must in the new calendar environment. I don't think the new calendars can currently be viewed outside of your own ward.

...and this brings up a current problem we have with wards from different stakes in a single building. The relevant stake presidencies have had to resort to an external calendar to schedule the building. Viewing approved calendars from neighboring stakes would be very appreciated.

For managing resources, I'd like to see that as "properties" of the event. So any changes in the event would change the resources used. (Having to schedule resources separately causes errors.)

For people in other units, they see "busy" for resources, but not what meeting was taking place. Much like Google calendars.

kisaac wrote:inspired by the thread started by JDlessley

that thread is here:(some of the issues in the thread are already corrected.)

I would like a discussion about enhancements or improvements for the beta version of the calendar, now up and running at https://beta.lds.org/church-calendar.
Sign in with your LDS account.

I'm very excited about this next generation calendar in association with the next generation of LUWS, and hope this is not taken as criticisms, but helpful improvement ideas. That is the purpose for the Beta test, right? I also realize that for the developers of the calendar to receive these issues, we should use the "submit feedback" link on the calendar page, as they may or may not be monitoring this forum. However, this forum allows the community to brainstorm and collaborate on suggestions, and we can reference this dialog when we "submit feedback."

Here is my short wishlist of changes and enhancements for the short time I've used it.

1. The repeating event function doesn't include an option to repeat most days, but exclude some days. Example: bishopric meeting is every tuesday, except the second tuesday. Choir practice is every sunday, except fifth sundays. Temple recommend interviews are signed every Sunday except fast (first) Sunday. You can put them in every day, then manually erase each one that is wrong. Tedious.
2. The increments of time available for scheduling events is 15 minutes, but that may be too long for some events, such as tithing settlement (10 minute) or Home Teaching interviews, (5 or 10 minutes.)
3. It is impossible to see later events in a very fully scheduled day in month view, with no scroll ability. In week view, 30 minute events are difficult to read. A "day" view doesn't exist but would help. It may also help if a "mouse over" of an event brought up at least the full event title.
4. The printed calendar is not detailed enough to be a stand-alone calendar. For example, it probably couldn't be useful in the printed ward newsletter.

What have others found?

Excellent suggestions - we're on it, but please be patient ... we don't have the resources of a Google - Thanks! Chadf - Product Manager

RussellHltn wrote:For managing resources, I'd like to see that as "properties" of the event. So any changes in the event would change the resources used. (Having to schedule resources separately causes errors.)

For people in other units, they see "busy" for resources, but not what meeting was taking place. Much like Google calendars.

This is a much better idea. It would still need some supervisory function to answer the question of "Who is using the kitchen when I need to schedule it?"

jdlessley wrote:The multiple layering of calendars in the beta calendars is good. It just needs to include a quick way to permit a calendar editor to view all events within the ward, and even the stake, for deconfliction and then return to their preferred subscription selections. Perhaps adding a button that toggles between the two would meet this need.

oregonmatt wrote:I agree this is a good idea as well. If building deconflicting is what is required, you can always create a "building" calendar that is similar to the current resource calendar.

That is an area that needs attention and I am glad you brought it up. What I was addressing is one organization planning and scheduling an event the same time as another organization. For example the Scouts are planning to have an outing in which many of the fathers will be involved but at the same time the Elders quorum is planning to have an activity. A good number of the Elders quorum members will be absent from the quorum activity in support of their son's scouting event. This is a weak example but I think you get the idea. Sometimes these conflicts are caught through the other communications channels such as ward council. The deconfliction of events in the early stages of planning through the calendar can save the late or even last minute cancelation of an event because of participation conflicts or other conflicts.

oregonmatt wrote:

RussellHltn wrote:For managing resources, I'd like to see that as "properties" of the event. So any changes in the event would change the resources used. (Having to schedule resources separately causes errors.)

For people in other units, they see "busy" for resources, but not what meeting was taking place. Much like Google calendars.

This is a much better idea. It would still need some supervisory function to answer the question of "Who is using the kitchen when I need to schedule it?"

I agree with oregonmatt in needing more information on a scheduled resource. A method we use today for our stake center that has three wards using that same building is to have point-of-contact information such as name, telephone number or e-mail address or both provided with a resource reservation so that others can ask for accomodation for their event directly with the person or organization making the original reservation.

When a calendar is created the text field "Description" is required to have something in it. Yet I do not see where that information is displayed for users. I created some calendars that fill similar yet different needs. Without the description of the calendar displayed to a user it is difficult if not impossible for them to determine whether or not they should subscribe to the calendar. Am I missing something or is this a feature that has not yet been implemented? I submitted feedback but I was wondering if others see where this information is provided that I do not.

oregonmatt wrote:I agree this is a good idea as well. If building deconflicting is what is required, you can always create a "building" calendar that is similar to the current resource calendar.

Actually, this brings up the critical nature of enabling cross-ward calendars. Building scheduling with resource-type calendars is a must in the new calendar environment. I don't think the new calendars can currently be viewed outside of your own ward.

...and this brings up a current problem we have with wards from different stakes in a single building. The relevant stake presidencies have had to resort to an external calendar to schedule the building. Viewing approved calendars from neighboring stakes would be very appreciated.

I submitted a stake calendar for scheduling our building and he was able to approve it. It shows up on the stake calendars list and members are able to subscribe to it if they please. The resources overlay nicely over the other calendars. It didn't take much time to set up. Unfortunately, it does mean double entry. But for now, it's a sufficient work around. In the long term, I think it would be much more convenient to do what you're proposing.

nutterb wrote:The resources overlay nicely over the other calendars. It didn't take much time to set up. Unfortunately, it does mean double entry.

Although I too would like to see some integration of resources with event calendars, I would note that it's not as simple as some people seem to be implying. It is very often (almost always, in my experience) the case that a resource is needed for a different time slot than the event. For the event, you want to schedule the exact time the event starts and ends, but for the resource, there is often setup and takedown time which needs to be scheduled before and after the actual time of the event. Any useful integration of resources and events will need to take this dynamic into account.

jdlessley wrote:For example the Scouts are planning to have an outing in which many of the fathers will be involved but at the same time the Elders quorum is planning to have an activity.

An interesting perspective on "conflict". That would be a problem.

jdlessley wrote:
Our (my stake) current experiences with the LUWS ward calendars and resources calendars teach us that errors abound when people have to look in more than one place for information to complete a process.

The multiple layering of calendars in the beta calendars is good. It just needs to include a quick way to permit a calendar editor to view all events within the ward, and even the stake, for deconfliction and then return to their preferred subscription selections. Perhaps adding a button that toggles between the two would meet this need.

I have problems even now with the LUWS and submission of conflicting events. Yes, leaders often don't even do their own checking before submitting an event that conflicts now, with just one "master' ward calendar to check. I guarrantee they will not be checking multiple places.

some kind of conflict checking is warranted.

oregonmatt wrote:If building deconflicting is what is required, you can always create a "building" calendar that is similar to the current resource calendar.

Do we know if a new resource scheduling "module" is in the works to accompany the new calendar and directory, but just not in beta yet?

kisaac wrote:Do we know if a new resource scheduling "module" is in the works to accompany the new calendar and directory, but just not in beta yet?

There's really no reason you can't create any number of calendars for resources using the beta calendar as it is right now. That's what someone else has already done, as described in this post. Even in the current LUWS, aside from features for assigning a stake resource to multiple wards, there's really not much difference between a resource calendar and an event calendar.

kisaac wrote:Do we know if a new resource scheduling "module" is in the works to accompany the new calendar and directory, but just not in beta yet?

Yes, resource scheduling is in the works. Should be in beta sometime between now and the end of June.

nutterb wrote: The resources overlay nicely over the other calendars. It didn't take much time to set up. Unfortunately, it does mean double entry.

More wishlist ideas...

1) Eliminate some "double entry" by providing a "copy to another calendar" feature. If you enter an event in one calendar, such as a ward party, it would be nice to "copy" that event to another calendar you have rights to, such as a building scheduling calendar. This could be within the "right click" options that already contain a "copy" feature, but it copies it to the same calendar, not your calendar of choice.

2) Be able to add viewers or editors to calendars based on calling, or class. Currently, you must add viewers one at a time to a private calendar. If you want to add all bishopric, or all ward leaders, or in larger groups like all relief society members it would be very tedious. (not that you would need to make this private, but you might) see 4 below

3) provide email notifications / reminders based on viewer preferences. In current LUWS, it's nice to have an email sent to those who choose to have it, that a new event was added. Or, better yet, add "notifications" similar to google calendar, allowing viewer or administrator defined reminders on certain events, like email or SMS (text.)

4) allow a "privacy" (obfuscate) feature as talked about by others. It may be advantageous to have viewers see a calendar, but not be able to see all details. Such as a bishops interview schedule. Members could see open slots and filled slots, but the actual interviewee's name is not visible. Tithing settlement sign-ups are a perfect example when we may need to see open slots but not who has filled the occupied slots. Administrators would see all data.

5) is there an "all ward members as editors" option? Or all organization members as editors? This would be advantageous in the case of appointment sign-up, such as tithing settlement or Home teaching PPI's where any member could sign themselves up for any convenient open spot, by adding their name to the calendar?

If we could combine the features above, imagine the future of "tithing settlement!"

An administrator makes a calendar (or a part of a new "resource scheduling" module) for tithing settlement, outlining which times will be available. each member then logs on, selects an appropriate time from those provided, and places his families name in a time block. He can only see the available open slots, he does not see any others names for privacy. Notifications are set to automatically email him a few days before the appointment as a reminder.

the adiminsrator and bishop at any time can print the schedule, and make adjustments by adding more time slots if needed, or removing or rescheduling some. Perhaps even a statistical report could be generated at any time showing how many ward members are signed up, and estimating how many more interviews need to be scheduled, or print a list of ward members who have not signed up, etc.

this may be more then could be incorporated in a calendar, and perhaps needs to be a hybrid between resource scheduling and a calendar, a whole new module!

jdcr256 wrote:Yes, resource scheduling is in the works. Should be in beta sometime between now and the end of June.

Great! is it too early to provide a wishlist? How about a better description and rules section? A link to fill in "on-line" the often neglected "hold harmless" legal form or a contract when an "outside party" schedules the resource? An option to reserve the whole resource or just portions, such as only the cultural hall, or only the Bowery and not the baseball field? inclusion of Pictures? We have resources shared between two stakes, how can we schedule a common resource for all the members of both stakes?

I submitted through Feedback the request for the ability to jump to a specific month/year like you can with the LUWS calendar. I was chasing down a problem with a repeating entry and it was a bit bothersome to be limited to moving forward and back a month at a time.

kisaac wrote:4) is there an "all ward members as editors" option? Or all organization members as editors? This would be advantageous in the case of appointment sign-up, such as tithing settlement or Home teaching PPI's were any member could sign themselves up for any convenient open spot, by adding their name to the calendar?

This idea seems problematic to me. If all ward members are editors, couldn't they just as well delete one person's tithing appointment and schedule themselves in it's place?

nutterb wrote:This idea seems problematic to me. If all ward members are editors, couldn't they just as well delete one person's tithing appointment and schedule themselves in it's place?

In that case, I think it would have to be "anyone add/delete own" rights for the membership with full editorial rights for the regular editors.

BTW, I really like the idea of connecting the editor to a church position. That way editing rights change with a change in calling. The only problem is, I'm not sure how many callings are exposed in the app that the developers have to work with.

RussellHltn wrote:BTW, I really like the idea of connecting the editor to a church position. That way editing rights change with a change in calling.

I like the idea as well.

RussellHltn wrote: The only problem is, I'm not sure how many callings are exposed in the app that the developers have to work with.

They should have access to all the standard positions.

I've always liked the old LUWS calendar feature that didn't "truncate" long event titles.

A long event title such as this:

Christmas in Jerusalem. Ward Dinner Party
would display correctly in old LUWS calendar, both onscreen and printed, scrolling the title to a second line if needed.

The new calendar constricts an event title to one line in month view, and only displays what fits, like this:

Christmas in Jerusalem. War
and may not be understandable when printed, or on-screen without further clicking to pull up the details. (ok. it might not break the word apart, but it's just an example.)

Google calendar has always truncated long titles, and the new beta calendar has followed suit. This makes the new LUWS less useful to me for use in printing copies for ward newsletters or leadership planning meetings, as truncated events often are not understandable. One can mitigate this by printing in the smallest size possible and not using long titles, but this isn't always possible.

I'll add "don't truncate event titles, scroll them if needed to a second line" to my calendar wishlist!

nutterb wrote:This idea seems problematic to me. If all ward members are editors, couldn't they just as well delete one person's tithing appointment and schedule themselves in it's place?

I had to laugh!
the image of someone signing up for a worthiness interview, where they will discuss their own moral values with their priesthood leader, by "stealing" a coveted spot of another ward member!:p

valid point, however.

I second this

kisaac wrote: ...
2) Be able to add viewers or editors to calendars based on calling, or class. Currently, you must add viewers one at a time to a private calendar. If you want to add all bishopric, or all ward leaders, or in larger groups like all relief society members it would be very tedious. (not that you would need to make this private, but you might)
...

Maintaining calendars for different quorums would be a lot easier if privelages were defined by calling instead of simply name. (Much more helpful in membership record volatile wards, like our YSA ward)

kisaac wrote: ...
A long event title such as this:
Christmas in Jerusalem. Ward Dinner Party
would display correctly in old LUWS calendar, both onscreen and printed, scrolling the title to a second line if needed.

The new calendar constricts an event title to one line in month view, and only displays what fits, like this:

Christmas in Jerusalem. War
and may not be understandable when printed, or on-screen without further clicking to pull up the details. (ok. it might not break the word apart, but it's just an example.)
...

Looks like a newspaper headline.

Also, imagine how...embarrassing to have certain words truncated at certain spots, a light example being 'assume'. (I'm guessing the new restriction is in the database itself [varchar field length or somethin'])

A perfect situation would be to allow calendar owners the ability to create user forms to require end users to populate the form to submit an entry with the ability to have list boxes and check boxes.

See attached or http://rogers-famille.com/schedule/ as an example (this is what our stake uses). It submits to the office LUWS resource calendar and populates the following in the description section of the resource calendar entry...

[INDENT][INDENT]Scheduled Date:.. 06-24-2010
Building:.. LGF
Ward:.. CD
Event:.. Court of Honor
Event Date:.. 06-24-2010
Start Time (w/Setup):.. 06:00 PM
End Time (w/Cleanup):.. 09:00 PM
Rooms:.. Gym, Kit
Contact:.. Joe Smith
Contact Phone:.. 123-4567
Contact E-Mail:.. ihaveanemail@email.com
Key Needed:.. Yes
Scheduled Via: http://rogers-famille.com/schedule

Additional Details/Comments:..
[/INDENT][/INDENT]

Realizing that this would be difficult....

How difficult would it be to allow the calendar owner the ability to populate a template for the description and then everyone adding events would see the description. Similar to something like

[INDENT][INDENT]Ward:
Event:
Rooms Needed:
Contact:
Contact Phone:
Contact E-Mail:
Key Needed?:

Additional Details/Comments:[/INDENT][/INDENT]

While this is still free form it would still collect most of the information necessary for those who need to interact with someone who has a reservation as well as knowing what rooms are needed to reduce double-booking.

Thoughts?

Thanks

oregonmatt wrote:...and this brings up a current problem we have with wards from different stakes in a single building. The relevant stake presidencies have had to resort to an external calendar to schedule the building. Viewing approved calendars from neighboring stakes would be very appreciated.

My unit needs this feature. My unit shares a building with a unit from a different stake. We are willing to dump the Google Calendar we use now but it isn't going to happen unless the developers enable this feature.