Lack of stake access

Discussions about the Newsletter Tool at LDS.org.
User avatar
johnshaw
Senior Member
Posts: 1839
Joined: Fri Jan 19, 2007 1:55 pm
Location: Syracuse, UT

Lack of stake access

Postby johnshaw » Fri Jul 27, 2012 7:51 pm

Utterly disappointed by the lack of access to this solution by the stake. We sent a message today to all our units, something we do each Friday. I included a note about the live status of the newsletter. A Bishop called and wanted help with a post he was working on, without access I was unable to help. He was frustrated, and likely we lost the only chance of adopting that solution.

What do i tell him, call the GSC?

User avatar
aebrown
Community Administrator
Posts: 14693
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Fri Jul 27, 2012 10:27 pm

JohnShaw wrote:Utterly disappointed by the lack of access to this solution by the stake. We sent a message today to all our units, something we do each Friday. I included a note about the live status of the newsletter. A Bishop called and wanted help with a post he was working on, without access I was unable to help. He was frustrated, and likely we lost the only chance of adopting that solution.

What do i tell him, call the GSC?


The Church can either wait to deliver tools until they are fully perfected, or give them to us when they are quite useful, but still need more work. I personally agree with the philosophy of getting useful tools into our hands sooner rather than later. That gives the development team a chance to incorporate real-world feedback into the next phase of their development, which is a good thing.

The GSC has nothing to do with the development plans, so there's no point in telling him to call them. In the case of the newsletter, I would hope that there are people at the ward level (clerks, executive secretary, website administrator) who have the technical competence to help a bishop -- and they have full administrative access to the ward's Newsletter. I would suggest that one of them could help.
Questions that can benefit the larger community should be asked in a public forum, not a private message.

russellhltn
Community Administrator
Posts: 20777
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Sat Jul 28, 2012 12:45 pm

JohnShaw wrote:A Bishop called and wanted help with a post he was working on, without access I was unable to help.


Without the ability to share his screen, your ability to help may have been quite limited.

Stake DO have the ability to create stake newsletters, so if that wasn't enough then access to the ward newsletter may not have helped.

I suggest you look into one of the free screen-sharing applications. Just make sure both computers are personally owned to comply with any licensing.
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

User avatar
johnshaw
Senior Member
Posts: 1839
Joined: Fri Jan 19, 2007 1:55 pm
Location: Syracuse, UT

Postby johnshaw » Sat Jul 28, 2012 2:36 pm

There needs to be a better alignment with ICS design and ward/stake organization. The only policy I've seen about technology responsibility in a stake or a ward is role for the STS. We had a previous thread about the Clerk being the CTO in a ward, in that thread I was trying to figure out whether a ward clerk should assume a technology responsibility like the stake clerk does, the overwhelming response was that responsibility did NOT reside there, but in the STS - I am just really confused.

jdlessley
Community Moderators
Posts: 6526
Joined: Sun Mar 16, 2008 11:30 pm
Location: USA, TX

Postby jdlessley » Sat Jul 28, 2012 3:22 pm

JohnShaw wrote:There needs to be a better alignment with ICS design and ward/stake organization.
As far as I can tell they are aligned. The Hanbook states that the stake clerk and assistant clerks are responsible for training unit clerks and assistant clerks. The STS is an assistant stake clerk. He should be training the unit clerks and assistant clerks on the use of equipment and applications.

While the STS is the primary agent at the stake for technology within the stake, he does not have to be the only person that every member of the stake goes to to learn how to use technology. The principle here is that he trains people in the wards. In our ward he would train the clerks and ward website administrator who use most of the technology and are also ward default administrators for online applications using ward administrators. These clerks and website administrator ensure the other ward administrators are trained and familiar with their responsibilities. Ward members then go to the trained clerks and website administrator for questions and issues. Any questions and issues they cannot adequately respond to are directed to the STS or the clerks go online to the forums and wiki.

Having been an STS I viewed my responsibilities as managing the hardware and software and provided input to the stake president for policies. I trained unit representatives to be their unit point of contact for technology and technology training.
JD Lessley
Have you tried finding your answer on the LDS.org Help Center page or the LDSTech wiki?


Return to “Newsletter”

Who is online

Users browsing this forum: No registered users and 1 guest