New Member
There will be access to schedule classes at stake level? ie. 4th Sunday clases. Sunday school also at stake level?
gmolleda7 wrote:There will be access to schedule classes at stake level? ie. 4th Sunday clases. Sunday school also at stake level?
This is an early rollout for beta testing and only wards can schedule at this time. I believe they plan to add stake capability, but wanted to get something out as soon as possible, hence it is not complete.This is currently a ward/branch level only application.
Please consider adding stake into workflow before going live
lajackson wrote:According to the curriculum guidelines, Sunday School is scheduled at the ward level. The stake schedules the 2nd, 3rd, and 4th Sunday priesthood and Relief Society lessons (although the stake has the option of delegating the 4th Sunday to the bishop).
This is an early rollout for beta testing and only wards can schedule at this time. I believe they plan to add stake capability, but wanted to get something out as soon as possible, hence it is not complete.
I'm sure that in some stakes, "convenience" and "trickle down" would not be the proper terms describing how "decisions" by the stake president is presented to the wards.jdcr256 wrote: The convenience of stake "trickle down" functionality is a lower priority.
Handbook 2: 7.8.1 "Fourth Sundays: On the fourth Sunday the lesson is taught...The stake president or bishop selects the message"
Adding such lessons to the stake calendars would continue to be the work-around in some stakes even after the scheduler goes live...Instructions for curriculum 2012, page 6
"If stake conferences or other meetings preclude the teaching of one of these lessons, stake presidents and bishops decide if it should be taught on another Sunday."
kisaac wrote:I'm sure that in some stakes, "convenience" and "trickle down" would not be the proper terms describing how "decisions" by the stake president is presented to the wards. Adding such lessons to the stake calendars would continue to be the work-around in some stakes even after the scheduler goes live...
With the calendar and directory, and both have been out for quite awhile, some wards are off and running, some are not, and need a little "push" from trained people on the stake level. Why would the lesson scheduler, or any new module, be any different?aebrown wrote: [*]Stake clerks are specifically responsible for training ward clerks; it's very difficult for them to learn what they need to know in order to provide that training with no access. .....
So if it's not a huge effort, please consider involving stake administrators in lesson schedules.
kisaac wrote:(Check my math: Assume nine class schedules per ward X four conference dates = 36 entries made for each ward, times the number of wards (6 for me) = entering four conference dates a total of 244 times!)
Sorry! My mistake! I did some adjusting (adding our "extra" non-traditional unit, more units but with less organizations) and didn't show my math! (yeah, that fourth grade teacher was right, it does get me in trouble....) 244 was my "guesstimate" for us, or 7.7% of the weeks as you put it.aebrown wrote:Being a math guy, I couldn't help but check your math, and I'm having a hard time figuring out where the number 244 comes from, since 244 is not a multiple of 36. If there were 7 wards in a stake, then 7*36 = 252 is pretty close to 244. Some stakes have 10, 12, or even more wards, so the total number could be 432 or more. But a more realistic way to look at is that 4 out of 52 events are stake and general conferences, so for any schedule we're talking about 7.7% of the weeks on the schedule.
kisaac wrote:As the beta exists now, and if I understand it, each ward must instead add those four dates separately into each class schedule, for a grand approximate total of entering the dates 244 times in my stake![INDENT][INDENT]4 conferences = 244 "events" added by ward leaders (to all ward schedules individually, across a whole stake)
[/INDENT][/INDENT](hope nobody makes a typo in any of those times....)
(Check my math: Assume nine class schedules per ward X four conference dates = 36 entries made for each ward, times the number of wards (6 for me) = entering four conference dates a total of 244 times!)
eblood66 wrote:Actually, events like general and stake conference only have to be added once per ward. There is a checkbox to indicate it applies to all courses. Even for events that don't affect all courses, you just check the courses it applies to. You don't create separate events. So it's only 24 events in your case. And creating an event only takes a few seconds. I created all 4 for our ward in just over a minute.
I whole-heartedly disagree with the response, while it is true the tool doesn't remove the authority, It only makes sense that access at the Stake level is implied.The Handbook gives the stake president specific authority over some of these areas (as kisaac documented) and general authority over all of them.
My Own comment here is that the church has sent out policies, and when you call leader, member and unit support a high priority is given to stake clerks, ward clerks are supposed to funnel up through a stake clerk, who is unable to view/help --> This is my own observation as well, the tools, priorities, seem to go against what I see as a mandate coming down. It makes Stake Clerk's lives very difficult. --> Here is a scenario... Ward Clerk calls Stake Clerk, asks for help, Stake Clerk replies, sorry, I don't have access, I can't see what you see, you'll have to call SLC... Ward Clerk calls SLC, waits on hold a long time because they are not a Stake Clerk, first question from helpdesk, did you talk to your Stake Clerk? Well, I called but he couldn't help me.... Helpdesk, we're need you to work with your Stake Clerk, if he isn't able to help you, please have him call us.Stake clerks are specifically responsible for training ward clerks; it's very difficult for them to learn what they need to know in order to provide that training with no access. This is an important issue that seems to be neglected in the current direction of the Church with its leader and clerk web applications. I know I'm going to be asked many questions by ward clerks and others about this new lesson schedule module and I will only have a vague idea how to help them. That's not good.
I would add additionally, there are stake-level courses that we offer in Family History, Marriage, through LDS Social Services, Know your religion, Institute, etc.. that would be administered at the Stake Level only.In the specific case of lesson schedules, a stake clerk could provide the first pass at creating priesthood and RS lesson schedules in a way that provides consistency across the stake, then turn over administration to the wards.
So if it's not a huge effort, please consider involving stake administrators in lesson schedules.
We decided the additional complexity of stake administration was not necessary to give wards the ability to publish a lesson schedule, and so would not be a part of the 1.0 release.
JohnShaw wrote:I am personally very interested in who 'we' is, but I realize I'll probably never know. What I hope 'we' is is a collection of Ward and Stake Clerks, experts at MLS from wards and stakes in Utah, but also surrounding areas, maybe some with large boundaries with hours to drive end to end. The perspective would be refreshing I think. Maybe this already happens, but in my experience, a top-down, here's what I'm giving you approach, rather than a bottom-up, what would you like to see approach seems a better thing.
I doubt there is a Stake Clerk in the church that would say... ya... develop it so that only ward clerks have access.
That's me! As a ward website administrator, it has been frustrating to me to have little to no control over the Priesthood/Relief Society Schedule, especially since the Relief Society Secretary lets me know exactly what the schedule is.eblood66 wrote:I'm sure there are quite a few ward clerks who would say, "Yes, give it to me sooner even if the Stake Clerk can't help me yet."
I think the real issue to me in this rollout is that it is not only too little, it is too late. We're already midway through February, I anticipate the actual rollout being March, by then we've operated 25% of the year with an older system, or a paper system. I don't anticipate adoption of the system until the start of the year next year. Maybe I'm just a downer in this, but I didn't see or read the clamor over a simple scheduling system. I haven't had anyone in my stake come to me and say, hey, we need this, when is it coming.... I do hear other things, but I'm a broken record in that area by now... Frankly without Stake-level access, what is my motivation to ensure that it gets rolled out to the wards and branches? I'd probably prefer to wait until the stake might have the access, or roll it out to begin a year.eblood66 wrote:So as valid as your points are, not every ward needs stake help so there will be a fair number of wards that can start using it. And you may be right that no Stake Clerk would say to develop it with only ward level access, but I'm sure there are quite a few ward clerks who would say, "Yes, give it to me sooner even if the Stake Clerk can't help me yet."
To me that's a reasonable position on the stake level. Actually, I doubt our ward will use this any time soon. Most people in my ward just don't go on-line to get information. But I'm glad to be able to play with it and I'm glad that others will start using it. With that feedback hopefully it will be useful for all units sooner.JohnShaw wrote:Frankly without Stake-level access, what is my motivation to ensure that it gets rolled out to the wards and branches? I'd probably prefer to wait until the stake might have the access, or roll it out to begin a year.
JohnShaw wrote:It is disappointing that we couldn't enter 2012 with some of these systems in place (Newsletter and Scheduler), I believe with all my heart that it was the intention to provide it prior to 2012 but for many reasons beyond IT control, other areas were prioritized ahead of it.
lajackson wrote:According to the curriculum guidelines, Sunday School is scheduled at the ward level. The stake schedules the 2nd, 3rd, and 4th Sunday priesthood and Relief Society lessons (although the stake has the option of delegating the 4th Sunday to the bishop).
mtwerner wrote:Where exactly in the curriculum guidelines does it say this? I just looked through the "Instructions for Curriculum 2012" and can't find anything like that.
It seems unlikely the stake president would have any decision power unless the stake set the schedule in the first place. It would certainly complicate it if wards were on different lessons.Second and Third Sundays.
If stake conferences or other meetings preclude the teaching of one of these lessons, stake presidents and bishops decide if it should be taught on another Sunday.
That seems pretty clear.Fourth Sunday —Teachings for Our Time.
The stake president or bishop selects the talks.
JohnShaw wrote:I doubt there is a Stake Clerk in the church that would say... ya... develop it so that only ward clerks have access.
This is the primary reason I like the new scheduler the way you rolled it out. Thank you.jdcr256 wrote:The closer an admin is to the class, the more likely the schedule will be updated to remain relevant.
With that Qualifier, if you had asked me, a stake clerk, I would've said the same thing.... Another great reason to publish your roadmap, strategic initiatives you're working towards, deadlines you are on, etc... The community is here to support you, and offer assistance, we are the ones who roll out the apps to your end users, typically.... I would take advantage of a group like this.jdcr256 wrote:Believe it or not, in our quest to simplify the app, the strongest advocate for leaving stake admin out is indeed a stake clerk.
In cutting corners to fit our resources, we decided to support the people who could best maintain the schedule first (ward and auxiliary leaders). Are there really good reasons to support Stake admin, absolutely. It just didn't fit in the 1.0 release, so we had to push it off for later.
RussellHltn wrote:It's easier not to give in the first place then to try and take things away later.
This sounds like some people believe we are talking about an application that has been fully released. It has not been fully released. The scheduler is in beta and we as the community are helping with the development by giving feedback and insights into issues so that when it is fully released there will not be significant issues. Granted we can use it, but as noted in the Lesson Scheduler Application now available in Beta thread notice even the data may not persist once it is released. If you are using the scheduler for your official scheduler for your unit then you may be quite unhappy when the data is reset, if that need were to occur.JohnShaw wrote: Why not develop it fully, roll it out a bit later?
So the question becomes what features will it have when it reaches "fully released". I'm under the impression that the stake will not have any access until some time later. It's not being added during the beta.jdlessley wrote:This sounds like some people believe we are talking about an application that has been fully released. It has not been fully released.
jdcr256 wrote:I'm not sure what you're referring to here. What are we taking away?
RussellHltn wrote:I'd assume that wards would have a limited ability to override what the stake enters. Someone is going to complain if V1 gives them total control but V2 then limits them. I'm just saying you need to be ready to explain any changes that adds restrictions. (While freedoms are welcomed with open arms.)
My point is why the rush now? Why rush to bring out only part of what you want to bake into the system. By the team's own admission they had to limit what they originally wanted to do in an initial rollout (that's my interpretation) due to time and resource constraints. Nobody is expecting v2 or v3, that's reserved for adding to the calendar, adding to lds tools or gospel library, or adding RSS feeds, having lessons show up when you log into lds.org, etc....jdlessley wrote:This sounds like some people believe we are talking about an application that has been fully released.
The "initial rollout" is currently beta only, for community members to do quality assurance testing with it. As of right now, it is not ready to be used in wards and stakes since there are still many issues to be ironed out. At this point, I would encourage people to "play with it" if they want to, and nothing more. It's not as if we are being asked to incorporate this in our wards right now. There will likely be many changes before official implementation occurs. One of those changes may be stake access, and it may not be. (I would have no knowledge either way). Does that make sense?JohnShaw wrote:By the team's own admission they had to limit what they originally wanted to do in an initial rollout (that's my interpretation) due to time and resource constraints.
AileneRHerrick wrote:There will likely be many changes before official implementation occurs. One of those changes may be stake access, and it may not be. (I would have no knowledge either way).
But I certainly understand the need to make compromises between features, time, and resources. My hope is that the stake administration features will be added to Lesson Schedules by November or so -- that way the stake can be involved in the 2013 planning process.jdcr256 wrote:In cutting corners to fit our resources, we decided to support the people who could best maintain the schedule first (ward and auxiliary leaders). Are there really good reasons to support Stake admin, absolutely. It just didn't fit in the 1.0 release, so we had to push it off for later.
Oh, I could be wrong, but I thought that the beta version that was online now was the "first release" and intended for beta use only. I could be mistaken, but that was my understanding.aebrown wrote:Actually, we do have knowledge of that. There will not be stake access in the first release.
I don't see that there is a rush. There is no requirement that units use the beta. The link to the beta has only been publicized in the forum. We have most of this year to test it. There may be a period during 2012 that v1 will be available. But in my opinion that gives time to work out issues that need to be taken care of before everyone begins 2013 with the new lesson scheduler and the classic is retired. The only point I am seeing discussed is that the stake will not have input directly to the online schedule at least for version 1. That could be incorporated before the release that is used for 2013.JohnShaw wrote:My point is why the rush now? Why rush to bring out only part of what you want to bake into the system.
Until there is a version 1 it is not an official release. Alpha and beta versions are pre-release stages of development. The release today was beta revision 506, not yet to version 1.AileneRHerrick wrote:Oh, I could be wrong, but I thought that the beta version that was online now was the "first release" and intended for beta use only. I could be mistaken, but that was my understanding.
jdlessley wrote:Until there is a version 1 it is not an official release. Alpha and beta versions are pre-release stages of development. The release today was beta revision 506, not yet to version 1.
gxwheel wrote:Will the Scheduler be available in other languages with Version 1? Hopefully German is available : -)
Thank you! Your response was helpful.jdcr256 wrote:I need to clarify some things here.
Don't worry. No offense taken here. I think you did good by focusing on the ward level first.jdcr256 wrote:Oh, and since it's my fault that I wasn't clearer that this was a short beta, I'll try to sooth the wounds by saying as much as I can. You want us to move on to the other projects.
jdcr256 wrote:You want us to move on to the other projects.
nbflint wrote:For what it's worth, as a Ward Clerk and Website Administrator I absolutely LOVE the way v1 is planned. My biggest frustration with the Priesthood/R.S. Schedule in the classic LUWS was that it was inaccurate enough to discourage usage AND there was nothing I could do about it. I'd rather be responsible for inputing and updating the schedule than to have a tool without credibility.
I cannot test this, but is this ability available now in beta? What stake callings does this apply to, STAKE WEBSITE ADMIN and / or others?jdcr256 wrote:In order to accommodate some of the requests in this thread, we have added the ability for stake admins to view the application as though they were admins in their home ward. In other words, stake admins will be able to log in and create/modify classes and lessons for their own ward.
This will allow stake admins to see and use the admin controls so they can help members of their stake with training upon request.
I tried it, and it's definitely available now to an assistant stake clerk. I assume it's the standard set of stake admins that are the analogues of the ward callings listed in Default administrators for Lesson Schedules.kisaac wrote:I cannot test this, but is this ability available now in beta? What stake callings does this apply, STAKE WEBSITE ADMIM and / or others?
Please address this in a separate thread in the Calendar forum.sharonlower wrote:Stake clerks in our Stake what nothing to do with the Stake Calendar so I'm elected to do the updates
1-can not see other wards to help other new ward admins
Please address this in the Directory forum.sharonlower wrote:2-directory.. that has disappeared can't help stake members with their profile
Stake leaders have access to their own ward's lesson scheduler as though they are leaders within their own ward. Stake level access/input will come some time in the future. The program has been rolled out with the essential elements for wards to schedule lessons.sharonlower wrote:3-Lessons: haven't seen anything so I add by hand on Stake Calendar and add lds.org magazine link to the lessons
Please address this in the Beta Newsletter forum.sharonlower wrote:4-Newsletter: haven't seen this added to my Stake Admin tools yet
sharonlower wrote:What needs to be added is this:
NOT ALL WARDS have Ward Admin and Ward Calendars !
So the Stake Depends on me as Stake Admin to add the lessons
which now I do by hand on each Sunday with the link
that takes the lessons to the lds.org lesson site
and I have a auto email sent to each stake Member 2 days
before the lessons on that sunday
sharonlower wrote:As Stake Admin I now can NOT add emails to stake members nor can I add photos members send me from their wards within my stake
sharonlower wrote:I can not even add HC new photos within our Stake
sharonlower wrote:The clerks in our ward will not be adding lessons
they don't want to so I hope I have rights as Stake and Ward admin with our Ward calendar
sharonlower wrote:Please consider all that the Stake Admin use to do in
the OLD Calendars and now we have nothing to do but type in calendar events
sharonlower wrote:Frustrating having members so nicely email me for help and they cant or don't want to take the time to log in to add their family photos or emails
...
And we have Chinese and Koream members that need help and I can not because the rights for me as Stake Admin for adding to their profile has been taken away.
You will have visibility into ward calendars in the future; see Access to all Ward/Branch calendars within Stake by Stake/District leadership. In the meantime, you can help ward administrators by sitting down with them (perhaps using screen sharing software if they are some distance away) as they sign in to their account.sharonlower wrote:Lastly: How can I help anyone with new Ward calendars
if I can not see them?
Stake Access
Ability for Stake to Input Master Lesson Schedule for PH/RS
Does this take into account ward specific events such as ward conference?sorensenbm wrote:All the wards use the same master schedule.
I would agree as long as the wards could adjust the schedule to accommodate ward specific events.sorensenbm wrote:It would so much easier to do it once at the stake level.
jdcr256 wrote:The ability to for wards and auxiliaries to create and use a lesson schedule was the priority for the 1.0 release. The convenience of stake "trickle down" functionality is a lower priority. There is consideration and design for stake admin level functionality that is being considered for a later release.