TechWiki - User contributions [en]

E-books

2015-04-24T17:20:13Z

Aebrown: Remove pointless bolding on header cells (style already includes bold)

'''E-books''' are electronic formatted text that can be read on devices such as e-readers, tablets, smartphones, and computers. Currently the Church is developing ePub-formatted e-books that can be found at [https://www.lds.org/manual/epub?lang=eng EPUB Manuals] on [https://www.lds.org/?lang=eng LDS.org].

== Church-supported e-book formats ==
There are many formats for e-books available. The Church is currently supporting three specific formats that cover a wide range of devices; specifically ePub, Mobi, and KF8.

:{| border="1" cellpadding="3" cellspacing="0"
|+ '''Current e-book formats the Church is looking to create and support'''
! Format
! Devices That Use This Format
|-
|ePub
|B&N Nook, Sony reader, Kobo, iOS devices, Android devices, most smartphones and tablets
|-
|Mobi
|E-Ink Kindles, Kindle Fire
|}

== New Projects ==

===New Teachings of Presidents of the Church Manual Coming Soon===
We will be posting ePub and mobi (Kindle format) versions of the Teachings of Presidents of the Church manual for 2014 soon.

As always, we are looking for testers for these e-books. You will also be able to download these e-books directly from the Amazon Kindle Store, iTunes iBookstore, Kobo eBookstore, Google Play, and Barnes & Noble.

We ask that you leave your technical feedback [https://docs.google.com/spreadsheet/viewform?formkey=dG5kekZLRkNaV0Y1VHFkQmp2QTNHQ1E6MQ here] to make sure and fix any bugs that might arise.

===Current 3rd Party Publishing Channels===
*[http://www.amazon.com/s/ref=ntt_athr_dp_sr_1?_encoding=UTF8&field-author=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&search-alias=digital-text&sort=relevancerank Amazon Kindle Store ]
*[https://itunes.apple.com/us/artist/church-jesus-christ-latter/id522965373?mt=11 iTunes iBookstore ]
*[http://store.kobobooks.com/en-US/Search?query=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&fcsearchfield=Author Kobo eBookstore ]
*[https://play.google.com/store/books/author?id=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&hl=en Google Play eBookstore ]
*[http://www.barnesandnoble.com/c/the-church-of-jesus-christ-of-latter-day-saints Barnes & Noble ]

===Download Links===
*[http://Media.ldscdn.org/epub/lds-scriptures/holy-bible/holy-bible-eng.epub Holy Bible - ePub ]
*[http://Media.ldscdn.org/epub/lds-scriptures/triple-combination/triple-combination-eng.epub Triple Combination - ePub ]
*[http://Media.ldscdn.org/epub/lds-scriptures/book-of-mormon/book-of-mormon-eng.epub Book of Mormon - ePub ]
*[http://Media.ldscdn.org/mobi/lds-scriptures/holy-bible/holy-bible-eng.mobi Holy Bible - Kindle ]
*[http://Media.ldscdn.org/mobi/lds-scriptures/triple-combination/triple-combination-eng.mobi Triple Combination - Kindle ]
*[http://Media.ldscdn.org/mobi/lds-scriptures/book-of-mormon/book-of-mormon-eng.mobi Book of Mormon - Kindle ]

===Amazon Kindle Store===
*[http://www.amazon.com/Holy-Bible-ebook/dp/B00BMWE99S/ref=sr_1_6?ie=UTF8&qid=1362151173&sr=8-6&keywords=holy+bible+lds+scriptures Holy Bible ]
*[http://www.amazon.com/Mormon-Doctrine-Covenants-Pearl-ebook/dp/B00BMWEEJ8/ref=sr_1_1?s=digital-text&ie=UTF8&qid=1362151383&sr=1-1&keywords=Book+of+Mormon+%7C+Doctrine+and+Covenants+%7C+Pearl+of+Great+Price+lds+scriptures Triple Combination ]

===iTunes iBookstore===
*[https://itunes.apple.com/us/book/holy-bible/id609027028?ls=1 Holy Bible ]
*[https://itunes.apple.com/us/book/the-book-of-mormon/id609027608?ls=1 Book of Mormon ]

===Using Calibre to Transfer E-Books to Your Device===
[http://calibre-ebook.com Calibre ] is an excellent free software tool to transfer e-books to your device.

For Kindle users, *do not use the ePub format, instead use either mobi or Kindle format. Otherwise the conversion from epub to a readable Kindle format will not perfectly render properly.

E-books are currently only available on [https://www.lds.org/manual/epub?lang=eng LDS.org] and [https://tech.lds.org/wiki/Gospel_Library_for_ePub LDSTech]. We are in the process of creating and publishing more e-books in the three formats listed above.

:{| border="1" cellpadding="3" cellspacing="0"
! Channels
! eBookstore Links

|-
|iTunes
|https://itunes.apple.com/us/artist/church-jesus-christ-latter/id522965373?mt=11

|-
|Amazon
|http://www.amazon.com/s/ref=ntt_athr_dp_sr_1?_encoding=UTF8&field-author=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&search-alias=digital-text&sort=relevancerank

|-
|Google Play
|https://play.google.com/store/books/author?id=The+Church+of+Jesus+Christ+of+Latter-day+Saints

|-
|Kobo Bookstore
|http://store.kobobooks.com/en-US/search?query=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&fcsearchfield=Author&fclanguages=all

|-
|Barnes & Noble
|http://www.barnesandnoble.com/c/the-church-of-jesus-christ-of-latter-day-saints
|}

===Cost per download===
There is an associated cost to readers to download e-books from some of these third party stores. Amazon and Barnes & Noble require a minimum of $0.99-$2.99 (depending on the file size) to distribute e-books in their respective stores. E-books in the iTunes iBookstore will be available for free. This is not because we favor one distributor over another, but what the minimum requirements for each store are.

== New Projects ==

== E-book Files for Testing ==

* [http://Media.ldscdn.org/epub/scripture-and-lesson-support/book-of-mormon-teacher-manual/2012-11-00-book-of-mormon-teacher-manual-eng.epub Book of Mormon Teacher Manual]
* [http://Media.ldscdn.org/epub/scripture-and-lesson-support/book-of-mormon-student-manual/2012-11-00-book-of-mormon-student-manual-eng.epub Book of Mormon Student Manual]
* [http://Media.ldscdn.org/epub/lds-manuals/gospel-teaching-and-learning/2012-11-00-gospel-teaching-and-learning-eng.epub Gospel Teaching and Learning]
* [http://Media.ldscdn.org/epub/scripture-and-lesson-support/preach-my-gospel-a-guide-to-missionary-service/2012-18-00-preach-my-gospel-a-guide-to-missionary-service-eng.epub Preach My Gospel]
* [http://Media.ldscdn.org/epub/lds-manuals/teachings-of-the-presidents-of-the-church-lorenzo-snow/2012-06--teachings-of-the-presidents-of-the-church-lorenzon-snow-eng.epub Teachings of the Presidents of the Church: Lorenzo Snow]

'''Please leave feedback [https://docs.google.com/spreadsheet/viewform?formkey=dG5kekZLRkNaV0Y1VHFkQmp2QTNHQ1E6MQ here].'''

[[Category:ePublishing]]
[[Category:e-books]]
[[Category:epub]]
[[Category:mobi]]
[[Category:KF8]]

Main Page

2015-04-10T15:24:25Z

Aebrown: Undo revision 70960 by Dauthudvbt2 (talk)

{{Other languages/Main Page}}
<div style="margin: 5px 0px 0px 0px;">
<div style="text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
<div style="font-size: 1.15em;">The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Community Project Handbook]] for information on getting started, and the [[LDSTech:Guidelines|Wiki guidelines]] for information on editing the wiki.</div>
{| width="100%"

| width=33% align="center" |
<span style="font-size: 1.15em;">'''[[LDSTech | LDSTech Projects]]'''</span><br />
<div class="borderedimage">[[image:ldstechhome.jpg|style="homepageimage"|220px|link=LDSTech]]</div>

| width=33% align="center" |
<span style="font-size: 1.15em;">'''[https://tech.lds.org/wiki/Clerk_Wiki_Redirect Clerks]'''</span><br />
<div class="borderedimage">[[image:clerkshome.jpg|220px|link=https://tech.lds.org/wiki/Clerk_Wiki_Redirect]]</div>

| width=33% align="center" |
<span style="font-size: 1.15em;">'''[[LDS.org applications| LDS.org applications]]'''</span><br />
<div class="borderedimage">[[image:Ldsorgapplications.png|220px|link=LDS.org_applications]]</div>

|-
| width=33% align="center" |
<span style="font-size: 1.15em;">'''[http://mhtech.lds.org Meetinghouse Technology]'''</span><br />
<div class="borderedimage">[[image:mhhome.jpg|220px|link=http://mhtech.lds.org]]</div>

| width=33% align="center" |
<span style="font-size: 1.15em;">'''[[Family_Safety | Internet and Family Safety]]'''</span><br />
<div class="borderedimage">[[image:cybersafetyhome.jpg|style="homepageimage"|220px|link=Family_Safety]]</div>

| width=33% align="center" |
<span style="font-size: 1.15em;">'''[[:Category:LDSTech_Administration|Wiki Administration]]'''</span><br />
<div class="borderedimage">[[Image:ldstech-guidelines.png|style="homepageimage"|220px|link=Category:LDSTech_Administration]]</div>

|-
| width=33% align="center" |
<span style="font-size: 1.15em;">'''[[LDS Java Stack | LDS Java Stack]]'''</span><br />
<div class="borderedimage">[[Image:Lds-java-stack.png|style="homepageimage"|220px|link=LDS Java Stack]]</div>

| width=33% align="center" |
<span style="font-size: 1.15em;">'''[[LDS .NET Stack | LDS .NET Stack]]'''</span><br />
<div class="borderedimage">[[Image:LDS_.NET_Stack.png|style="homepageimage"|220px|link=LDS .NET Stack]]</div>

| width=33% align="center" |
 

|}

__NOTOC__
__NOEDITSECTION__

[[Category:Portals]]

Tech.churchofjesuschrist.org

2015-03-15T00:22:37Z

Aebrown: Previous edit inappropriately included the editor's skills, when the article should contain a general description of skills needed for projects.

Any tasks or issues relating to any of the community tools found at tech.lds.org, such as Joomla, Forum, Wiki, Jira, or Subversion.
; '''Summary'''
; Project Manager : Dennis Keating
; Dev Lead : Tim Riker
; Meeting Schedule:
: Mon, Wed, Thurs, Fri. 9:30am-9:45am mst
: Tues, weekly staff meeting 10am-11am via VIDYO

==Purposes of tech.lds.org==
Many people know of the resources for ward clerks and technology specialists on tech.lds.org. The forum and wiki contain myriad conversations and a knowledge base for technology related ward and stake issues that cannot be found anywhere else. Tech.lds.org is an indispensable resource to those seeking technology support in their demanding and difficult callings.

Tech.lds.org also serves as an avenue to facilitate community participation in development of Church technology projects. The Church has many technology [[Community_Projects|projects]] to complete to meet the needs of an ever-growing, world-wide church. The Church seeks the help of the tech.lds.org community with this tremendous undertaking.

==Project Objectives==
The purpose of this project is to continue to improve the '''self-support''' services provided through tech.lds.org. It is also to expand the ability to '''partner''' with the tech.lds.org community on Church technology projects.

===Self-Support===
The '''forum and wiki''' are the tools for '''self-support''' on the site. The wiki provides a codified knowledge base for officially approved uses and scenarios for Church related technology. In the forum, users can post questions and get answers from other forum users. They can also search previous remarks from users. Problems that aren't answered in the wiki can be researched in the forum.

===Community Involvement===
The Church invites participants to review the list of [[Community_Projects|projects]] and '''volunteer''' where they have time and inclination.

==Community Collaboration==
Tech.lds.org provides a collection of tools, held together by glue and sawdust, to enable community collaboration.

===Issue Tracking===
'''JIRA''' is used to track issues on community projects. After joining a project users will have access to that project in JIRA.

===Source Control===
Tech.lds.org currently has source control available with Subversion ('''SVN'''). Git support may be added in the near future. Users have access to the source through the project page. Users do not automatically receive commit access to Subversion, but should contact a project manager to obtain access. Users can create JIRA issues and attach patches to those JIRA tickets.

===Skills Profile===
Users of tech.lds.org can identify which technologies they are comfortable with or interested in learning. This aids project managers in identifying people who will be able to contribute to their project. It is '''not necessary to fill out the skills profile''' to join projects.

===Projects===
The list of available community projects is visible to those who sign the '''contributor agreement'''. Projects are created by sponsors internal to The Church. Community members can join projects they are interested in and participate at a level they are comfortable with. After joining a project, users will be able to comment on and add JIRA tickets related to that project. They'll also be able to submit patches to the project through JIRA. Volunteers can leave a project at any time.

====Contributor Agreement====
Those willing to contribute to Church technology projects must sign the '''contributor license agreement''' before they will be able to start.

===Content Management===
'''Joomla''' is used to manage and maintain the site, the users and the projects.

===LDSTech Development Virtual Machine===
We have created a VirtualBox Appliance that contains functioning instances of the LDSTech web sites so that developers can get started quickly. There are additional details on the [[LDSTech Development Virtual Machine]] wiki page.

==Key Information==
===Communication===

====Weekly Meeting====
An open meeting is held '''weekly on Fridays, 9:30am-9:45am Mountain Time'''.

'''How to Join:'''

Our weekly meeting has been moved to [[IRC]]—Channel: #ldstech
Server: freenode.net (for a U.S. Server: chat.us.freenode.net)

Join using your IRC client, or use the freenode browser interface: http://webchat.freenode.net/

History of IRC Located: http://infobot.rikers.org/%23ldstech/ https://tech.lds.org/irc/%23ldstech/

====IRC====
The preferred method of communication regarding all LDSTech projects is in #ldstech channel on irc.freenode.net. [http://colloquy.info/ Colloquy] is a good IRC client for Mac and [http://www.trillian.im/ Trillian] is a good one for PC. See [[IRC]] for more details.

====Google Groups====
'''Announcement group''' https://groups.google.com/a/tech.lds.org/group/ldstech-announce

'''Discussion group''' https://groups.google.com/a/tech.lds.org/group/ldstech

'''Commits group''' https://groups.google.com/a/tech.lds.org/group/ldstech-commits

===Source code===
The code for tech.lds.org is available:<br>
https://code.lds.org/svn/ldstech/trunk.

===Issue tracking===
Issues, tasks, and bugs can be found in the LDSTech instance:<br>
https://tech.lds.org/jira/browse/LDSTECH

===Test system===
The dev site: http://cdev.lds.org/ldstech/joomla/

The test site uses [[Coda_Application|CODA]] to provide fake user credentials for testing purposes. http://cdev.lds.org/coda/

The following users exist and can be used for testing. The password is 'password' for all of them.

* aaron
* alonzosl
* bruno
* cholder
* ChungBond
* dowdyls
* HarlandBooker
* ian_lees
* JaneDoe
* JaneyDoe
* JimmyDoe
* JohnDoe
* JohnnyDoe
* kaneyb
* KurtBlunt
* luci
* mata
* motleyte
* nonmember
* Octavio
* olmsteadas
* OToole
* pholder
* PorterBadger
* RusselAdam
* vholder
* Бартли
* 逆さ逆さ
* ♠♥♦♣

===Wireframes===
The old wireframes: https://cdev.lds.org/ldstech/wireframes/

===Internal Team Members===
* [[user:smootar|Alan Smoot]]
* [[user:timriker|Tim Riker]]
* [[user:ekeating|Elder Dennis Keating]]

===Release Steps===
* note current release in case we want to role back
* review required sql patches
* confirm regular mysql backups are working
* short news blurb that upgrade is in progress on home and irc
* backup ldstech directory
* svn up
* apply sql patches
* enter and re-save ldap/talentpool/etc modules in administrator if needed
* test joomla, wiki and forum
* remove or update short news blurb and irc topic
* when all tested, remove backup directory

==Requirements==
* XAMPP - PHP/MySQL Development (or similar) - http://www.apachefriends.org/en/xampp.html

[[Category:Tech.lds.org]]

Gospel Library JavaME download

2015-03-13T18:22:58Z

Aebrown: Change external link to wikilink

[[Gospel Library for JavaME|Return to Gospel Library for JavaME]].

== '''New Beta Download page:''' [http://tech.lds.org/dl/gljme/ http://tech.lds.org/dl/gljme/] ==

This article explains how to download the [[Mobile Gospel Library]] to a Java ME phone.

== '''Current Version: Beta 1.0.0''' ==
WARNING: This is a beta version, and may function in an unexpected way on your phone.

'''For questions and bug reports, please email [mailto:glfp@ldsmail.net glfp@ldsmail.net].'''

== Download links ==
'''NOTE:''' Some Java ME phones require a JAD/JAR pair. Some require only a JAR file.

Here are the download links for the appropriate files:

'''WARNING: BETA VERSION '''

'''Most popular '''
{|border="1" cellspacing="0" cellpadding="2"
! BETA 1.0.0 !! Gospel Library JAD !! Gospel Library JAR ONLY
|-
| English ||align="center" | '''http://bit.ly/glengjad''' ||align="center" | http://bit.ly/glengjar
|-
| Español (Castellano)||align="center" | '''http://bit.ly/glspajad''' ||align="center" | http://bit.ly/glspajar
|-
| Português ||align="center" | '''http://bit.ly/glporjad''' ||align="center" | http://bit.ly/glporjar
|}
{{-}}

'''Alphabetical '''
{|border="1" cellspacing="0" cellpadding="2"
! BETA 1.0.0 !! Gospel Library JAD !! Gospel Library JAR ONLY
|-
| Bahasa Indonesia ||align="center" | '''http://bit.ly/glindjad''' ||align="center" | http://bit.ly/glindjar
|-
| Cebuano ||align="center" | '''http://bit.ly/glcebjad''' ||align="center" | http://bit.ly/glcebjar
|-
| Česky ||align="center" | '''http://bit.ly/glcesjad''' ||align="center" | http://bit.ly/glcesjar
|-
| Dansk ||align="center" | '''http://bit.ly/gldanjad''' ||align="center" | http://bit.ly/gldanjar
|-
| Deutsch ||align="center" | '''http://bit.ly/gldeujad''' ||align="center" | http://bit.ly/gldeujar
|-
| Eesti ||align="center" | '''http://bit.ly/glestjad''' ||align="center" | http://bit.ly/glestjar
|-
| English ||align="center" | '''http://bit.ly/glengjad''' ||align="center" | http://bit.ly/glengjar
|-
| Español (Castellano)||align="center" | '''http://bit.ly/glspajad''' ||align="center" | http://bit.ly/glspajar
|-
| Faka-Tonga ||align="center" | '''http://bit.ly/gltonjad''' ||align="center" | http://bit.ly/gltonjar
|-
| Français ||align="center" | '''http://bit.ly/glfrajad''' ||align="center" | http://bit.ly/glfrajar
|-
| Gagana Samoa ||align="center" | '''http://bit.ly/glsmojad''' ||align="center" | http://bit.ly/glsmojar
|-
| Icelandic ||align="center" | '''http://bit.ly/glisljad''' ||align="center" | http://bit.ly/glisljar
|-
| Ilokano ||align="center" | '''http://bit.ly/glilojad''' ||align="center" | http://bit.ly/glilojar
|-
| Italiano ||align="center" | '''http://bit.ly/glitajad''' ||align="center" | http://bit.ly/glitajar
|-
| Kreyòl Ayisyen||align="center" | '''http://bit.ly/glhatjad''' ||align="center" | http://bit.ly/glhatjar
|-
| Magyar ||align="center" | '''http://bit.ly/glhunjad''' ||align="center" | http://bit.ly/glhunjar
|-
| Malagasy ||align="center" | '''http://bit.ly/glmlgjad''' ||align="center" | http://bit.ly/glmlgjar
|-
| Nederlands ||align="center" | '''http://bit.ly/glnldjad''' ||align="center" | http://bit.ly/glnldjar
|-
| Norsk ||align="center" | '''http://bit.ly/glnorjad''' ||align="center" | http://bit.ly/glnorjar
|-
| Português ||align="center" | '''http://bit.ly/glporjad''' ||align="center" | http://bit.ly/glporjar
|-
| Română ||align="center" | '''http://bit.ly/glronjad''' ||align="center" | http://bit.ly/glronjar
|-
| Shqip ||align="center" | '''http://bit.ly/glsqijad''' ||align="center" | http://bit.ly/glsqijar
|-
| Suomi ||align="center" | '''http://bit.ly/glfinjad''' ||align="center" | http://bit.ly/glfinjar
|-
| Svenska ||align="center" | '''http://bit.ly/glswejad''' ||align="center" | http://bit.ly/glswejar
|-
| Tagalog ||align="center" | '''http://bit.ly/gltgljad''' ||align="center" | http://bit.ly/gltgljar
|-
| Tiếng Việt ||align="center" | '''http://bit.ly/glviejad''' ||align="center" | http://bit.ly/glviejar
|-
| Монгол ||align="center" | '''http://bit.ly/glmonjad''' ||align="center" | http://bit.ly/glmonjar
|-
| Русский ||align="center" | '''http://bit.ly/glrusjad''' ||align="center" | http://bit.ly/glrusjar
|-
| Українська ||align="center" | '''http://bit.ly/glukrjad''' ||align="center" | http://bit.ly/glukrjar
|-
| 한국어 ||align="center" | '''http://bit.ly/glkorjad''' ||align="center" | http://bit.ly/glkorjar
|-
| 中文 ||align="center" | '''http://bit.ly/glzhojad''' ||align="center" | http://bit.ly/glzhojar
|-
| 日本語 ||align="center" | '''http://bit.ly/gljpnjad''' ||align="center" | http://bit.ly/gljpnjar
|}
{{-}}

== Installation ==
To install on your Java ME phone, there are several methods:
* Download directly to your phone using your phone's Internet browser (enter the above link into your phone's browser, and it should install appropriately).
* Download to a PC then copy the files to your phone using Bluetooth. Then find the files in the appropriate folder, and click on them to install.
* Use a custom APP installer that is based on your particular phone.
* Download to a PC then copy the files to your phone using a USB Cable. Then find the files in the appropriate folder, and click on them to install.
* Download to PC then copy files to a micro SD card (micro SD card capable phones). Create kjava directory on the card, copy jar file, and jad file if needed, to card. Insert card in phone, go to app giving access to card directories (may be "My Stuff" or something similar), click on the jar file to install.

== See also ==
[[Book of Mormon JavaME download]]

[[Category:JavaME applications]]
__NOTOC__

Talk:UI text translation (Gospel Library for JavaME)

2015-03-11T05:47:07Z

Aebrown: Aebrown moved page Talk:Gospel Library for JavaME: UI Text Translation to Talk:UI text translation (Gospel Library for JavaME): st

German translation of 'Sel' and 'Clr' must have four letters or it does not make sense. --[[User:Sanktsimon|Sanktsimon]] 19:22, 29 September 2011 (UTC)

Talk:Hardware versions (Gospel Library for JavaME)

2015-03-11T05:46:16Z

Aebrown: Aebrown moved page Talk:Gospel Library for JavaME: Hardware Versions to Talk:Hardware versions (Gospel Library for JavaME)

Are you planning to develop the content on this page, or should it be removed? --[[User:Johnsonth|Tom Johnson]] 22:27, 19 March 2012 (UTC)

Template:GLJMELinks

2015-03-11T05:27:04Z

Aebrown: Reverted edits by Aebrown (talk) to last revision by Timriker

<div style="border: 1px solid black; padding: 10px; margin: 10px; background-color: #F2F3E5; font-size: x-small; float:right;">
<span style="font-size: medium; font-weight: bold">Research Links</span>
* [[Gospel Library for JavaME: Phone Types and Capabilities | Phone Types and Capabilities]]
* [[Gospel Library for JavaME:_Cell_Phone_Carriers | Cell Phone Carriers]]
* [[Gospel Library for JavaME:_App_Distribution_Methods | App Distribution Methods]]
* [[Gospel Library for JavaME:_Interesting_Articles | Interesting Articles on Cell Phones and Apps]]
* [[Gospel Library for JavaME:_Cross_Platform_and_Multi-language| Cross Platform and Multi-language Development]]
* [[Gospel Library for JavaME | Gospel Library for JavaME home]]
</div><noinclude>{{tempmain|Gospel Library for JavaME}}
== Purpose ==
This template is an infobox for research-oriented links for [[Gospel Library for JavaME]] articles. It will help readers navigate between related articles.

== Usage ==
This template has no parameters. The template should be added to relevant articles by inserting {{tl|GLJMELinks}} at the very top of the article code.

== Categorization ==
Articles that transclude this template will automatically be categorized in [[:Category:Gospel Library for JavaME]].
[[Category:Index box templates|GLJMELinks]]
</noinclude><includeonly>[[Category:Gospel Library for JavaME]]</includeonly>

Template:GLJMELinks

2015-03-11T05:11:30Z

Aebrown: Add sort key to category

User talk:Wbernal

2015-02-24T14:49:25Z

Aebrown: format, respond

== Access to youth names in other wards ==
Would it be possible on LDS tools app to have the Stake leaders like myself (stake YM's)to have access to the names of the Youth from all wards? Given that most families have pictures up it sure would be nice when visiting new wards to put names with faces to some of the kids that we see and teach. Yes, we need to get out there and introduce ourselves but it makes a good impression on someone when you can walk up to them and call them by name. is there anyway to enable that information? -- [[User:Wbernal|Wbernal]] 14:25, 23 February 2015‎

: First of all, questions should be asked in a talk (discussion) page, so I moved your question to your User Talk page.

: As for your question, hardly anyone will see it here on the wiki. You're much better off posting it in the LDSTech Forum, probably in the [https://tech.lds.org/forum/viewforum.php?f=115# LDS Tools] or [https://tech.lds.org/forum/viewforum.php?f=111# Directory] forum section (the access rules are the same for both the Directory and LDS Tools). You also might want to review existing discussions for this issue, such as [https://tech.lds.org/forum/viewtopic.php?f=111&t=20444 Member Directory] or [https://tech.lds.org/forum/viewtopic.php?p=101081#p101081 Stake YM/YW Visibility to Unit Youth and Calendars]. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 07:49, 24 February 2015 (MST)

User:Wbernal

2015-02-24T14:40:06Z

Aebrown: Aebrown moved page User:Wbernal to User talk:Wbernal: discussions belong in the Talk namespace

#REDIRECT [[User talk:Wbernal]]

User talk:Wbernal

2015-02-24T14:40:06Z

Aebrown: Aebrown moved page User:Wbernal to User talk:Wbernal: discussions belong in the Talk namespace

Would it be possible on LDS tools app to have the Stake leaders like myself (stake YM's)to have access to the names of the Youth from all wards? Given that most families have pictures up it sure would be nice when visiting new wards to put names with faces to some of the kids that we see and teach. Yes, we need to get out there and introduce ourselves but it makes a good impression on someone when you can walk up to them and call them by name. is there anyway to enable that information?

User:Aebrown/Sandbox

2015-02-12T16:02:01Z

Aebrown:

This is my primary sandbox, where I test out various proposed features or pages, or experiment with wiki syntax.

== Response when users post to main namespace ==
: First of all, please don't ask questions in the main namespace of the wiki -- that is reserved for actual articles. Questions should only be asked in a Talk (discussion) namespace. So I moved your question to your user talk page.

: Second, you'll get much better answers if you ask questions like these on the LDSTech Forum. So I'd recommend that you post your question in the [https://tech.lds.org/forum/viewforum.php?f=92 LDS Account] forum section. Many more people will see your question there. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 23:41, 21 January 2015 (MST)

== Images ==
[[Image:LDS-Account-registration.png|thumb|LDS Account registration screen]]This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...This image should float right by default. But it doesn't currently. This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...

This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...This image should float right by default. But it doesn't currently. This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...

== Statistics ==
* Articles: {{NUMBEROFARTICLES}}
* Pages: {{NUMBEROFPAGES}}
* Pages in Projects category: {{PAGESINCAT:Projects}}

== Parser functions ==
* <nowiki>{{#ifeq: 1 | 1 | yes | no}}</nowiki>: {{#ifeq: 1 | 1 | yes | no}}
* <nowiki>{{#ifeq: 1 | 2 | yes | no}}</nowiki>: {{#ifeq: 1 | 2 | yes | no}}
* <nowiki>{{#ifexist: Main_Page | yes | no}}</nowiki>: {{#ifexist: Main_Page | yes | no}}
* <nowiki>{{#ifexist: Main Page | yes | no}}</nowiki>: {{#ifexist: Main Page | yes | no}}
* <nowiki>{{#ifexist: xyzzy | yes | no}}</nowiki>: {{#ifexist: xyzzy | yes | no}}

== Sub-sub page ==
[[User:Aebrown/Sandbox/subpage]]

== Langlink template ==
El {{langlink|es|stake technology specialist|especialista en tecnología}} es responsable de:

... mantener y apoyar las {{langlink|es|Printing|impresora}} y equipos ...

=== Translation of system messages ===
* en: {{MediaWiki:Otherlanguages}}
* de: {{MediaWiki:Otherlanguages/de}}
* es: {{MediaWiki:Otherlanguages/es}}
* fr: {{MediaWiki:Otherlanguages/fr}}

=== Conditional system messages ===
* Link to Spanish page: [[User:Aebrown/es]]
* Link to English page: [[User:Aebrown/en]]

== Table classes ==
{| class="wikitable"
|+ Test table
! Head 1
! Head 2
|-
| R1C1
| R1C2
|-
| R2C1
| R2C2
|}

=== Vertical alignment ===

{| border="1"
|+ Test table
! Head 1
! Head 2
|-
| R1C1
| R1C2
2
3
4
|- valign="top"
| R2C1
| R2C2
2
3
4
|}

== Linked image ==
<div style="border: 1px solid gray; padding:1px; width: {{#expr:175+4}}px; float:right; margin: 10px;">
<div style="padding: 2px; text-align:center; margin:auto; ">[[File:Firmanualthumb.png|link={{Filepath:FIR Documentation 120329 1.pdf}}|175px]]<br> Click to view the FIR user manual (PDF)</div>
</div> This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...This image should float right by default. But it doesn't currently. This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...

User:Jessepromise

2015-02-09T23:03:28Z

Aebrown: Constrain photo size

===TECH LOVER===
[[file:Jesse.jpg|300px]]
;E-mail
:jessepromise@yahoo.com
;Website
:jessepromise.blogspot.com

===LOCATION===
Nigeria

User:Grandpasvedin

2015-02-05T03:25:53Z

Aebrown:

Walter Stephen Svedin<br>
Live in Nampa Idaho<br>
Phone # - 208-941-3689

Real life Job - Horticulturalist (Gardener)

User talk:Janicerose

2015-01-12T14:39:37Z

Aebrown: format and respond

I LOVED! being able to do the following on the LDS Scriptures app:
* Highlight text
* Put notes by the text
* Tag paragraphs or scriptures to a topic
* Cross reference scriptures

When will Gospel Library allow me to do these things?<br>
Jan

: You can do almost all of that right now. The cross-referencing is a bit weak, but the other three things are all in place. I use them all the time on my Android Gospel Library.

: But in any case, hardly anyone sees discussions on the wiki. You will get a much better discussion if you post on the LDSTech Forum, in the [https://tech.lds.org/forum/viewforum.php?f=101# Gospel Library] forum or one of its subforums, depending on your device. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 07:39, 12 January 2015 (MST)

User:Swtbentley/Sandbox

2014-11-25T20:30:41Z

Aebrown: Created page with "== Elder Bentley's Sandbox == Test pages in the Sandbox: * Test Page"

== Elder Bentley's Sandbox ==

Test pages in the Sandbox:
* [[User:Swtbentley/Sandbox/Test Page|Test Page]]

User:Swtbentley/Sandbox/Test Page

2014-11-25T20:27:30Z

Aebrown: Example of how to create a Sandbox page

Elder Bentley's test page.

Installing MarkLogic

2014-11-14T06:04:38Z

Aebrown: Add category

== Installing MarkLogic on Windows ==

(These instructions are for Windows XP, Vista, and 7. Installation and server start-up may differ slightly for other operating systems.)

# [http://developer.marklogic.com/products Download] the latest version of the MarkLogic Server for your operating system.
#* Upon clicking on the download link, you will need to agree to MarkLogic's Terms of Use.
# Execute the MarkLogic Server installer.
#* Choose a "Typical" setup. This will take about 5 minutes.
# After installation is complete start the Mark Logic Server.
#* (Windows Only) Go to Start > All Programs > MarkLogic Server > Start MarkLogic Server
#** Important! Right-click on "Start MarkLogic Server" and select "Run as administrator". Otherwise, the server may not start.
#** If you get the error message "The application failed to initialize properly...", then see [http://developer.marklogic.com/products/marklogic-server/requirements MarkLogic Server 4.x System Requirements] to download and install the necessary dll for your operating system. Then try starting the server again.
#** If start-up succeeds, you will not see any message.
# Go to the Mark Logic administration console:
#* (Windows Only) Go to Start > All Program > MarkLogic Server > Admin MarkLogic Server.
#* A browser window will open and you will be prompted to enter a license key.
#** If you do not yet have a license, do one of the following:
#*** (Employees Only) Request a license key by emailing [mailto:DL-ICS-MARKLOGIC DL-ICS-MARKLOGIC].
#**** Enter the licensee and the license key, then click "OK". The MarkLogic Server will restart.
#*** (Non-employees Only) You may request a free license for community development by clicking the "Free" button and then entering the required information in the supplied form.
#**** '''Licensee'''. This is '''your''' name.
#**** '''Company'''. ''Do NOT put the name of the Church or any of its business entities in this field.'' You may put "Home" or "Community" in this field if you will be using the MarkLogic Server for personal or community development.
#**** '''Email'''. This is your personal email address.
#**** Choose "Select Community License".
#**** Make a copy of your license information and then click "OK". The MarkLogic Server will restart.
#* Accept the license agreement by scrolling to the bottom of the page and clicking "Accept". The MarkLogic Server will restart.
#* You will now be prompted to install the initial databases and application servers. Click "OK" to continue. When installation is complete. The server will restart.
#* When prompted to enter an Admin username and password, enter "admin" as the user and "admin" as the password. Confirm the password and click "OK" to continue.
#* When prompted, enter the user name and password you supplied. You will then be redirected to the MarkLogic Server administration console.
# Configure an XDBC server
#* Expand "Groups", then expand "Default", and then select "App Servers".
#*; <br/>[[File:marklogic-admin-step1.png]]<br/><br/>
#* Click the tab "Create XDBC"
#** Supply an XDBC server name.
#*** For the Stack Petstore project, enter "stack-petstore".
#** Supply a value for the module directory root.
#*** For the Stack Petstore project, enter "/".
#** Supply a value for the port the XDBC server will listen to for connections.
#*** For the Stack Petstore project, enter "8010".
#** For the modules field, choose "Modules" from the list of options.
#** Leave all other fields as they are, and click "OK" at the top of the page.
#*; <br/>[[File:marklogic-admin-step2.png]]<br/><br/>
# To try out your Mark Logic installation, go to [http://localhost:8000 <nowiki>http://localhost:8000</nowiki>] and login with your admin username.

[[Category:MarkLogic]]

What is MarkLogic?

2014-11-14T06:02:39Z

Aebrown: Fix category

== What is MarkLogic? ==
[http://www.marklogic.com/what-is-marklogic/ MarkLogic] is a [http://www.marklogic.com/what-is-marklogic/inside-marklogic/ '''REST application server''', '''document database''', and '''search engine''']. It is REST through and through. It is built specifically for hypertext documents, links, metadata, URIs, MIME types, and HTTP. It is schema-agnostic because it is automatically aware of the independent structure of each of its JSON and XML documents. It is search-centric because it can search for ''any combination'' of words, values, structures, and links within and across documents. It scales horizontally to hundreds of servers within and between data centers while maintaining ACID-compliant transactions.

MarkLogic has the following [http://www.marklogic.com/what-is-marklogic/enterprise-nosql/ enterprise features]:
* [http://www.marklogic.com/resources/java-developers-guide/ Java APIs]
* [http://en.wikipedia.org/wiki/Node.js Node.js APIs]
* [http://developer.marklogic.com/learn/2009-07-search-api-walkthrough Search] and [http://developer.marklogic.com/learn/arch/search-and-indexing Query]
* [http://www.marklogic.com/blog/can-you-pass-the-acid-test/ ACID Transactions]
* [http://www.marklogic.com/resources/marklogic-high-availability-and-disaster-recovery/resource_download/datasheets/ High Availability] and [http://docs.marklogic.com/guide/database-replication/dbrep_intro#chapter Disaster Recovery]
* [http://www.marklogic.com/resources/marklogic-flexible-replication/resource_download/datasheets/ Replication within and across data centers]
* [http://docs.marklogic.com/guide/admin/security#chapter Government-grade Security]
* [https://docs.marklogic.com/guide/cluster.pdf Scalability] and [https://docs.marklogic.com/guide/admin/database-rebalancing#chapter Elasticity]
* [https://docs.marklogic.com/guide/ec2/managing#chapter On-premise or Cloud Deployment (especially AWS)]
* [http://www.marklogic.com/resources/marklogic-and-hadoop/resource_download/datasheets/ Hadoop for Storage and Compute]
* [http://www.marklogic.com/resources/marklogic-semantics-mlw14/ Semantics]

== What is REST? ==
REST is an architectural style that uses a uniform resource identifier ('''URI''') and a web protocol ('''HTTP/HTTPS''') to request and transfer a representation ('''MIME media type''') of the state of a resource ('''document''') at a point in time from a server to a client.

REST was coined and defined by Roy Fielding in his
[http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm dissertation, ''Architectural Styles and the Design of Network-based Software Architectures'']. REST standardizes and documents the patterns used in the world wide web: self-documenting hypertext with data and metadata (HTML), stateless request/response communication protocol (HTTP/HTTPS), resource locators (URL), multiple representations per URL (MIME types), and downloading code on demand to process resources (JavaScript, CSS, etc.).

REST consists of three main concepts:
* (RE) Representation
* (S) State
* (T) Transfer

== Why is MarkLogic RESTful? ==

=== '''Representation and MarkLogic''' ===
* A representation is a document that represents a resource. It has three requirements: MIME media type, URI, and hypertext.

* '''MIME type:''' Each resource can be represented by one or more types of documents. The MIME media type defines the representation a client requests. A client may request the resource to be represented as JSON, XML, HTML, PNG, PDF, etc.
**'''MarkLogic''' stores any type of document and assigns the appropriate [http://developer.marklogic.com/blog/document-formats-part2 MIME type] to it. It can fully index, query, search, and process JSON, XML, and RDF documents. It meets the REST requirement of being able to transform JSON, XML, and RDF documents into any other MIME type. It knows how to execute JavaScript, XQuery, XSLT, and SPARQL documents. It knows how [http://docs.marklogic.com/guide/cpf/default#chapter to transform into XHTML] the content, formatting, and structure of Microsoft Word, PowerPoint, Excel, textual PDF, DocBook, and CSS documents. (It can also use Microsoft Office to create, edit, and manage content in MarkLogic.) It knows how to [https://docs.marklogic.com/guide/search-dev/binary-document-metadata extract metadata and text from over 138 types of binary documents], such as raster images, vector images, videos, archive files, database files, encoded emails, presentations, spreadsheets, word-processing documents, text formats.
**Few NoSQL databases use MIME types to identify the media type of each document. Most NoSQL databases support only one type of data and it is usually proprietary: columnar, BSON, binary, etc. Most cannot transform from one MIME type to another.

* '''URI:''' A resource is identified by a globally unique identifier (URI). '''MarkLogic''' identifies each document with a [http://developer.marklogic.com/try/rest/page2 unique URI]. A document in MarkLogic is like a row in a table in a schema in a relational database. A URI is liberating. It provides random access to any resource anywhere. It is like being able to retrieve any row in any table in any schema of a relational database without having to know what table and schema the row is stored in.
**Navigating URL hierarchy is fundamental to REST. MarkLogic understands the hierarchy within a URI, which is represented by slashes "/", such as https://www.lds.org/scriptures/ot/gen/1 MarkLogic treats the items between the slashes as folders. The URI of each document automatically places it in a folder in a folder hierarchy. A URI automatically defines the folder hierarchy. In the example URI above, the document for Genesis chapter 1, is located in the Genesis folder, which is located in the Old Testament folder, which is located in the Scriptures folder on lds.org. '''MarkLogic''' indexes the documents in each folder and its subfolders. This makes it fast and easy to retrieve any or all documents in any folder and/or its subfolders.
**Few NoSQL databases use the URI as the primary key for their documents or data. They also don't index the URI hierarchically to filter documents by folder and subfolder.

* '''Hypertext:''' A document should contain data that represents the resource. The data should be '''human readable and self-documenting''', like JSON, XML, RDF, and HTML. It should be '''linked data''' (i.e. the "hyper" in "hypertext"). A document should contain ''' metadata links''' about the resource, such as RDF. It should contain '''action links''' to define what further actions can be done with the resource. It should contain '''related links''' to related resources, such as images, audio, video, related documents, etc. Each related link should define what actions can be done with the referenced resource, such as download it, display a link to it, execute a command against it, etc.)
**'''Hypertext''' or '''hypermedia''' documents must have all these features. Hyperlinks are what the "hyper" in hypertext and hypermedia refers to. You can't have REST without ''metadata links'' to define what the data means, ''action links'' to know how to work with the resource, and ''related links'' to connect resources. It should all be human readable and self-documenting so a developer does not have to read documentation to know how to interact with a REST web service and its documents.
** '''MarkLogic''' meets all the requirements for hypertext representation. It is designed around MIME types, URIs, and Linked data. It stores documents with their MIME types as [http://www.w3schools.com/json/ JSON], [http://www.w3schools.com/xml/ XML], [http://www.w3schools.com/webservices/ws_rdf_intro.asp RDF], [http://www.w3schools.com/html/ HTML], etc. These documents are human-readable and self-documenting, which MarkLogic leverages to recognize and index each document's data, data structure, metadata links, action links, and related links. This makes it easy to '''search''', '''query''', '''transform''', and '''deliver''' hypertext documents. MarkLogic can also store any type of binary document and deliver it as a related resource, such as an image, video, or audio. MarkLogic is designed to process simple links and RDF links using [http://en.wikipedia.org/wiki/SPARQL SPARQL] and [https://docs.marklogic.com/xinc XInclude]. MarkLogic can represent links in many formats: [https://docs.marklogic.com/xp XPointer], [https://docs.marklogic.com/guide/semantics/loading#id_97709 RDF/XML], [https://docs.marklogic.com/guide/semantics/loading#id_79194 RDF/JSON], [https://docs.marklogic.com/guide/semantics/loading#id_73211 Turtle], [https://docs.marklogic.com/guide/semantics/loading#id_70596 N-Triples], [https://docs.marklogic.com/guide/semantics/loading#id_61596 N-Quads], and [https://docs.marklogic.com/guide/semantics/loading#id_74485 TriG].
**No other NoSQL database natively indexes and fully processes all the document types required for REST hypertext: JSON, XML, RDF, HTML, CSS, and JavaScript.

=== '''State and MarkLogic''' ===
* State in REST exists on the client and in server documents. It does not exist in the communications protocol or in the server as cached session data.

* '''Server:''' All information needed to process a request must be presented in the request and processed against documents in the database. State must only be in the request and in database documents: state cannot be anywhere else, such as in a session cache. The documents in the server define the state of the server. A REST server should explicitly create a state machine that defines the acceptable actions that can transacted against documents in specific contexts.
**A REST transaction occurs at a '''point in time'''. The state of the data in the request is unchanging, but the state of the documents and state machines in the database are often changing. Since request state and database state are both required to process the request and since shifting state creates unpredictable results, a REST transaction should run at a point in time with unchanging state. Only an ACID-compliant database can ensure consistent state because it isolates each transaction from every other transaction. The only time REST does not need an ACID-compliant database is when database documents do not change, database state machines do not change, or when clients can live with the resultant level of unreliable and unpredictable results.
**'''MarkLogic''' meets all the requirements for REST state. Its web services are stateless: there is no session cache. It is ACID compliant. It ensures each transaction occurs at a point in time and is isolated from all other transactions. This ensures consistent processing during a transaction -- even across billions of documents. MarkLogic is an [http://en.wikipedia.org/wiki/Multiversion_concurrency_control MVCC] database which provides transaction isolation without slowing the performance of reads -- even when documents being read are being modified simultaneously by other transactions. (Also, like any other ACID database, when multiple updates and deletes compete for the same documents, they will impact each other's performance because change has to be serialized.)
** Most other NoSQL databases are not ACID compliant. They are only suitable for REST services when their documents or data do not change or when the rate of change is slow enough or dispersed enough that it creates an acceptable level of unreliability and unpredictability.

* '''Client:''' A REST client, such as a web browser or spider, locally maintains transactional state, such as what to do in response to documents and result codes that are returned from server transactions. An application exists only in the client -- not in the server (although, a server may deliver application code to a client, such as when a web server downloads HTML, CSS, and JavaScript to a browser). Client application code decides when to execute web service calls and it ties the results together to accomplish its purpose. This allows multiple authorized applications to reuse web services for a variety of purposes.
**The server helps the client know what web service calls are available by providing action links with each response. Action links are contextual and the context is based on the application account, user account, database documents, links within and between documents, the server state machine, etc. Through action links, the server can inform a client application what web service calls are permissible in any given context.
**'''MarkLogic''' meets the needs of client applications through its built-in ability to process and send action links to clients based on context. MarkLogic supports RDF triples and SPARQL, which enables context to be defined across applications, users, document state, links between documents, server state machine, etc. MarkLogic processes triples very quickly, which enables context to scale to billions of documents, millions of users, etc.
**'''MarkLogic''' also uses application and user permissions to filter which documents are returned to clients. MarkLogic does this automatically and transparently by adding security filtering constraints into every search and query. This ensures no account can access unauthorized documents. This is fast because all security permissions are built-into MarkLogic's indexes -- which allows document-level security to scale across billions of documents.
** Most other NoSQL databases do not provide government-grade, document-level security and they also do not support RDF triples and SPARQL.

Because MarkLogic can provide both the web service and database in one server, it is easy to use the state of the documents and the

=== '''Transfer and MarkLogic''' ===
* '''Transfer''' in REST is a communication protocol that enables a client to send a hypertext request to a server and receive back a hypertext response. The transfer must be stateless and be a request/response protocol. It must have human readable, self-descriptive headers. The header must contain metadata about the request, such as the requested resource URI, MIME type of the resource, action to perform on the resource (such as get, put, post, patch, and delete). [http://www.w3schools.com/tags/ref_httpmethods.asp '''HTTP'''] (Hypertext transfer protocol) and '''HTTPS''' (secure HTTP) are designed specifically for REST (that is why they have "hypertext" in their name).

* All '''MarkLogic''' communication is through through HTTP and HTTPS REST services (except for its SQL JDBC feature). This includes all internal cluster communication. MarkLogic provides out-of-the-box REST interfaces for manipulating resources (insert, update, delete, query, search, transform, etc.) and administering MarkLogic (REST app servers, databases, indexes, clusters, etc). MarkLogic makes it very easy to create custom REST services because everything in MarkLogic is built around REST and because they provide simple and powerful application server APIs.

== MarkLogic Query and Search ==
MarkLogic is unlike relational databases (and a few NoSQL databases) where they use full table scans to retrieve every row in the table unless a query accesses less than 20% of the rows and then they use an index. MarkLogic does not do full table scans. It needs all queries to be resolved out of the indexes. For that reason, it indexes most things and allows you to index more.

MarkLogic can query and search -- and use both in combination. MarkLogic uses indexes to execute searches and queries. The same indexes are used for both. The difference between search and query is how documents are sorted. Searches sort by relevance and queries sort by values. MarkLogic uses indexes to extract words, values, structures, and links out of documents.

This enables you to search and query for documents as if they contained only
*'''Words:''' a flat set of words without structure, such as <br><code>["Mary" "had", "a", "little", "lamb"]</code>
*'''Phrases:''' a flat set of phrases without structure, such as <br><code>["Mary had", "had a", "a little", "little lamb"]</code>
*'''Elements:''' a flat set of elements without values, such as <br><code>["poem", "text", "line"]</code>
*'''Element-values:''' a flat set of elements with string values, such as <br><code>"line": "Mary had a little lamb"</code>
*'''Element-words:''' a flat set of elements with words, such as <br><code>"line": ["Mary" "had", "a", "little", "lamb"]</code>
*'''Element-phrases:''' a flat set of elements with phrases, such as <br><code>"line": ["Mary had", "had a", "a little", "little lamb"]</code>
*'''Element-value lexicon:''' a flat set of elements with typed values, such as <br><code>"lineSequence": 3</code><br> or a list, count, or co-occurrence of element values scoped to a database, set of documents, or one document.
*'''XPath-structure-value lexicon:''' a flat set of hierarchical elements with typed values, such as <br><code>poem.text.line.lineSequence: 3</code><br> or a list, count, or co-occurrence of hierarchical element values scoped to a database, set of documents, or one document.
*'''XPath-structure:'''hierarchical structures without values, such as <br><code>poem.text.line</code>
*'''XPath-structure-words:''' hierarchical structures with words, such as <br><code>poem.text.line: ["Mary", "had", "a", "little", "lamb"]</code>
*'''XPath-structure-phrases:''' hierarchical structures with phrases, such as <br><code>poem.text.line: ["Mary had", "had a", "a little", "little lamb"]</code>
*'''XPath-structure-values:''' hierarchical structures with values, such as <br><code>poem.text.line: "Mary had a little lamb"</code>
*'''RDF document links''' to other documents, such as <br><code>{"subject": "http://example.org/documents/thisDoc", "predicate": "http://example.org/predicates/relatesSomehowTo", "object": "http://example.org/documents/thatDoc"}</code>
*'''RDF abstract links''' to other abstract concepts, such as <br><code>{"subject": "http://example.org/documents/thisDoc", "predicate": "http://example.org/predicates/relatesSomehowTo", "object": "http://example.org/documents/someConceptWithNoDocumentAtTheURI"}</code>
*'''RDF data links''' to data, such as <br><code>{"subject": "http://example.org/documents/thisDoc", "predicate": "http://example.org/predicates/ageInYears", "object": 12}</code>

MarkLogic can combine any of these indexes in any way to find matching documents. It can sort the result by relevance or by value.

The [[MarkLogic Query and Search]] page provides more detail about how MarkLogic's unique indexes work and how they work together.

[[Category:MarkLogic]]

Glossary

2014-11-10T18:19:48Z

Aebrown: Simplify recent edits; remove grammatical errors.

{{A2ZTOC}}
== A ==
;Active : Participating on a regular basis, such as attending meetings, observing the principles of the gospel, and accepting Church callings; Under current Church policy, those who attend meetings at least once a month.

; AD - Active Directory
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments. AD (also known as EAD) stores information and settings relating to an organization in a central, organized, accessible database.

; AF - Ancestral File
: A database containing family history information contributed by members of the Church and others from 1979 to 1999. The file contains millions of names linked in family groups and pedigrees. Ancestral File data may be accessed on FamilySearch.org.

;Agent Bishop : The Bishop responsible for a meetinghouse when that building has multiple wards.

; AJAX - Asynchronous JavaScript and XML
: AJAX is a Web development technique for creating interactive Web applications. It exchanges small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change.

; API - Application Programming Interface
: An application programming interface (API) is a source code interface that a computer library provides to support requests to be made of it by a computer program.
: [http://en.wikipedia.org/wiki/Application_programming_interface Wikipedia Definition]

;Area : A geographical administrative region of many stakes and missions, usually including hundreds of thousands of members. Areas often cover many nations and are presided over by either a General Authority or an Area Authority Seventy.

;Area Presidency : A Presidency of general or regional leaders who preside over an area of the Church.

;Area President : A general or regional leader, a General Authority or Area Authority Seventy, who presides over an area of the Church.

; ASA
: Church-managed Cisco ASA 5505 firewall used for meetinghouse Internet connections.

; ASCII
: American Standard Code for Information Interchange. A standard definition employing characters that can be read without conversion.

; ASE - Application Service Engineer

; ASP - Active Server Pages
: ASP is Microsoft's server-side script engine for dynamically-generated Web pages. Programming ASP Web sites is made easier by various built-in objects.
: [http://en.wikipedia.org/wiki/Active_Server_Pages Wikipedia Definition]

;Auxiliary Organizations : Organizations in a ward that do not include the priesthood quorums. These organizations include the Relief Society, Primary, Young Women, Young Men, and Sunday School.

== B ==
; B2B - Business-to-Business
: Business-to-business (or B2B for short) is a marketing strategy that involves the transaction of goods or services between businesses (as opposed to relations between businesses and other groups, such as consumers or public administration).
: [http://en.wikipedia.org/wiki/B2B Wikipedia Definition]

; B2C - Business-to-Consumer
: B2C (also business-to-customer) describes activities of commercial organization serving the end consumer with products and services.
: [http://en.wikipedia.org/wiki/B2C Wikipedia Definition]

; B2E - Business-to-Employee
: B2E uses an intrabusiness network that allows companies to provide products and services to their employees. Typically, companies use B2E networks to automate employee-related corporate business.
: [http://en.wikipedia.org/wiki/B2E Wikipedia Definition]

;Baptism : The initial saving ordinance performed on those who have joined the Church or who have reached the age of eight, characterized by immersing the person completely in water. Baptisms therefore need to be recorded on Membership records.

; BI - Business Intelligence
: BI is a broad category of applications and technologies for gathering, providing access to, and anlyzing data for the purpose of helping enterprise users make better business decisions.
: [http://en.wikipedia.org/wiki/Business_Intelligence Wikipedia Definition]

;Bishop : A priesthood leader responsible for the spiritual and temporal welfare of a ward. Bishops preside over most ward functions and activities, interview members of their wards for worthiness, call members of their ward to callings within the ward and oversee efforts to provide for ward members unable to provide for themselves.

;Block Schedule : A schedule of Sunday meetings that takes place in a three-hour period. The block schedule contains the sacrament meeting and Melchizedek Priesthood, Aaronic Priesthood, Relief Society, Young Women, Primary, and Sunday school meetings. See ''Handbook 2: Administering the Church'', section [http://lds.org/handbook/handbook-2-administering-the-church/meetings-in-the-church 18] for timing and sequence of meetings.

; Blog - Web Log
: A blog is a Web site where entries are made in journal style and displayed in reverse chronological order.
: [http://en.wikipedia.org/wiki/Blog Wikipedia Definition]

; BO - BusinessObjects
: Enterprise software that is used for business intelligence.

; Born in the Covenant (BIC) : A child who is born in the covenant does not have to be sealed to the parents. A child whose parents were sealed to one another in the temple before the child was born is BIC. A child born after the mother's sealing to her husband is canceled is not BIC. A child born after one of the parents is excommunicated is not BIC.

;Branch : The smallest organized unit of the Church. A congregation not large enough to be made into a ward, or not in an area with enough members to make a stake.

;Branch Clerk : A priesthood leader responsible for the administrative functions of a branch; generally managing the membership and financial records of a branch.

;Branch President : The priesthood holder called and set apart to lead a branch.

;Bulletin : (a k a Ward Bulletin or Sacrament Meeting Program) The printed listing of planned prayers, talks and other sacrament meeting elements passed out at the beginning of each Sacrament Meeting in most LDS congregations.

== C ==
;CAB : Church Administration Building

;Calling : An office or assignment in the Church; An invitation to accept an office or assignment in the Church.

; CCN - Church Communications Network
: The Church's global network.

;[[CDOL]] : Church Directory of Organizations and Leaders

; CES - Church Educational System : The '''Church Educational System (CES)''' serves as the umbrella for all education programs of the Church, including Church-owned universities and colleges, institutes of religion, and seminary programs worldwide.

;CFAR : ''Obsolete''. See CUBS.

;CHI : ''Obsolete''. See Handbook.

;CHQ : Church Headquarters

;Church Handbook of Instructions : ''Obsolete''. See Handbook.

;Clerk : A priesthood holder responsible for tracking financial and membership information and maintaining the associated records.

;Clerk's Office : The room in an LDS meetinghouse or stake center that is used by the Clerks. The room where a unit's financial and membership transactions are made and the associated records are kept.

;COB : Church Office Building

;Confirmation : An ordinance performed after baptism whereby a person becomes a member of The Church of Jesus Christ of Latter-day Saints. This ordinance is performed under the direction of the bishop. One or more Melchizedek Priesthood holders place their hands on the person’s head and confirm them as a member of The Church of Jesus Christ of Latter-day Saints and use the wording “Receive the Holy Ghost.” May also pronounce a blessing as inspired by the Holy Ghost. Confirmation for eight-year-old [[members of record]] is performed at the baptism. Confirmation for converts is performed at a sacrament meeting on a Sunday following the baptism.

;[[Consolidated Financial Statement]] : Monthly summary for the stake of all units' financial activity.

;Convert
: An individual nine years of age or older who is baptized and confirmed a member of the Church, or an eight-year-old whose parents are not members or are being baptized at the same time. Individuals under the age of eighteen must have the permission of both parents before being baptized.

; COTS - Commercial Off-the-Shelf
: COTS is a term for software or hardware products that are ready-made and available for sale, lease, or license to the general public. They are often used as alternatives to in-house development projects.
: [http://en.wikipedia.org/wiki/Commercial_off-the-shelf Wikipedia Definition]

;Court : ''Obsolete''. See Disciplinary Council

; CRM - Customer Relationship Management
: CRM is a broad term that covers concepts used by companies to manage their relationships with customers, including the capture, storage, and analysis of customer information.
: [http://en.wikipedia.org/wiki/Customer_relationship_management Wikipedia Definition]

;CUBS - Church Unit Banking Services
: Introduced in 2010, a worldwide back office system used by administrative offices for financial record-keeping. Over time, all regions will transition from CFAR or LURBS to CUBS.

;CUFS : [[Church Unit Financial Statement]] (Bank Statement) This has been replaced by the Unit Financial Statement.

== D ==
;Disciplinary Council : A council of local leaders and other priesthood holders held to review the inappropriate behavior of a Church member and to decide on appropriate consequences. Councils may also be reconvened after a period of time to see if a member has repented sufficiently to be restored to full fellowship. See chapter 6 of ''Handbook 1: Stake Presidents and Bishops'' for details.

;District : A district is a smaller version of a stake, organized as the parent unit of branches instead of wards. A district may be organized when there are enough branches in an area to allow easy communication and convenient travel to district meetings. A district president presides over the district and reports to the mission presidency.

;District Clerk : Person responsible for all clerical activities in a district.

;District President : The district president presides over the district and is assisted by two counselors. The district president reports to and receives direction from the mission president.

; DIZ - Development Integration Zone

== E ==
; EAD - Enterprise Active Directory
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments (also known as AD) stores information and settings relating to an organization in a central, organized, accessible database.
: [http://en.wikipedia.org/wiki/Active_Directory Wikipedia Definition]

; EFD - Exploration Findings Document
: This document is used to identify possible solutions for a specific project.

;Elders Quorum : A quorum in the Church is a combination of a class, a fraternity of brethren, and a service organization. An elders quorum is a group of brethren in a ward consisting of up to 96 elders. After this number is reached, the quorum may be divided under direction of the stake president.

;Elders Quorum President : The elders quorum in a ward is presided over by an elders quorum president and two counselors.

;Endowment : Instruction received in the temple pertaining to the purposes and plans of the Lord in creating and peopling the earth and in exalting his children in the life to come.

;Equalized Contribution : Refers to the support from the General Missionary Fund that results in each missionary serving from a specific country contributing the same amount irrespective of where in the world they serve.

;ERC : Employment Resource Center

; ERS - [http://providentliving.org/content/list/0,11664,1962-1,00.html Employment Resource Services]

; EUP - End-User Productivity

== F ==
;Family History Center : A Family History Center is a branch facility of the Family History Library in Salt Lake City. It contains staff to help patrons identify their ancestors through the use of computer programs and microfilms and microfiche that may be ordered from the Family History Library.

;Fast Offering : Fast offerings are funds freely given monthly by members of the Church to help the needy. As a general guideline members fast for two meals and contribute the cash equivalent of the cost of the two meals to the Church. The use of fast offerings is at the discretion of the bishop under the direction of the stake president.

; FCH - Family and Church History Department

;FHC : Family History Center

; FHL - [http://www.familysearch.org/Eng/Library/FHL/frameset_library.asp Family History Library]

;[[Financial Clerk]] : Person responsible for financial matters in the unit.

; FIR - Facility Issue Reporting : The FIR system provides LDS Church leaders, building representatives, and facilities management groups the ability to report and review facility issues electronically. It uses a web interface to streamline reporting, viewing, and resolving of facility issues.

;FIS : Old DOS-based local unit financial software that is no longer used. See [[MLS]] for current software.

;FM Group : Facilities Management Group

; FWIW - For What It's Worth

== G ==
;General Handbook of Instructions : ''Obsolete''. See Handbook.

;[[Geo code]] : A code used to group members into geographic areas, usually to analyze how a unit might be divided.

;GHI : General Handbook of Instructions. ''Obsolete''. See Handbook.

; GIDS - Global Identity Services
: Project to create LDS Sign-in.

; GIS - Geographic Information System
: A geographic information system (GIS) is a system for capturing, storing, analyzing, and managing data and associated attributes which are spatially referenced to the earth.
: [http://en.wikipedia.org/wiki/Gis Wikipedia Definition]

; GSC - [[Global Service Center]]
: The GSC enables Directors of Temporal Affairs and Managing Directors to focus on their most important work by providing efficient transaction processing. They make gospel teachings, resources, and services directly and globally accessible in a self-service, scalable, affordable way. They help with questions and problems related to things such as IT support, Distribution Services, and clerk and leader issues.

; GSD - Global Service Desk
: Former name for the Global Service Center (GSC).

== H ==
;Handbook : The policy manual for administering the Church, consisting of two volumes: ''Handbook 1: Bishops and Stake Presidents'' and ''[http://lds.org/handbook/handbook-2-administering-the-church Handbook 2: Administering the Church]''.

;High Priests Group : The stake president presides over the stake quorum of high priests, made up of all the high priests in the stake. The quorum is divided at the ward level into individual high priests groups.

;High Priests Group Leader : The high priest group in a ward is presided over by a high priest group leader and two assistants. Under the bishopric’s direction, the high priests group leader coordinates temple and family history work in the ward.

;[[Annual History|Historical Specialist]] : Clerk responsible for preparing the [[Annual_History|annual historical reports]].

;Home Teacher : Home teachers are priesthood brethren who are assigned families at the ward level to visit monthly, to help and to strengthen. They are assigned by priesthood leaders.

;Home Teaching : Home teaching is the responsibility of all Melchizedek Priesthood holders and of those who are teachers and priests in the Aaronic Priesthood. As part of their responsibility to watch over the members of the Church, home teachers visit their assigned families at least once each month to teach and strengthen them.

== I ==
; ICS - Information and Communications Systems Department

; IGI - International Genealogical Index
: A list of names of deceased persons for whom temple ordinances have been performed. The most current version is available on the [http://www.familysearch.org/ FamilySearch] Web site.

; IMOS - Internet Mission Office System

;Inactive : A term not officially used in the Church any more. See '''Less Active'''.

;Inactivity

;[[Individual Ordinance Summary]] : A form that contains most of the information on a [[Membership Records|Membership Record]] that can appropriately be given to a member.

;Investigator

;[[Individual Ordinance Summary|IOS]] : Individual Ordinance Summary

; IP - Internet Protocol
: An Internet protocol is a unique address that devices use to identify and communicate with each other on a computer network utilizing the Internet protocol standard (IP).
: [http://en.wikipedia.org/wiki/IP_address Wikipedia Definition]

; IROP - Internal Record Of Purchase : A document used to record internal Church purchase transactions. The most common IROP transactions for Church units are those made at LDS Distribution Services online through the LDS Store, in person, or by telephone. Unit IROPs are transmitted electronically through MLS.

== J ==
; JSMB - [http://www.lds.org/placestovisit/location/0,10634,1872-1-1-1,00.html Joseph Smith Memorial Building]

== K ==
; KB - KnowledgeBase
: A database of articles that help individuals resolve issues.

== L ==
;Less Active : Participating in Church on an irregular basis, which may vary from coming to a few things a year to never coming at all. Members who attend meetings less than once a month are considered less active.

;[[Priesthood Line of Authority|Line of Authority]] : The chain of ordinations for a priesthood holder showing who ordained him to his current office, who ordained the ordainer, and so on back to Jesus Christ.

;LUAAT : Local Unit Area Auditor Trainer

;[[Budget Allowance|LUBA]] : Local Unit Budget Allowance

;LURBS : Local Unit Receipting, Reporting, and Banking System - A back office system used by administrative offices for financial record-keeping outside of North America. It provides various reports for local units, including a [[Ward/Branch Monthly Financial Report|monthly financial report]].

;[[Administrative office#Local Unit Support|LUS]] : Local Unit Support Group - Located in Salt Lake City, Utah, provides support for priesthood leaders in Canada and the United States.

;[[LUWS]] - Local Unit Web Site
: Also called the "Classic Ward and Stake Website," these sites were retired at the end of 2012 and replaced by various tools on LDS.org.

== M ==
;Member : A member of the Church of Jesus Christ of Latter-day Saints is a person eight years old or older who has been baptized and confirmed a member of the Church.

;Membership : The state of being a member of the Church of Jesus Christ of Latter-day Saints, as evidenced by records kept at Church headquarters and in the local unit's MLS. Records are also created for children of members of the Church who are under eight years old; however, these children are not considered members until eight years old, when they are baptized and confirmed.

;[[Membership Clerk]] : Person responsible for maintaining membership records on the members of a unit.

;[[Membership Records|Membership Record]]

;MIS : Old DOS-based local unit membership software. See [[MLS]] for current software.

;[[MLS]] - Member and Leader Services (membership and financial software)
: MLS software is for use by unit leaders, clerks, auxiliary and quorum leaders, and secretaries at both the ward and stake levels. MLS is designed to make Church record-keeping easier and more efficient.

;MRN : Membership Record Number

;[[Administrative office|MSR]] : Membership and Statistical Records Department - the Church department that is commonly known to clerks as the [[administrative office]].

== N ==
;[[NQI]] : Non-quality item - a financial transaction that is not complete after 2 months.

; NOB - North Office Building
: The building that is directly north of the Church Office Building and was previously called the Data Center.

== O ==
;Office : A position in the priesthood (such as priest, elder, and high priest) that has attached to it certain duties, responsibilities, and rights.

;Ordinance : A ceremony performed by the priesthood for a specific purpose. Examples are baptism/confirmation, ordination to the priesthood, and temple sealings. Some are saving ordinances and must be received by members in order to be saved, such as baptism/confirmation. Others may not necessarily be saving ordinances, such as a child blessing.

;Ordination : The bestowal of the priesthood and/or a priesthood office. For example, when a male member is ordained to the office of elder, he receives the Melchizedek Priesthood and is ordained to the office of elder within the Melchizedek Priesthood. Later in life, if he is ordained to the office of high priest, he does not receive the Melchizedek Priesthood again, but is ordained to the office of high priest within the Melchizedek Priesthood. Both examples are considered ordinations.

== P ==
; PAF - Personal Ancestral File
: A Church-produced computer software program that enables people to compile and organize their genealogy on their personal computers. PAF can help members identify ancestors and prepare their names for temple work.

;Patriarch : Patriarch is an office in the Melchizedek Priesthood, and not a calling. A patriarch is recommended by the stake president, sustained in stake conference or stake priesthood meeting, and ordained by the First Presidency or one of the Twelve Apostles or (with written permission from the Twelve) the stake president. Patriarchs give personal blessings to members of the stake (see Patriarchal Blessing).

;Patriarchal Blessing : A blessing given to a member by the patriarch of his or her stake. After the member obtains a recommendation from the bishop, he or she is given a blessing in which the patriarch may give the member's lineage, list weaknesses and strengths, pronounce advice from the Lord concerning the member's future, and any other direction or guidance.

; PC - Personal Computer

; PDD - Project Definition Document

;PEC : Priesthood Executive Committee

;PEF : Perpetual Education Fund

;Perpetual Education Fund

;Personal Priesthood Interview : ''Obsolete''. See Priesthood Interview

;Physical Facilities Representative : A local priesthood holder responsible for the physical status of a meetinghouse.

;PI : Priesthood Interview

; PIX
: Church-managed Cisco PIX firewall used primarily for FHC Internet connections.

;PLT : Priesthood Leadership Travel

;PPI : Personal Priesthood Interview. ''Obsolete''. See Priesthood Interview

;Presiding Bishop : A General Authority of the Church. The Presiding Bishop and his counselors serve under the direction of the First Presidency to administer the temporal affairs of the Church.

; PRF - Pedigree Resource File
: A file of lineage-linked data submitted by both members and nonmembers through the [http://www.familysearch.org/ FamilySearch] Web site. The master index is available online and the entire file is available on CD. The Pedigree Resource File is the successor to the Ancestral File.

;Priesthood Executive Committee

;Priesthood Interview : A private stewardship meeting between a priesthood leader and a person who reports to him

== Q ==
;[[Quarterly Report]] : A report of member attendance and other key statistics submitted by wards to the stake and the Church each quarter

== R ==
;Recommend

;Record

;Record Keeping

;REFIS

;Relief Society : The women's organization of the Church, organized by Joseph Smith in 1842, dedicated to "the exercise of all benevolent purposes." The Relief Society provides Sunday gospel instruction, other Relief Society meetings, visiting teaching, and welfare and compassionate service opportunities.

;RS : Relief Society

; RSS - Really Simple Syndication
: RSS is a Web-feed format that is used to publish frequently updated digital content to consumers who use RSS aggregators to notify them of updates.
: [http://en.wikipedia.org/wiki/RSS Wikipedia Definition]

== S ==
; SAV - Symantec Anti-Virus : An anti-virus software formerly used on Church-owned computers, such as those used in stakes and wards. All computers should now have the Sophos anti-virus software.

; SA - Single Adult
: A single member above the age of 30. See also YSA.

; SDK - Software Development Kit
: SDK is typically a set of development tools that allows a software engineer to create applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, and more.
: [http://en.wikipedia.org/wiki/Software_development_kit Wikipedia Definition]

; SEO - Search Engine Optimization

; SERP - Search Engine Results Page

;Set Apart

;SFS : ''Obsolete''. See Consolidated Financial Statement.

; SOAP - Simple Object Access Protocol
: A protocol for exchanging XML-based messages over a computer network, normally using HTTP.
: [http://en.wikipedia.org/wiki/SOAP Wikipedia Definition]

; Sophos Anti-Virus : An anti-virus software currently used on Church-owned computers, such as those used in stakes and wards.

; SORT
: An internal conference hosted by ICS for technical Church employees.

; SRD - Solutions Requirement Document
: The SRD is used to identify the business requirements and business case for a proposed technology project.

; SSH - Secure Shell
: SSH is a communication system that uses public-key cryptography to establish a secure connection between remote computers.
: [http://en.wikipedia.org/wiki/Ssh Wikipedia Definition]

;Stake

;[[Stake Clerk]] : Person responsible for all clerical activities in a stake.

;Stake President : The stake president presides over the stake and is assisted by two counselors. The stake president reports to and receives direction from the presidency of the Seventy or from the Area President.

;[[Stake Technology Specialist]] : Person responsible for the technology assets of the stake and each ward in the stake.

;[[Statistical Clerk]] : Person responsible for collecting and preparing the [[Quarterly Report]].

== T ==

;[[Desktop Management Software|TEM]] - Tivoli Endpoint Manager
: Replaced LANDesk as the official software CHQ uses to centrally manage and secure the global fleet of Church-owned computers. TEM will install and utilize the BES Client service.

;Temple

;Temple Ordinances

;Temple Recommend

;Temporal

;Tithing

;Tithing Settlement

== U ==
;Unit : A congregation or other function in the Church that is responsible for its budget. Wards, Stakes, Branches, Districts, Family History Centers, etc., are all examples of Units.

;Unit Financial Statement : the Unit Financial Statement has replaced the old Church Unit Financial Statement.

== V ==
;Visiting Teacher

;Visiting Teaching

; VoIP - Voice Over Internet Protocol
: The technology that allows voice communication (such as telephone) over a network instead of through traditional phone lines. The Church has deployed VoIP in several locations indlucing BYU, the North Office Building, the Triad Center, and Ghana.
: [http://en.wikipedia.org/wiki/Voip Wikipedia Definition]

; VPN - Virtual Private Network
: VPN is a private communications network often used within a company, or by several companies or organization, to communication confidentially over a publicly accessible network.
: [http://en.wikipedia.org/wiki/Vpn Wikipedia Definition]

== W ==
;Ward

;Ward Budget

;[[Ward Clerk]] : Person responsible for all clerical activities in a ward.

;Ward Council

;Ward Welfare Committee

;Welfare

;Welfare Services

== Y ==
;YM - Young Men
:Single male members between the ages of 12-18.

;YSA - Young Single Adult
:A single member between the ages of 18-30. See also SA.

;YW - Young Women
:Single female members between the ages of 12-18.

[[Category:Help]]

User:Aebrown

2014-11-03T16:13:07Z

Aebrown: Update callings

__NOTOC__
== Alan Brown ==
=== Forum/Wiki ===
* Moderator, [http://tech.lds.org/forum LDSTech Forums] (User [http://tech.lds.org/forum/member.php?u=1684 aebrown])
* Administrator, [[Main Page|LDSTech Wiki]] (User [[User:Aebrown|Aebrown]])

=== Contact ===
[[Special:EmailUser/Aebrown|Send me email]].

=== Location ===
Sandy, UT

=== Interests ===
.NET and Java development

=== Occupation ===
Software Engineer for the [http://www.FamilySearch.org Church Family History Department]

=== Current callings ===
* 2014-present: Bishopric counselor

=== Previous callings ===
* 2012-2014: Stake Clerk
* 2004-2014: Stake Web Site Administrator
* 1997-2014: Stake Technology Specialist
* 2006-2012: Stake Financial Clerk
* 2001-2012: Assistant Stake Clerk
* 1996-2001: Ward Financial Clerk
* 1992-1994: BYU High Councilor with responsibility for clerks and computers in 12 wards
* 1986-1991: Ward Financial Clerk
* 1985-1988: Stake Auditor
* 1982: BYU Ward Membership Clerk

== Sandboxes ==
[[User:Aebrown/Sandbox|My Sandbox]]

TechWiki:Wiki editing tutorial

2014-10-30T21:21:21Z

Aebrown: fix sample table link

The platform for LDSTech is a wiki, powered by [http://www.mediawiki.org MediaWiki]. Anyone can view the wiki, but you need to be signed in with your [[LDS Account]] to make edits. Working with the wiki requires you to be familiar with some basic wiki syntax, but it's easy enough for practically anyone to contribute, regardless of technical skills. This page provides instructions for adding and updating content on the wiki. There are about 20 different wiki skills to master, with a brief practice exercise to demonstrate mastery of each skill.

As you learn the wiki, feel free to experiment on this [[LDSTech:Sandbox page|shared sandbox page]] or on [[Special:Mypage/Sandbox|your own sandbox page]].

==Creating your user page==
Your user page shares information about yourself that you want others to know. For example, here's a sample user page: [[User:Aebrown]]. By reading the user page, you can find information about the person's role, interests, and contact information. This can help you evaluate the validity of the user's edits.

When you make edits to the wiki, the wiki shows your username next to edits in the version history for the page. To see the version history, click the '''History''' button above the page title. The history shows the edits and timestamps, with the users who made each of the edits. If the usernames appear in red and are underlined, it means the user hasn't yet created a user page. Without a user page, it's hard to know who is making edits to the wiki.

To create a user page:
# Log in to the wiki.
# Click your username that appears near the login section, or just this link: [[Special:MyPage]].
# Add some information about yourself.
# Click '''Create'''.

''PRACTICE: Create your user page.''

== Watching pages ==

To keep updated about edits to a specific wiki page, you can "watch" the page by clicking the '''Watch''' button above the page title. Every time someone updates the page, you will be notified by e-mail according to the e-mail address listed in in your [[Special:Preferences|preferences]].

''PRACTICE: Watch this page.''

==Setting your e-mail preferences==

If your email isn't configured correctly in your preferences, you won't receive e-mail notifications even if you are watching a page. To configure your e-mail preferences:
# Click '''My preferences''' (near the login area).
# On the '''User Profile''' tab, make sure your e-mail address is up to date.
# In the Email section of the User Profile tab, select the check boxes to set your notification preferences. (At the very least, select "E-mail me when a page on my watchlist is changed.")
# Click '''Save'''.

Note that when you have an e-mail address added to your preferences, other users can send you e-mail. When you view a user page (such as this one, [[user:Johnsonth]]), scroll to the Toolbox section of the footer and click ''E-mail this user''. If users don't have an e-mail address added to their preferences, the ''E-mail this user'' option will not appear in the Toolbox on their user page, and so you can't send them an e-mail.

''PRACTICE: Check your e-mail address and preferences to make sure your settings are up to date.''

== Editing articles ==

When you edit the wiki, you can choose to edit the entire page or just a section on the page. If you click the Edit button above the title, you edit the entire page. If you click the Edit button to the right of a section, you just edit that section.

When you make an edit, provide a brief summary of the edit. This allows people to quickly scan the list of edits on the [[Special:RecentChanges|Recent Changes]] to see the reasons for the edits.

To edit a page:
# Click the '''Edit''' button above the page.
# Make the changes.
# In the Summary section, briefly summarize your edits.
# To stay notified about changes to the page, select the '''Watch this page''' check box.
# Click '''Save page'''.

Because multiple people may be working on the same page, it's best to edit just the section you're updating. The chances of multiple people updating the same ''section'' at the same time are far fewer than the chances of multiple people editing the entire ''page'' at the same time. That's why each section has its own Edit section.

If multiple people edit the same content at the same time, and then click Save, the last person to save will be prompted to merge the changes in with the other updates.

''PRACTICE: Go to [[Special:MyPage|your user page]] and edit the page. Make an update and save it.''

==Creating pages==

On the wiki, you create a page by searching for it. When you search for the page, if there isn't a page with the same name, you're asked whether you want to create the page. This is the wiki's own way of prompting users to get involved in creating more wiki content. Note that the capitalization style for page names on this wiki follows the same conventions as Wikipedia: single case. Other than the first word and proper nouns, lowercase words in titles.

To create a page:
# In the search box, type the name of the page you want to create. (Note that capitalization matters. The page ''Dogs'' is different from the page ''dogs''.)
# The page you searched for appears as a red, underlined link. Click the link.
# Add some content, and then click '''Create''' to create the page.

You can also create a page by adding <nowiki>[[Page title]]</nowiki> on a page and saving it, where "Page title" is the name of the page you want to create. When you save the page, the link will appear red and underlined. Click the link to create the page.

''PRACTICE: Search for a hypothetical page name in the Search box. Note how the site prompts you to create the page it cannot find. Now go to your [[Special:MyPage|user page]], edit the page, and add a link to a page you want to create. Click the link to see how to create the page. However, do not actually create the page. This is a live site, so rather than creating unnecessary pages, make edits on your user page.

== Deleting pages==
Deleting pages requires administrative permissions. Instead of deleting a page, you "move" the page to a new location. When you click '''Move''', you can choose a new page title. By ''moving'' rather than ''deleting'' a page, any user who clicks on the link to the old page will be automatically redirected to the new page. This is because the old page will receive a "redirect" to point users to the new page.

''PRACTICE: Go to a [[Special:Random|random page]] and identify the location of the Move button. You can click the Move button above the title, but don't click the additional Move button on the Move page, which will actually move the page.''

== Making text bold or italic==

The wiki uses a special syntax for formatting. When you save a page, this syntax gets converted into HTML for the browser. To create bold or italic formatting, add ticks around a word, like this:
<pre>
'''bold formatting'''
''italic formatting''
</pre>

You can also use the B and I buttons on the editor toolbar.

''PRACTICE: On your [[Special:MyPage|user page]], bold and italicize a word.''

==Inserting lists==

To create a bulleted list, add an asterisk (*) at the start of each line, like this:
<pre>
* first item
* second item
* third item
</pre>

To create a numbered list, add a pound sign (#) at the start of each line, like this:
<pre>
# first item
# second item
# third item
</pre>

With numbered lists, make sure you don't have spaces between the lines, or the numbered lists will start over.

To insert a bulleted list within a numbered list, combine the two forms of syntax like this:
<pre>
# first item
#* bulleted list item 1
#* bulleted list item 2
# second item
# third item
</pre>

''PRACTICE: On your [[Special:MyPage|user page]], create a numbered list with a bulleted sublist on one of the list items.''

== Adding notes and tips ==

You can add notes before or after a procedure by adding
<pre>{{Note|Type your note here.}}
</pre>

When you style notes this way, the note calls a template that styles the note with more formatting.

Here's what a note looks like:

{{Note|This is a sample note.}}

''PRACTICE: On your [[Special:MyPage|user page]], add a note.''

==Adding links to wiki pages==

To add a link to another page, enclose the page name in double brackets, like this:
<pre>
[[LDSTech:Manual of Style]]
</pre>

You can also change the text of the link by adding a pipe after the page name. If you want the link to just say "Manual of Style" rather than "LDSTech:Manual of Style" you would write the link like this:
<pre>
[[LDSTech:Manual of Style|Manual of Style]]
</pre>

''PRACTICE: On your [[Special:MyPage|user page]], add a link to this page.''

==Adding links to external pages==

Creating an external link (to a site such as byu.edu) is similar to creating an internal link but with a couple of minor differences. Rather than two square brackets, you use single brackets. And rather than a pipe separating the link from the link's text, you just use a space. Here's an example:

<pre>
[http://byu.edu BYU's website]
</pre>

''PRACTICE: On your [[Special:MyPage|user page]], add a link to your blog or other website. If you don't have a website, add a link to your favorite website.''

== Inserting subheadings ==
To create a subheading on a page, surround the subheading with two equals signs, like this:

<pre>
== Subheading title ==
</pre>

This creates an h2 style around the subheading. You can create a third level subheading by using three equals signs. Avoid using just one equals sign, which would result in an h1 subhead style.

MediaWiki automatically generates a table of contents (TOC) when you have at least four subheadings on a page. The general style on the wiki is to show the TOC after an introductory paragraph. You can force the display of the table of contents by adding <nowiki>__TOC__</nowiki> where you want it to appear. To remove the automatic display of the TOC, include <nowiki>__NOTOC__</nowiki> on the page.

''PRACTICE: On your [[Special:MyPage|user page]], add two levels of headings.''

==Embedding images==
Adding an image requires two separate steps: first you upload the image using the '''Upload file''' link within the Toolbox menu in the footer. Then you embed the image by adding the following code, where sample.png is the name of the uploaded image file:

<pre>
[[File:sample.png]]
</pre>

You can add additional parameters for the image file as well, such as a border, alignment, and caption. To add these parameters, separate each parameter with a pipe, such as this:

<pre>
[[File:sample.png|frame|none|This is my caption.]]
</pre>

Frame will add a border around the image and caption area. None specifies no alignment (type "right" or "left" to specify right or left alignment). The final text constitutes the caption.

To add an image:
# Hold down the '''Ctrl''' key and click ''Upload file'' in the footer. A new tab opens with the file upload box.
# Click '''Choose File'' and select the file you want to upload.
# After uploading the file, embed the image on a page by adding <nowiki>[[File:sample.jpg]]</nowiki>, where sample.jpg is the name of the image.
# To add parameters to the image, add this information in pipes following the image name: <nowiki>[[File:sample.jpg|frame|none|This is my caption.]]</nowiki> Frame adds a border around the image with a caption area. ''None'' specifies the alignment. You can also type right or left here. The final text is the caption.
# Click '''Save page.'''

Note that you can put a width parameter for the images, but if you also include a frame, the width parameter does not work.

If you're embedding an image within a numbered list, you can avoid breaking the list's numbering sequence by adding the image code at the end of a list item rather than on a new line. The "none" alignment parameter in the image code will force the image to display on its own line, but it won't break the numbering sequence.

Here's an example:

Do these steps:
# This is the first step.
# This is the second step. [[File:Ldstechlogo.png|LDSTech logo|frame|none|LDSTech logo]]
# This is the third step.
# This is the fourth step.

The code that produces this is as follows:
<pre>
Do these steps:
# This is the first step.
# This is the second step. [[File:sample.jpg|frame|none|This is my caption.]]
# This is the third step.
# This is the fourth step.
</pre>

{{Note|In general, keep images to about 600px in width. Otherwise, the image will not fit with a sidebar. Also, rather than using width parameters with the image, which merely resize the image in the browser, resize your image before uploading it. This way the image file size will be smaller.}}

''PRACTICE: Embed the LDSTech logo [[File:Ldstechlogo.png|LDSTech logo]] on your [[Special:MyPage|user page]]. You don't need to re-upload the image file, but you can if you want to.''

== Discussing pages ==

Each page has a corresponding Discussion page that allows you to have a discussion about the page's content without actually changing or adding your comments and questions to the official page's content. To view the discussion page, click '''Discussion''' above the page title.

To indent your response to a question on the Discussion page, add a colon before your response. To double indent your response, add two colons. After your response, add four tildes (<nowiki>~~~~</nowiki>) to sign your name. Your name links to your profile page.

''PRACTICE: View the Discussion page for this page. Now go to the Discussion page for your [[Special:MyPage|user page]]. Ask a question, and then provide an indented response to the question and sign your name.''

== Adding a sidebar ==

Mediawiki allows you to create templates that you can then embed into pages. The sidebar that you see on many pages, for example on the [[LDS.org applications]] documentation, is created with a template. Creating a sidebar template can be helpful if you have a collection of pages that you want to group together. After you create a template, you embed it on a page by adding <nowiki>{{templatename}}</nowiki> on the page, where templatename is the name of your template.

To create a sidebar, it's best to simply copy an existing sidebar (like the calendar sidebar) and make changes.

''PRACTICE: View the template for the calendar by searching for [[Template:ldsorgapps]]. Now go to a [[LDS.org applications]] page and click edit. Look for the <nowiki>{{ldsorgapps}}</nowiki> template code. Now embed the LDS.org applications sidebar on your [[Special:MyPage|user page]], and then remove it.''

==Adding pages to categories==
You can tag each wiki page with one or more categories. Categories group together a collection of pages that all belong to the same category. For example, the [[:Category:LDSTech Conference]] category shows all pages that are tagged with <nowiki>[[Category:LDSTech Conference]]</nowiki>.

Mediawiki's structure prompts you to nest categories into progressively more general categories until you reach the top, like an inverted tree.

The category a page is in appears near the bottom of the page.

''PRACTICE: Look at the [[LDSTech Conference]] page. Locate the category at the bottom. Trace the category up the hierarchy until you reach the top level. The navigate back down to through the categories back to the LDSTech Conference homepage.''

==Viewing Special Pages==
Mediawiki has a collection of "Special Pages" that provide content management functions for managing the content on the wiki. To view these [[Special:SpecialPages|Special Pages]], click the ''Special Pages'' link in the Toolbox section of the footer.

You can click a variety of links to look at the content. For example, you can view the longest or shortest pages, pages that are orphaned (have no links) or which have the fewest revisions. These special pages can help you locate problem points on the wiki.

''PRACTICE: Go to the Special Pages section and find the oldest page on the wiki.''

==Formatting tables==

Inserting tables on the wiki is a little more complicated than the other wiki syntax. Here's a sample table:
{|
!first column name
!second column name
|-
|first row, first column
|first row, second column
|-
|second row, first column
|second row, second column
|-
|third row, first column
|third row, second column
|}

Here's what that table's wiki syntax looks like:
<pre>
{|
!first column name
!second column name
|-
|first row, first column
|first row, second column
|-
|second row, first column
|second row, second column
|-
|third row, first column
|third row, second column
|}
</pre>

The <nowiki>{|</nowiki> announces the start of the table and the <nowiki>|}</nowiki> ends the table.

The <nowiki>!</nowiki> indicates column name (optional).

The <nowiki>|-</nowiki> indicates the start of a row. The | is a column in that row.

You can also add style tags to create custom styles for tables. If you're creating a new table, it's often easiest to just copy over the code from an existing table.

''PRACTICE: Copy the table that appears on the [[LDSTech Conference 2012 session streams|live session streams]] page and embed it onto your [[Special:MyPage|user page]]. Change the column names. Then remove the table.

==View user contributions==
You can view a list of all your contributions by clicking the ''My Contributions'' link near the login area. This shows you all the edits you've made to the wiki.

You can also view contribution links from other users as well. When you view someone's user page (for example, [[user:Aebrown]], click the ''User Contributions'' link in the footer. This shows a list of just that user's contributions.

When you view the page history, you can also see a list of the user's contributions by clicking the ''contribs'' link next to the username. This can give you a quick idea about the user's credibility and authority to make edits to a page.

''PRACTICE: Go to a [[Special:Random|Random]] page on the wiki and look at the history of the page. Look at the list of contributions made by the last user to edit the page. Try and see if you can e-mail the user.''

==Get involved==
Now that you've completed the wiki editing tutorial, it's time to get involved. The [[LDSTech:Community Portal]] lists current needs for the wiki. There's a link to the Community Portal in the site's footer. You can see various efforts to adding or maintaining content.

''PRACTICE: Browse the Community Portal and find a task that interests you.''

[[category:LDSTech Administration]]

Tech Missionary Opportunities

2014-10-28T13:23:23Z

Aebrown: Replace HTML with wikitext for bulleted lists

[[File:Banner missionary.jpg|link=https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA]]

=='''CSM Opportunity of the Week--Web Developer, Church History'''==
The Church is currently looking for a Web Developer--Church History (opportunity 10838). This skilled developer should have practical and industry experience in a MarkLogic environment. The candidate should be comfortable working in a very fast pace and be nimble and agile in development cycles. The consecrated effort should be at least 15-20 hours a week for at least 6 months, but a year is preferred. The candidate needs to have 2 weeks of full-time training in the Riverton Office Building (ROB), Utah before starting to work remotely.

Required skills include:
* CS Bachelors or equivalent experience
* 2 years of Enterprise web application engineering experience
* Java
* Javascript
* XHTML
* CSS3
* XML
* XSLT
* Web Services (REST)
* XQuery (Marklogic)
* Responsive design
* Mobile Web
* LESS

Optional skills include:
* Eclipse
* GIT
* Agile Methodology

If this sounds like the perfect opportunity for you, please fill out the LDSTech Missionary and Service Opportunities form (link below). For further information, click on Opportunity number 10838 below or call Sister Bottorff at 801-240-7373.

=='''International Full-Time Missions'''==
Full-time Foreign Technology Specialist Missionary Opportunities have been posted!! Full-time Area Technology Specialist missionaries are being requested world-wide. The current list of open opportunities are on page 6 of the below link.

:'''LDSTech Full-time Technical Missionary'''
:* [https://www.lds.org/bc/content/ldsorg/callings/missionary/senior-missionary/senior-missionary-opportunities.pdf?lang=eng#page=7 '''International Area Technology Specialist''' (ATS) '''see page 6''']

{| class="wikitable"
! ATS Area !! Fluent Language(s) || Updated
|-
| [[Media:Area_Technology_Specialist_Description_(Korea).Jan_2014.pdf‎ |Korea, Seoul]] || Korean and English || 24 OCT 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Pacific).pdf |Apia, Samoa]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Pacific).pdf |Suva, Fiji]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology Specialist_Description_(Pacific).pdf |Nuku'alofa, Tonga]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology Specialist_Description_(Europe).pdf |Frankfurt, Germany]] || English and other European language || 27 OCT 2014
|-
|}

Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission. Opportunities are for healthy seniors with no dependents who are able to finance their mission based on the area's mission cost.

You may also call 801-240-6226 for further information on ATS Senior Couple full-time foreign missionary opportunities.

=='''Current Church-Service Missionary Opportunities''' ==
If you desire to serve a Church-service mission, you can become a missionary for LDSTech. LDSTech missions are ideal for worthy people who work or have worked in the IT industry. You may be a young or young-at-heart tech expert who is worthy to serve a proselyting mission but cannot. You could also be a couple that is retired or on a leave of absence and looking for an opportunity to serve a mission. This could be an ideal place to serve. Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission.

The latest Church-Service Missionary opportunities are listed on LDS.org. To view the opportunities, on [http://lds.org LDS.org] go to '''Resources > Missionary > Church-Service Missionaries''', then click '''Browse All Opportunities'''. Or go directly to [http://servicemission.ldschurch.org http://servicemission.ldschurch.org]. In the Select an Interest drop-down box, select '''Information Technology and Computer Science'''.

For convenience, the following list shows the available LDSTech Church-Service Missionary opportunities. Each of these opportunities links to the [http://servicemission.ldschurch.org http://servicemission.ldschurch.org] site listed above.

==='''Work-from-Home Opportunities'''===
:'''Blackberry Developer for LDSTech''' {{service mission|10279}}

:'''Church History Web Developer for LDSTech''' {{service mission|10838}}

:'''Mission Coordinator for LDSTech''' {{service mission|12162}}

:'''MSR Designer for LDSTech''' {{service mission|12537}}

:'''LDS Tools for Windows Developer for LDSTech''' {{service mission|12794}}

:'''Writer for LDSTech''' {{service mission|12818}}

==='''Opportunities at the Riverton Office Building'''===
:'''Web Developer for LDSTech''' {{service mission|9996}}

:'''Oracle/SQL Server DBA for LDSTech''' {{service mission|10500}}

:'''Telephone Inventory Specialist for LDSTech''' {{service mission|12082}}

:'''Change Coordinator for LDSTech''' {{service mission|12528}}

:'''QA Engineer for LDSTech''' {{service mission|12555}}

:'''Android QA Engineers for LDSTech''' {{service mission|12662}}

:'''QA Testing Engineer for LDSTech''' {{service mission|12970}}

:'''Social Media Expert for LDSTech''' {{service mission|13031}}

If you have another IT skill and would still like to serve, there may be other opportunities available as well. Please call us at 801-240-7373 or email us at ldstech-mission@ldschurch.org.

==Time commitments==
Time commitments can be 6, 12, or 18 months. At the end of the term of service, you can extend the missionary commitment to continue serving.

==Skills==
The skills required to serve an LDSTech mission vary based on the opportunity. See the opportunity descriptions for each advertised position. Senior couples with varying technical skills are especially welcome. Many times one person may serve in one role on a project (for example, project leader) while the spouse serves in another role (for example, tester).

==Language requirements==
At this time, an LDSTech mission requires the ability to speak English. We also now have opportunities for those who speak other languages along with English, to help with special projects.

==Application process==
Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission. When you fill out this form, LDSTech can help you through the mission process. If you have questions about an LDSTech mission, please send an email to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. If you prove to be a good fit for one of these positions, you will then complete the Church-service missionary application process. This process is described on the [https://www.lds.org/callings/missionary/church-service?lang=eng Church-Service Missionaries page on LDS.org]. In summary, the application process is as follows:

# First, you complete the [https://www.lds.org/bc/content/ldsorg/content/english/service/missionary-service/church-service-missionaries/form/pdf/recommendation-for-church-service-missionary-eng.pdf?lang=eng Recommendation Form for Church-service Missionaries].
# Upon receiving the completed recommendation forms, the bishop certifies your worthiness and concurs with the selected choice for service. He then signs the form and forwards it to the stake president.
# The stake president interviews you for worthiness, signs the recommendation form, and forwards it to the Church Service Missionary Office at Church headquarters for authorization to extend the call. (See Note below)
# The Stake President will receive your call letter and will extend the call to you. The stake president authorizes the bishop to set the new missionary apart.
# Church-service missionaries should then contact the operation where they will be serving. They are supervised and trained under the direction of the operation in which they serve. The stake president and bishop remain the ecclesiastical leaders for the member.

{{Note|To submit your Church-service mission application please ask your stake president for a copy and scan and email to Sister Noni Boyle (boylene@ldschurch.org) and the form will be forwarded to the Church Service Missionary Office. You may also fax it to 801-353-4350, with a cover letter to Sister Boyle. Sister Boyle will alert you when your call has been issued.}}

==Backlogs ==
If you've inquired about a mission or already submitted your papers and haven't heard back from LDSTech yet, please be patient. As we work to manage the numerous inquiries for LDSTech Church-service missions, we have found more interest than we have current opportunities for. This has been a pleasant surprise. More opportunities are being created on a regular basis. We will continue to do our best to match current opportunities with those who have matching skills and availability.

Most importantly, if you feel prompted to serve, don’t wait for us -– reach out and remind us of your desire to serve. When you do, please include a brief description of your availability and technical experience and skills. Many opportunities require service to be done at the Riverton, UT office building. If you have strong interest in one of the following opportunities, please let one of us know.

* Testers
* Software Developers
* Interaction Designers
* Writers
* Project Managers
* Business Analysts

If you are not able to serve at the [[Riverton Office Building]], but are still interested in an LDSTech Church-service mission, please be patient with us as we try to find more opportunities to serve from home. These opportunities will grow over time and we are excited about the growth.

=='''Requesting a Church-service missionary'''==
If you're a '''Church employee''' and would like to request a Church-service missionary for your group or department, send the position details and requirements to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. LDSTech administrators will post the details on the [http://servicemission.ldschurch.org LDS.org Church-service missionary opportunity page], this wiki page, and will include it in articles and newsletters to find the right person for the position. You can also fill out the form below.

:'''LDSTech Missionary Opportunity Request'''
:* [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dGtaSzZtbWdycXZIVDNJSk9TLURLOHc6MA '''LDSTech Missionary Opportunity Form''']

==Questions and contacts==

If you need more information about Church-service missionary opportunities, contact Sister Cheryl Bottorff, LDSTech Missionary Coordinator, at [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org] or [mailto:cheryl.bottorff@ldschurch.org cheryl.bottorff@ldschurch.org].

{{note|LDSTech Contact Information:

Phone: +1-801-240-7373

Email: [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]}}

==Additional reading==
The following articles provide more information about LDSTech Church-service missions.
* [https://tech.lds.org/index.php/ldstech/1-miscellaneous/459-using-a-church-service-missionary-on-your-project Helping out projects as a Church service missionary]
* [https://tech.lds.org/index.php/component/content/article/1-miscellaneous/411-profile-of-a-technology-service-missionary Profile of a technology service missionary]
* [https://tech.lds.org/blog/480-new-church-service-missionary-opportunities-available Church-service missionary opportunities available]

Tech Missionary Opportunities

2014-10-28T13:20:08Z

Aebrown: Fix table end for ATS table

[[File:Banner missionary.jpg|link=https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA]]

=='''CSM Opportunity of the Week--Web Developer, Church History'''==
The Church is currently looking for a Web Developer--Church History (opportunity 10838). This skilled developer should have practical and industry experience in a MarkLogic environment. The candidate should be comfortable working in a very fast pace and be nimble and agile in development cycles. The consecrated effort should be at least 15-20 hours a week for at least 6 months, but a year is preferred. The candidate needs to have 2 weeks of full-time training in the Riverton Office Building (ROB), Utah before starting to work remotely.

Required skills include:<ul>
<li style="margin: 0;">CS Bachelors or equivalent experience</li>
<li style="margin: 0;">2 years of Enterprise web application engineering experience</li>
<li style="margin: 0;">Java</li>
<li style="margin: 0;">Javascript</li>
<li style="margin: 0;">XHTML</li>
<li style="margin: 0;">CSS3</li>
<li style="margin: 0;">XML</li>
<li style="margin: 0;">XSLT</li>
<li style="margin: 0;">Web Services (REST)</li>
<li style="margin: 0;">XQuery (Marklogic)</li>
<li style="margin: 0;">Responsive design</li>
<li style="margin: 0;">Mobile Web</li>
<li style="margin: 0;">LESS</li>
</ul>
Optional skills include:<ul>
<li style="margin: 0;">Eclipse
<li style="margin: 0;">GIT
<li style="margin: 0;">Agile Methodology</li>
</ul>
If this sounds like the perfect opportunity for you, please fill out the LDSTech Missionary and Service Opportunities form (link below). For further information, click on Opportunity number 10838 below or call Sister Bottorff at 801-240-7373.

=='''International Full-Time Missions'''==
Full-time Foreign Technology Specialist Missionary Opportunities have been posted!! Full-time Area Technology Specialist missionaries are being requested world-wide. The current list of open opportunities are on page 6 of the below link.

:'''LDSTech Full-time Technical Missionary'''
:* [https://www.lds.org/bc/content/ldsorg/callings/missionary/senior-missionary/senior-missionary-opportunities.pdf?lang=eng#page=7 '''International Area Technology Specialist''' (ATS) '''see page 6''']

{| class="wikitable"
! ATS Area !! Fluent Language(s) || Updated
|-
| [[Media:Area_Technology_Specialist_Description_(Korea).Jan_2014.pdf‎ |Korea, Seoul]] || Korean and English || 24 OCT 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Pacific).pdf |Apia, Samoa]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Pacific).pdf |Suva, Fiji]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology Specialist_Description_(Pacific).pdf |Nuku'alofa, Tonga]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology Specialist_Description_(Europe).pdf |Frankfurt, Germany]] || English and other European language || 27 OCT 2014
|-
|}

Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission. Opportunities are for healthy seniors with no dependents who are able to finance their mission based on the area's mission cost.

You may also call 801-240-6226 for further information on ATS Senior Couple full-time foreign missionary opportunities.

=='''Current Church-Service Missionary Opportunities''' ==
If you desire to serve a Church-service mission, you can become a missionary for LDSTech. LDSTech missions are ideal for worthy people who work or have worked in the IT industry. You may be a young or young-at-heart tech expert who is worthy to serve a proselyting mission but cannot. You could also be a couple that is retired or on a leave of absence and looking for an opportunity to serve a mission. This could be an ideal place to serve. Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission.

The latest Church-Service Missionary opportunities are listed on LDS.org. To view the opportunities, on [http://lds.org LDS.org] go to '''Resources > Missionary > Church-Service Missionaries''', then click '''Browse All Opportunities'''. Or go directly to [http://servicemission.ldschurch.org http://servicemission.ldschurch.org]. In the Select an Interest drop-down box, select '''Information Technology and Computer Science'''.

For convenience, the following list shows the available LDSTech Church-Service Missionary opportunities. Each of these opportunities links to the [http://servicemission.ldschurch.org http://servicemission.ldschurch.org] site listed above.

==='''Work-from-Home Opportunities'''===
:'''Blackberry Developer for LDSTech''' {{service mission|10279}}

:'''Church History Web Developer for LDSTech''' {{service mission|10838}}

:'''Mission Coordinator for LDSTech''' {{service mission|12162}}

:'''MSR Designer for LDSTech''' {{service mission|12537}}

:'''LDS Tools for Windows Developer for LDSTech''' {{service mission|12794}}

:'''Writer for LDSTech''' {{service mission|12818}}

==='''Opportunities at the Riverton Office Building'''===
:'''Web Developer for LDSTech''' {{service mission|9996}}

:'''Oracle/SQL Server DBA for LDSTech''' {{service mission|10500}}

:'''Telephone Inventory Specialist for LDSTech''' {{service mission|12082}}

:'''Change Coordinator for LDSTech''' {{service mission|12528}}

:'''QA Engineer for LDSTech''' {{service mission|12555}}

:'''Android QA Engineers for LDSTech''' {{service mission|12662}}

:'''QA Testing Engineer for LDSTech''' {{service mission|12970}}

:'''Social Media Expert for LDSTech''' {{service mission|13031}}

If you have another IT skill and would still like to serve, there may be other opportunities available as well. Please call us at 801-240-7373 or email us at ldstech-mission@ldschurch.org.

==Time commitments==
Time commitments can be 6, 12, or 18 months. At the end of the term of service, you can extend the missionary commitment to continue serving.

==Skills==
The skills required to serve an LDSTech mission vary based on the opportunity. See the opportunity descriptions for each advertised position. Senior couples with varying technical skills are especially welcome. Many times one person may serve in one role on a project (for example, project leader) while the spouse serves in another role (for example, tester).

==Language requirements==
At this time, an LDSTech mission requires the ability to speak English. We also now have opportunities for those who speak other languages along with English, to help with special projects.

==Application process==
Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission. When you fill out this form, LDSTech can help you through the mission process. If you have questions about an LDSTech mission, please send an email to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. If you prove to be a good fit for one of these positions, you will then complete the Church-service missionary application process. This process is described on the [https://www.lds.org/callings/missionary/church-service?lang=eng Church-Service Missionaries page on LDS.org]. In summary, the application process is as follows:

# First, you complete the [https://www.lds.org/bc/content/ldsorg/content/english/service/missionary-service/church-service-missionaries/form/pdf/recommendation-for-church-service-missionary-eng.pdf?lang=eng Recommendation Form for Church-service Missionaries].
# Upon receiving the completed recommendation forms, the bishop certifies your worthiness and concurs with the selected choice for service. He then signs the form and forwards it to the stake president.
# The stake president interviews you for worthiness, signs the recommendation form, and forwards it to the Church Service Missionary Office at Church headquarters for authorization to extend the call. (See Note below)
# The Stake President will receive your call letter and will extend the call to you. The stake president authorizes the bishop to set the new missionary apart.
# Church-service missionaries should then contact the operation where they will be serving. They are supervised and trained under the direction of the operation in which they serve. The stake president and bishop remain the ecclesiastical leaders for the member.

{{Note|To submit your Church-service mission application please ask your stake president for a copy and scan and email to Sister Noni Boyle (boylene@ldschurch.org) and the form will be forwarded to the Church Service Missionary Office. You may also fax it to 801-353-4350, with a cover letter to Sister Boyle. Sister Boyle will alert you when your call has been issued.}}

==Backlogs ==
If you've inquired about a mission or already submitted your papers and haven't heard back from LDSTech yet, please be patient. As we work to manage the numerous inquiries for LDSTech Church-service missions, we have found more interest than we have current opportunities for. This has been a pleasant surprise. More opportunities are being created on a regular basis. We will continue to do our best to match current opportunities with those who have matching skills and availability.

Most importantly, if you feel prompted to serve, don’t wait for us -– reach out and remind us of your desire to serve. When you do, please include a brief description of your availability and technical experience and skills. Many opportunities require service to be done at the Riverton, UT office building. If you have strong interest in one of the following opportunities, please let one of us know.

* Testers
* Software Developers
* Interaction Designers
* Writers
* Project Managers
* Business Analysts

If you are not able to serve at the [[Riverton Office Building]], but are still interested in an LDSTech Church-service mission, please be patient with us as we try to find more opportunities to serve from home. These opportunities will grow over time and we are excited about the growth.

=='''Requesting a Church-service missionary'''==
If you're a '''Church employee''' and would like to request a Church-service missionary for your group or department, send the position details and requirements to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. LDSTech administrators will post the details on the [http://servicemission.ldschurch.org LDS.org Church-service missionary opportunity page], this wiki page, and will include it in articles and newsletters to find the right person for the position. You can also fill out the form below.

:'''LDSTech Missionary Opportunity Request'''
:* [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dGtaSzZtbWdycXZIVDNJSk9TLURLOHc6MA '''LDSTech Missionary Opportunity Form''']

==Questions and contacts==

If you need more information about Church-service missionary opportunities, contact Sister Cheryl Bottorff, LDSTech Missionary Coordinator, at [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org] or [mailto:cheryl.bottorff@ldschurch.org cheryl.bottorff@ldschurch.org].

{{note|LDSTech Contact Information:

Phone: +1-801-240-7373

Email: [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]}}

==Additional reading==
The following articles provide more information about LDSTech Church-service missions.
* [https://tech.lds.org/index.php/ldstech/1-miscellaneous/459-using-a-church-service-missionary-on-your-project Helping out projects as a Church service missionary]
* [https://tech.lds.org/index.php/component/content/article/1-miscellaneous/411-profile-of-a-technology-service-missionary Profile of a technology service missionary]
* [https://tech.lds.org/blog/480-new-church-service-missionary-opportunities-available Church-service missionary opportunities available]

Tech Missionary Opportunities

2014-10-28T13:11:08Z

Aebrown: Remove spaces in file links

[[File:Banner missionary.jpg|link=https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA]]

=='''CSM Opportunity of the Week--Web Developer, Church History'''==
The Church is currently looking for a Web Developer--Church History (opportunity 10838). This skilled developer should have practical and industry experience in a MarkLogic environment. The candidate should be comfortable working in a very fast pace and be nimble and agile in development cycles. The consecrated effort should be at least 15-20 hours a week for at least 6 months, but a year is preferred. The candidate needs to have 2 weeks of full-time training in the Riverton Office Building (ROB), Utah before starting to work remotely.

Required skills include:<ul>
<li style="margin: 0;">CS Bachelors or equivalent experience</li>
<li style="margin: 0;">2 years of Enterprise web application engineering experience</li>
<li style="margin: 0;">Java</li>
<li style="margin: 0;">Javascript</li>
<li style="margin: 0;">XHTML</li>
<li style="margin: 0;">CSS3</li>
<li style="margin: 0;">XML</li>
<li style="margin: 0;">XSLT</li>
<li style="margin: 0;">Web Services (REST)</li>
<li style="margin: 0;">XQuery (Marklogic)</li>
<li style="margin: 0;">Responsive design</li>
<li style="margin: 0;">Mobile Web</li>
<li style="margin: 0;">LESS</li>
</ul>
Optional skills include:<ul>
<li style="margin: 0;">Eclipse
<li style="margin: 0;">GIT
<li style="margin: 0;">Agile Methodology</li>
</ul>
If this sounds like the perfect opportunity for you, please fill out the LDSTech Missionary and Service Opportunities form (link below). For further information, click on Opportunity number 10838 below or call Sister Bottorff at 801-240-7373.

=='''International Full-Time Missions'''==
Full-time Foreign Technology Specialist Missionary Opportunities have been posted!! Full-time Area Technology Specialist missionaries are being requested world-wide. The current list of open opportunities are on page 6 of the below link.

:'''LDSTech Full-time Technical Missionary'''
:* [https://www.lds.org/bc/content/ldsorg/callings/missionary/senior-missionary/senior-missionary-opportunities.pdf?lang=eng#page=7 '''International Area Technology Specialist''' (ATS) '''see page 6''']

{| class="wikitable"
! ATS Area !! Fluent Language(s) || Updated
|-
| [[Media:Area_Technology_Specialist_Description_(Korea).Jan_2014.pdf‎ |Korea, Seoul]] || Korean and English || 24 OCT 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Pacific).pdf |Apia, Samoa]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Pacific).pdf |Suva, Fiji]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology Specialist_Description_(Pacific).pdf |Nuku'alofa, Tonga]] || English || 27 OCT 2014
|-
| [[Media:Area_Technology Specialist_Description_(Europe).pdf |Frankfurt, Germany]] || English and other European language || 27 OCT 2014
|-
|

Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission. Opportunities are for healthy seniors with no dependents who are able to finance their mission based on the area's mission cost.

You may also call 801-240-6226 for further information on ATS Senior Couple full-time foreign missionary opportunities.

=='''Current Church-Service Missionary Opportunities''' ==
If you desire to serve a Church-service mission, you can become a missionary for LDSTech. LDSTech missions are ideal for worthy people who work or have worked in the IT industry. You may be a young or young-at-heart tech expert who is worthy to serve a proselyting mission but cannot. You could also be a couple that is retired or on a leave of absence and looking for an opportunity to serve a mission. This could be an ideal place to serve. Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission.

The latest Church-Service Missionary opportunities are listed on LDS.org. To view the opportunities, on [http://lds.org LDS.org] go to '''Resources > Missionary > Church-Service Missionaries''', then click '''Browse All Opportunities'''. Or go directly to [http://servicemission.ldschurch.org http://servicemission.ldschurch.org]. In the Select an Interest drop-down box, select '''Information Technology and Computer Science'''.

For convenience, the following list shows the available LDSTech Church-Service Missionary opportunities. Each of these opportunities links to the [http://servicemission.ldschurch.org http://servicemission.ldschurch.org] site listed above.

==='''Work-from-Home Opportunities'''===
:'''Blackberry Developer for LDSTech''' {{service mission|10279}}

:'''Church History Web Developer for LDSTech''' {{service mission|10838}}

:'''Mission Coordinator for LDSTech''' {{service mission|12162}}

:'''MSR Designer for LDSTech''' {{service mission|12537}}

:'''LDS Tools for Windows Developer for LDSTech''' {{service mission|12794}}

:'''Writer for LDSTech''' {{service mission|12818}}

==='''Opportunities at the Riverton Office Building'''===
:'''Web Developer for LDSTech''' {{service mission|9996}}

:'''Oracle/SQL Server DBA for LDSTech''' {{service mission|10500}}

:'''Telephone Inventory Specialist for LDSTech''' {{service mission|12082}}

:'''Change Coordinator for LDSTech''' {{service mission|12528}}

:'''QA Engineer for LDSTech''' {{service mission|12555}}

:'''Android QA Engineers for LDSTech''' {{service mission|12662}}

:'''QA Testing Engineer for LDSTech''' {{service mission|12970}}

:'''Social Media Expert for LDSTech''' {{service mission|13031}}

If you have another IT skill and would still like to serve, there may be other opportunities available as well. Please call us at 801-240-7373 or email us at ldstech-mission@ldschurch.org.

==Time commitments==
Time commitments can be 6, 12, or 18 months. At the end of the term of service, you can extend the missionary commitment to continue serving.

==Skills==
The skills required to serve an LDSTech mission vary based on the opportunity. See the opportunity descriptions for each advertised position. Senior couples with varying technical skills are especially welcome. Many times one person may serve in one role on a project (for example, project leader) while the spouse serves in another role (for example, tester).

==Language requirements==
At this time, an LDSTech mission requires the ability to speak English. We also now have opportunities for those who speak other languages along with English, to help with special projects.

==Application process==
Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Profile] to let LDSTech know of your interest in serving a mission. When you fill out this form, LDSTech can help you through the mission process. If you have questions about an LDSTech mission, please send an email to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. If you prove to be a good fit for one of these positions, you will then complete the Church-service missionary application process. This process is described on the [https://www.lds.org/callings/missionary/church-service?lang=eng Church-Service Missionaries page on LDS.org]. In summary, the application process is as follows:

# First, you complete the [https://www.lds.org/bc/content/ldsorg/content/english/service/missionary-service/church-service-missionaries/form/pdf/recommendation-for-church-service-missionary-eng.pdf?lang=eng Recommendation Form for Church-service Missionaries].
# Upon receiving the completed recommendation forms, the bishop certifies your worthiness and concurs with the selected choice for service. He then signs the form and forwards it to the stake president.
# The stake president interviews you for worthiness, signs the recommendation form, and forwards it to the Church Service Missionary Office at Church headquarters for authorization to extend the call. (See Note below)
# The Stake President will receive your call letter and will extend the call to you. The stake president authorizes the bishop to set the new missionary apart.
# Church-service missionaries should then contact the operation where they will be serving. They are supervised and trained under the direction of the operation in which they serve. The stake president and bishop remain the ecclesiastical leaders for the member.

{{Note|To submit your Church-service mission application please ask your stake president for a copy and scan and email to Sister Noni Boyle (boylene@ldschurch.org) and the form will be forwarded to the Church Service Missionary Office. You may also fax it to 801-353-4350, with a cover letter to Sister Boyle. Sister Boyle will alert you when your call has been issued.}}

==Backlogs ==
If you've inquired about a mission or already submitted your papers and haven't heard back from LDSTech yet, please be patient. As we work to manage the numerous inquiries for LDSTech Church-service missions, we have found more interest than we have current opportunities for. This has been a pleasant surprise. More opportunities are being created on a regular basis. We will continue to do our best to match current opportunities with those who have matching skills and availability.

Most importantly, if you feel prompted to serve, don’t wait for us -– reach out and remind us of your desire to serve. When you do, please include a brief description of your availability and technical experience and skills. Many opportunities require service to be done at the Riverton, UT office building. If you have strong interest in one of the following opportunities, please let one of us know.

* Testers
* Software Developers
* Interaction Designers
* Writers
* Project Managers
* Business Analysts

If you are not able to serve at the [[Riverton Office Building]], but are still interested in an LDSTech Church-service mission, please be patient with us as we try to find more opportunities to serve from home. These opportunities will grow over time and we are excited about the growth.

=='''Requesting a Church-service missionary'''==
If you're a '''Church employee''' and would like to request a Church-service missionary for your group or department, send the position details and requirements to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. LDSTech administrators will post the details on the [http://servicemission.ldschurch.org LDS.org Church-service missionary opportunity page], this wiki page, and will include it in articles and newsletters to find the right person for the position. You can also fill out the form below.

:'''LDSTech Missionary Opportunity Request'''
:* [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dGtaSzZtbWdycXZIVDNJSk9TLURLOHc6MA '''LDSTech Missionary Opportunity Form''']

==Questions and contacts==

If you need more information about Church-service missionary opportunities, contact Sister Cheryl Bottorff, LDSTech Missionary Coordinator, at [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org] or [mailto:cheryl.bottorff@ldschurch.org cheryl.bottorff@ldschurch.org].

{{note|LDSTech Contact Information:

Phone: +1-801-240-7373

Email: [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]}}

==Additional reading==
The following articles provide more information about LDSTech Church-service missions.
* [https://tech.lds.org/index.php/ldstech/1-miscellaneous/459-using-a-church-service-missionary-on-your-project Helping out projects as a Church service missionary]
* [https://tech.lds.org/index.php/component/content/article/1-miscellaneous/411-profile-of-a-technology-service-missionary Profile of a technology service missionary]
* [https://tech.lds.org/blog/480-new-church-service-missionary-opportunities-available Church-service missionary opportunities available]

User talk:Miltonbneto

2014-09-04T02:54:17Z

Aebrown: respond

Hy, I'am a brazillian Mormon. I have this idea since a long time ago. But I never had a chance to share with the Church. I hope you enjoy the idea. My email is guruhide@gmail.com or miltonbneto@hotmail.com I'm allways on the facebook: Milton Siedler Bologna or Milton BOlonha Neto

MITO Project
https://tech.lds.org/wiki/images/d/d8/MITOProject.pdf

: No one is likely to see your suggestion here. You will get a much better response if you post on the [https://tech.lds.org/forum LDSTech Forum]. No one will join the discussion here. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 20:54, 3 September 2014 (MDT)

User talk:Hhartman

2014-09-04T02:49:57Z

Aebrown: respond

My ENSIGN ONLY GOES TO JULY, HOW DO I ADD AUG AND SEPT? -- [[User:Hhartman|Hhartman]] 08:49, 1 September 2014‎

: You will get a much better response posting questions on the [https://tech.lds.org/forum LDSTech Forum]. No one will join the discussion here. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 20:49, 3 September 2014 (MDT)

Local Unit Apps Help Options

2014-08-27T18:43:00Z

Aebrown: Reorganize help into a single comprehensive table; fix all the forum links

If you are having problems with an application, want to learn how to use it, or want ideas on how you can use it better, there are several options available.

== Help resources ==
{| class="wikitable"
! Application
! Official Help
! Discussion Forum
! Community Help
|-
| Notes
| [https://www.lds.org/help/support/applications/notes-on-ldsorg?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=19 Forum]
| [[Notes on LDS.org]]
|-
| Calendar
| [https://www.lds.org/help/support/applications/calendar?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=110 Forum]
| [[Calendar]]
|-
| Directory
| [https://www.lds.org/help/support/applications/directory?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=111 Forum]
| [[Directory]]
|-
| Newsletter
| [https://www.lds.org/help/support/applications/newsletter?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=136 Forum]
| [[Newsletter]]
|-
| Lesson Schedules
| [https://www.lds.org/help/support/applications/lds-maps?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=132 Forum]
| [[Lesson Schedules]]
|-
| Maps
| [https://www.lds.org/help/support/applications/lds-maps?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=113 Forum]
| [[LDS Maps]]
|-
| Leader and Clerk Resources
| [https://www.lds.org/help/support?lang=eng Help]
| [https://tech.lds.org/forum/viewforum.php?f=112 Forum]
| [[Leader and Clerk Resources]]
|}

=== Help documentation ===
These pages have detailed help documentation for each application. In some cases this may include other resources like tutorials, videos, presentations, or FAQ lists.

=== Discussion forums ===
Each project has its own discussion forum. Here you can ask others for help/ideas. You can also report issues you have found. If you are stuck, this is probably your best option. There is a large group of knowledgeable users willing to help answer questions, and these forums are often reviewed by the developers of the applications, so there is a good chance you could get your issue addressed directly.

=== Community articles ===
These articles are written by community members. Some of the articles include helpful videos.

==Application feedback==
Each application has its own feedback link (usually somewhere near the bottom of the page within the application). You can submit ideas, questions, or problems to this link. They will be reviewed and prioritized by volunteers or project team members. Due to limited resources, you may get a quicker response from the community by using the forums listed above.

==Phone support==
Technical support is available via phone as well. If you need immediate help, or have exhausted the other sources listed above, this is a good option. Phone support is usually oriented more toward clerks and leaders, so if you need to use this option, work through your local clerks or leadership and they can help you contact the help desk.

[[Category:LDS.org applications]]

Leader and Clerk Resources

2014-08-27T18:38:09Z

Aebrown: Aebrown moved page Leader Resources and Clerk Resources to Leader and Clerk Resources: Since leader and clerk resources are combined on a single site on LDS.org, the title should reflect this.

The '''Leader Portal '''on new.lds.org provides stake presidencies, bishoprics, executive secretaries, and clerks with access to helpful resources for their leadership callings. The resources include links to relevant applications, reports from MLS, calling lists, and tools for focusing on members. By consolidating these resources into one secure, online location, leaders can spend less time managing administrative details and more time ministering to members.

== Callings with Leader Portal access ==

Members with the following callings have access to the Leader Portal:
*Stake Presidency (President, 1st and 2nd Counselor)
*District Presidency (President, 1st and 2nd Counselor)
*Bishopric (Bishop, 1st and 2nd Counselor)
*Branch Presidency (President, 1st and 2nd Counselor)
*Executive Secretary
*Assistant Executive Secretary (Stake only)
*Clerk
*Assistant Clerk - Membership
*Assistant Clerk

Some callings do not currently have access but will have access in the near future. These callings include:
*Assistant Clerk - Finance
*Assistant Clerk - Technology Specialist
*Acting Ward/Branch Leaders
NOTE: Finance clerks do not yet have access because the Leader Portal still lacks financial tools.

In order to gain access to the Leader Portal the calling must be recorded in MLS with the appropriate [https://tech.lds.org/wiki/Callings#Difference_between_standard_positions_and_custom_positions standard] position.

== Accessing the Leader Portal ==

To access the Leader Portal:

# On [http://lds.org/ lds.org], go to '''Tools > Leader and Clerk Resources'''. Or go directly to [http://lds.org/leader lds.org/leader.]
# Sign in with your [http://ldsaccount.lds.org/ LDS Account].

The Leader Portal shows a toolbar and other resources for leaders.

As you explore the resources on the Leader Portal, you can return to the Leader Portal home page by clicking the '''home''' icon [[File:Homeicon.jpg]] and selecting '''My Calling'''.

== The Leader Portal Homepage ==
The following image shows the main features of the Leader Portal.

[[File:Homepage.png|frame|none|The Leader Portal appears for bishops, stake presidents, clerks, and secretaries when they go to Tools > Leader and Clerk Resources.]]

[[File:Box1.png]] '''Navigation bar.''' The navigation bar is specific to the leadership portal and contains links to applications, tools, and reports. These resources are explained in more detail in the following sections. The options on this toolbar will continue to grow and change as new resources and tools are added.

[[File:Box2.png]] '''Send a Message.''' The messaging system allows you to send a message to a member in your ward or stake. Start typing a member's name to see the available matches. The message will appear to be sent from your LDS Account e-mail address and will include a tagline in the message footer noting your name and calling. You can also send an e-mail message to a predefined list that appears, such as Stake Council or Stake Young Mens Presidency. These lists group together members by calling.

If members have selected to keep their contact information private, leaders will see a visual indicator letting them know the members prefer not to be contacted. For countries outside the European Union, member contact information is shown by default until a member chooses to make it private. For countries inside the European Union, it's the opposite: member contact information is private by default until a member chooses to show it. (This data privacy policy conforms to European Union data privacy directives.) See [https://tech.lds.org/wiki/Data_privacy_settings_in_Directory Data privacy setting in Directory] for more detail.

[[File:Box3.png]] '''Member Lookup.''' In the Member Lookup field, start typing the name of a member in your ward or stake. As soon as you type a few letters, a list of matches appears (for both first and last names). After you select a name, a pop-up box appears with details about the member, including family information, ordinance dates, and calling information.

[[File:Box4.png]] '''Communications.''' The Communications area shows official communications from Church Headquarters and messages from applications. Notifications from applications will contain links that take you directly into the application.

[[File:Box5.png]] '''Schedule.''' The schedule shows events from calendars you are subscribed to. The [http://new.lds.org/church-calendar calendar] allows you to create both public and private calendars. For example, you can create a Ward Activities Calendar or Temple Calendar that all members can see. However, you can also create private calendars that only you and those you select can see. Common private calendars include interview schedules and private meetings. The Leader Portal brings the details of all calendars into your immediate view. For more information about the calendar, see the [https://tech.lds.org/ldshelp/index.php5/Local_Unit_Calendar:_Introduction_to_the_Calendar/eng Calendar Help].

[[File:Box6.png]] '''Leadership Training Resources.''' The center of the Leadership Portal shows leadership training resources, such as from World Wide Leadership Training or other resources from the Priesthood Department. Church Headquarters can easily publish new materials in this section that are timely and relevant for leaders.

[[File:Box7.png]] '''Welfare Tools.''' This new feature provides bishops with information about welfare. Features are still being added.

[[File:Box8.png]] '''Church Handbooks.''' Users can access online versions of Church handbooks. Access is role-based. Only those who can obtain a hard copy will be able to view the online copy.

[[File:Box9.png]] '''Directory of Leaders.''' The Directory of Leaders gives you quick access to the Church Directory of Leaders (CDOL). This directory shows contact information for leaders across the Church, including clerks, bishops, seminary instructors, stake presidents, patriarchs, seventies, apostles, and more. You can see the leader's position, phone number, unit, and location.

== Resources ==
The Resources section on the navigation bar provides links to applications that can help with your calling.

[[File:Resources.png|frame|none|The Resources menu lists applications relevant to leaders.]]

Each application from this Resources menu is described briefly below.

'''Member Focus.''' Member Focus allows a leader (bishop or stake president) and executive secretary to keep track of individuals they're working with by listing the names in a convenient location. For example, suppose you're working with a priest named Joe to help advance him to the Melchizedek priesthood. You might add Joe to this list so you can periodically review his progress.

After you add a member's name to the list, you can click the member's name to see details about the member, including his or her family information, ordinances, and callings. In the Last Appointment field, you can note the date you last met with the individual. Although Member Focus doesn't allow you to make notes about members, you can click two links:

* ''Request Appointment:'' Sends a message to the executive secretary requesting an appointment with the member.
* ''Send Message:'' Sends a message directly to the individual (based on the contact information in MLS).

'''Interviews.''' Interviews shows you upcoming interviews that are scheduled with members. This is a simple application that allows executive secretaries to inform the bishop about the interviews that are scheduled.

'''Missionary Recommend Entry.''' The [http://lds.org/mss Missionary Online Recommendation System] allows bishops and stake presidents to move missionary candidates through the missionary submission process. You can add your comments in the system and submit the forms to the next level.

'''Church Directory of Organizations and Leaders.''' This directory (referred to as [[CDOL]]) contains a global database of leader contact information. CDOL allows leaders to quickly call one another for a variety of reasons, such as when evaluating callings, conducting disciplinary councils, administering welfare, submitting applications, and more.

'''Employment Resource Services.''' [http://ldsjobs.org Employment Resource Services] helps members find employment, education resources, and community resources. Members can view job listings, build profiles of job history and skills, and save job searches. This site also provides information resources for leaders to help unemployed members.

'''Temple Entry System.''' After issuing temple recommends to members, you use Temple Entry System to activate or deactivate the recommends.

'''Purchase Materials.''' Purchase Materials takes you to the new Online Store at [http://store.lds.org/ http://store.lds.org], where you can order supplies for your ward or stake, scriptures, garments and temple clothing, manuals, gospel study materials, and more.

'''Action and Interview List.''' This list compiles actions that need to be taken in a ward or stake. The following situations are highlighted: children approaching baptism age, unbaptized members, overdue Aaronic priesthood ordinations, young men approaching mission age, men who have not served a mission, and potential missionary couples.

'''Key Indicators.''' Key indicators shows a chart of key statistics, such as sacrament meeting attendance, home teaching, endowed adults with temple recommends, and so on. The chart allows you to layer the statistics on top of each other so you can compare and contrast trends.

== Membership ==
The Membership menu provides access to membership records and the Officers Sustained Form.

[[File:Homepage_membership.png|frame|none|]]

== Organizations ==
The Organizations menu shows reports about callings. These calling reports allow bishops and stake presidents to more quickly fill open callings, monitor existing callings, and identify members who need callings.

[[File:Homepage_organizations.png|frame|none|]]
There are a multitude of options to look at the organization. You can look at comprehensive lists or lists specific to an organization.

== Reports ==
The Reports menu shows common reports from MLS.
[[File:Reports.png|frame|none|The Reports menu shows many of the reports that were previously only available in MLS.]]

The following reports are currently available:

* Action and Interview List
* Unit Statistics
* Without Recommend
* Members Moved In
* Not Endowed
* Birthday List
* Quarterly Report
* New Member
* Key Indicators
* Temple Recommend Status
* Attendance Rolls

== Instruction ==
The Instruction menu provides leaders access to information on various subjects.
[[File:Homepage_instruction.png|frame|none|]]

== Roadmap ==
The information currently in the Leadership Portal is just the beginning. More of the information from MLS will continue to migrate online, in addition to home and visiting teaching modules, a leadership training library, and more. The calendar and directory will also be more integrated. These enhancements will take place in 2011 and beyond.

[[Category:Websites]]

ChurchofJesusChrist.org apps

2014-08-27T18:15:09Z

Aebrown: Fix external links to be wiki links (please don't ever use external links for wiki articles!); follow guidelines for section capitalization

<div style="margin: 10px 0px 0px 0px;">
<div style="text-align: center;">
==LDS.org applications==
</div>
<div style="font-size: 1.15em;">This page lists community-created help material for LDS.org applications, tools, and resources. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.</div>
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="100%">
<div style="margin: 0px 0px 0px 10px; border: 1px solid #31312B;">

<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #D1D3BA; font-size: 1.25em; padding-left: 10px; ">
=====Tools=====
</div>
* [[Calendar|Calendar Help]]
* [[Directory|Directory Help]]
* [[Newsletter|Newsletter Help]]
* [[Lesson Schedules|Lesson Schedules Help]]
* [[LDS Maps|Maps Help]]
* [[Notes on LDS.org|Notes and Journal Help]]
* [[Leader Resources and Clerk Resources]]
* [[LDS.org getting started guides]]
* [[LDS.org Tools menu]]
* [[Local Unit Apps Help Options]]
</td>
<td><div style="background-color: #D1D3BA; font-size: 1.25em; padding-left: 10px; ">
=====Other=====
</div>

* [[LDS.org Search]]
* [[Leadership Training Library]]
* [[LDS.org scriptures]]
* [[LDS Account]]
* [[Local Unit Application Beta Testing]]
* [[Technology Training User Group Files|Church Technology Training Lessons]]
</td>
</tr>
<tr>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__
__NOTITLE__

[[Category:LDS.org applications]]
[[Category:Portals]]

TechWiki:Wiki editing tutorial

2014-08-23T13:04:41Z

Aebrown: Update links that pointed to deleted our outdated content

The platform for LDSTech is a wiki, powered by [http://www.mediawiki.org MediaWiki]. Anyone can view the wiki, but you need to be signed in with your [[LDS Account]] to make edits. Working with the wiki requires you to be familiar with some basic wiki syntax, but it's easy enough for practically anyone to contribute, regardless of technical skills. This page provides instructions for adding and updating content on the wiki. There are about 20 different wiki skills to master, with a brief practice exercise to demonstrate mastery of each skill.

As you learn the wiki, feel free to experiment on this [[LDSTech:Sandbox page|shared sandbox page]] or on [[Special:Mypage/Sandbox|your own sandbox page]].

==Creating your user page==
Your user page shares information about yourself that you want others to know. For example, here's a sample user page: [[User:Aebrown]]. By reading the user page, you can find information about the person's role, interests, and contact information. This can help you evaluate the validity of the user's edits.

When you make edits to the wiki, the wiki shows your username next to edits in the version history for the page. To see the version history, click the '''History''' button above the page title. The history shows the edits and timestamps, with the users who made each of the edits. If the usernames appear in red and are underlined, it means the user hasn't yet created a user page. Without a user page, it's hard to know who is making edits to the wiki.

To create a user page:
# Log in to the wiki.
# Click your username that appears near the login section, or just this link: [[Special:MyPage]].
# Add some information about yourself.
# Click '''Create'''.

''PRACTICE: Create your user page.''

== Watching pages ==

To keep updated about edits to a specific wiki page, you can "watch" the page by clicking the '''Watch''' button above the page title. Every time someone updates the page, you will be notified by e-mail according to the e-mail address listed in in your [[Special:Preferences|preferences]].

''PRACTICE: Watch this page.''

==Setting your e-mail preferences==

If your email isn't configured correctly in your preferences, you won't receive e-mail notifications even if you are watching a page. To configure your e-mail preferences:
# Click '''My preferences''' (near the login area).
# On the '''User Profile''' tab, make sure your e-mail address is up to date.
# In the Email section of the User Profile tab, select the check boxes to set your notification preferences. (At the very least, select "E-mail me when a page on my watchlist is changed.")
# Click '''Save'''.

Note that when you have an e-mail address added to your preferences, other users can send you e-mail. When you view a user page (such as this one, [[user:Johnsonth]]), scroll to the Toolbox section of the footer and click ''E-mail this user''. If users don't have an e-mail address added to their preferences, the ''E-mail this user'' option will not appear in the Toolbox on their user page, and so you can't send them an e-mail.

''PRACTICE: Check your e-mail address and preferences to make sure your settings are up to date.''

== Editing articles ==

When you edit the wiki, you can choose to edit the entire page or just a section on the page. If you click the Edit button above the title, you edit the entire page. If you click the Edit button to the right of a section, you just edit that section.

When you make an edit, provide a brief summary of the edit. This allows people to quickly scan the list of edits on the [[Special:RecentChanges|Recent Changes]] to see the reasons for the edits.

To edit a page:
# Click the '''Edit''' button above the page.
# Make the changes.
# In the Summary section, briefly summarize your edits.
# To stay notified about changes to the page, select the '''Watch this page''' check box.
# Click '''Save page'''.

Because multiple people may be working on the same page, it's best to edit just the section you're updating. The chances of multiple people updating the same ''section'' at the same time are far fewer than the chances of multiple people editing the entire ''page'' at the same time. That's why each section has its own Edit section.

If multiple people edit the same content at the same time, and then click Save, the last person to save will be prompted to merge the changes in with the other updates.

''PRACTICE: Go to [[Special:MyPage|your user page]] and edit the page. Make an update and save it.''

==Creating pages==

On the wiki, you create a page by searching for it. When you search for the page, if there isn't a page with the same name, you're asked whether you want to create the page. This is the wiki's own way of prompting users to get involved in creating more wiki content. Note that the capitalization style for page names on this wiki follows the same conventions as Wikipedia: single case. Other than the first word and proper nouns, lowercase words in titles.

To create a page:
# In the search box, type the name of the page you want to create. (Note that capitalization matters. The page ''Dogs'' is different from the page ''dogs''.)
# The page you searched for appears as a red, underlined link. Click the link.
# Add some content, and then click '''Create''' to create the page.

You can also create a page by adding <nowiki>[[Page title]]</nowiki> on a page and saving it, where "Page title" is the name of the page you want to create. When you save the page, the link will appear red and underlined. Click the link to create the page.

''PRACTICE: Search for a hypothetical page name in the Search box. Note how the site prompts you to create the page it cannot find. Now go to your [[Special:MyPage|user page]], edit the page, and add a link to a page you want to create. Click the link to see how to create the page. However, do not actually create the page. This is a live site, so rather than creating unnecessary pages, make edits on your user page.

== Deleting pages==
Deleting pages requires administrative permissions. Instead of deleting a page, you "move" the page to a new location. When you click '''Move''', you can choose a new page title. By ''moving'' rather than ''deleting'' a page, any user who clicks on the link to the old page will be automatically redirected to the new page. This is because the old page will receive a "redirect" to point users to the new page.

''PRACTICE: Go to a [[Special:Random|random page]] and identify the location of the Move button. You can click the Move button above the title, but don't click the additional Move button on the Move page, which will actually move the page.''

== Making text bold or italic==

The wiki uses a special syntax for formatting. When you save a page, this syntax gets converted into HTML for the browser. To create bold or italic formatting, add ticks around a word, like this:
<pre>
'''bold formatting'''
''italic formatting''
</pre>

You can also use the B and I buttons on the editor toolbar.

''PRACTICE: On your [[Special:MyPage|user page]], bold and italicize a word.''

==Inserting lists==

To create a bulleted list, add an asterisk (*) at the start of each line, like this:
<pre>
* first item
* second item
* third item
</pre>

To create a numbered list, add a pound sign (#) at the start of each line, like this:
<pre>
# first item
# second item
# third item
</pre>

With numbered lists, make sure you don't have spaces between the lines, or the numbered lists will start over.

To insert a bulleted list within a numbered list, combine the two forms of syntax like this:
<pre>
# first item
#* bulleted list item 1
#* bulleted list item 2
# second item
# third item
</pre>

''PRACTICE: On your [[Special:MyPage|user page]], create a numbered list with a bulleted sublist on one of the list items.''

== Adding notes and tips ==

You can add notes before or after a procedure by adding
<pre>{{Note|Type your note here.}}
</pre>

When you style notes this way, the note calls a template that styles the note with more formatting.

Here's what a note looks like:

{{Note|This is a sample note.}}

''PRACTICE: On your [[Special:MyPage|user page]], add a note.''

==Adding links to wiki pages==

To add a link to another page, enclose the page name in double brackets, like this:
<pre>
[[LDSTech:Manual of Style]]
</pre>

You can also change the text of the link by adding a pipe after the page name. If you want the link to just say "Manual of Style" rather than "LDSTech:Manual of Style" you would write the link like this:
<pre>
[[LDSTech:Manual of Style|Manual of Style]]
</pre>

''PRACTICE: On your [[Special:MyPage|user page]], add a link to this page.''

==Adding links to external pages==

Creating an external link (to a site such as byu.edu) is similar to creating an internal link but with a couple of minor differences. Rather than two square brackets, you use single brackets. And rather than a pipe separating the link from the link's text, you just use a space. Here's an example:

<pre>
[http://byu.edu BYU's website]
</pre>

''PRACTICE: On your [[Special:MyPage|user page]], add a link to your blog or other website. If you don't have a website, add a link to your favorite website.''

== Inserting subheadings ==
To create a subheading on a page, surround the subheading with two equals signs, like this:

<pre>
== Subheading title ==
</pre>

This creates an h2 style around the subheading. You can create a third level subheading by using three equals signs. Avoid using just one equals sign, which would result in an h1 subhead style.

MediaWiki automatically generates a table of contents (TOC) when you have at least four subheadings on a page. The general style on the wiki is to show the TOC after an introductory paragraph. You can force the display of the table of contents by adding <nowiki>__TOC__</nowiki> where you want it to appear. To remove the automatic display of the TOC, include <nowiki>__NOTOC__</nowiki> on the page.

''PRACTICE: On your [[Special:MyPage|user page]], add two levels of headings.''

==Embedding images==
Adding an image requires two separate steps: first you upload the image using the '''Upload file''' link within the Toolbox menu in the footer. Then you embed the image by adding the following code, where sample.png is the name of the uploaded image file:

<pre>
[[File:sample.png]]
</pre>

You can add additional parameters for the image file as well, such as a border, alignment, and caption. To add these parameters, separate each parameter with a pipe, such as this:

<pre>
[[File:sample.png|frame|none|This is my caption.]]
</pre>

Frame will add a border around the image and caption area. None specifies no alignment (type "right" or "left" to specify right or left alignment). The final text constitutes the caption.

To add an image:
# Hold down the '''Ctrl''' key and click ''Upload file'' in the footer. A new tab opens with the file upload box.
# Click '''Choose File'' and select the file you want to upload.
# After uploading the file, embed the image on a page by adding <nowiki>[[File:sample.jpg]]</nowiki>, where sample.jpg is the name of the image.
# To add parameters to the image, add this information in pipes following the image name: <nowiki>[[File:sample.jpg|frame|none|This is my caption.]]</nowiki> Frame adds a border around the image with a caption area. ''None'' specifies the alignment. You can also type right or left here. The final text is the caption.
# Click '''Save page.'''

Note that you can put a width parameter for the images, but if you also include a frame, the width parameter does not work.

If you're embedding an image within a numbered list, you can avoid breaking the list's numbering sequence by adding the image code at the end of a list item rather than on a new line. The "none" alignment parameter in the image code will force the image to display on its own line, but it won't break the numbering sequence.

Here's an example:

Do these steps:
# This is the first step.
# This is the second step. [[File:Ldstechlogo.png|LDSTech logo|frame|none|LDSTech logo]]
# This is the third step.
# This is the fourth step.

The code that produces this is as follows:
<pre>
Do these steps:
# This is the first step.
# This is the second step. [[File:sample.jpg|frame|none|This is my caption.]]
# This is the third step.
# This is the fourth step.
</pre>

{{Note|In general, keep images to about 600px in width. Otherwise, the image will not fit with a sidebar. Also, rather than using width parameters with the image, which merely resize the image in the browser, resize your image before uploading it. This way the image file size will be smaller.}}

''PRACTICE: Embed the LDSTech logo [[File:Ldstechlogo.png|LDSTech logo]] on your [[Special:MyPage|user page]]. You don't need to re-upload the image file, but you can if you want to.''

== Discussing pages ==

Each page has a corresponding Discussion page that allows you to have a discussion about the page's content without actually changing or adding your comments and questions to the official page's content. To view the discussion page, click '''Discussion''' above the page title.

To indent your response to a question on the Discussion page, add a colon before your response. To double indent your response, add two colons. After your response, add four tildes (<nowiki>~~~~</nowiki>) to sign your name. Your name links to your profile page.

''PRACTICE: View the Discussion page for this page. Now go to the Discussion page for your [[Special:MyPage|user page]]. Ask a question, and then provide an indented response to the question and sign your name.''

== Adding a sidebar ==

Mediawiki allows you to create templates that you can then embed into pages. The sidebar that you see on many pages, for example on the [[LDS.org applications]] documentation, is created with a template. Creating a sidebar template can be helpful if you have a collection of pages that you want to group together. After you create a template, you embed it on a page by adding <nowiki>{{templatename}}</nowiki> on the page, where templatename is the name of your template.

To create a sidebar, it's best to simply copy an existing sidebar (like the calendar sidebar) and make changes.

''PRACTICE: View the template for the calendar by searching for [[Template:ldsorgapps]]. Now go to a [[LDS.org applications]] page and click edit. Look for the <nowiki>{{ldsorgapps}}</nowiki> template code. Now embed the LDS.org applications sidebar on your [[Special:MyPage|user page]], and then remove it.''

==Adding pages to categories==
You can tag each wiki page with one or more categories. Categories group together a collection of pages that all belong to the same category. For example, the [[:Category:LDSTech Conference]] category shows all pages that are tagged with <nowiki>[[Category:LDSTech Conference]]</nowiki>.

Mediawiki's structure prompts you to nest categories into progressively more general categories until you reach the top, like an inverted tree.

The category a page is in appears near the bottom of the page.

''PRACTICE: Look at the [[LDSTech Conference]] page. Locate the category at the bottom. Trace the category up the hierarchy until you reach the top level. The navigate back down to through the categories back to the LDSTech Conference homepage.''

==Viewing Special Pages==
Mediawiki has a collection of "Special Pages" that provide content management functions for managing the content on the wiki. To view these [[Special:SpecialPages|Special Pages]], click the ''Special Pages'' link in the Toolbox section of the footer.

You can click a variety of links to look at the content. For example, you can view the longest or shortest pages, pages that are orphaned (have no links) or which have the fewest revisions. These special pages can help you locate problem points on the wiki.

''PRACTICE: Go to the Special Pages section and find the oldest page on the wiki.''

==Formatting tables==

Inserting tables on the wiki is a little more complicated than the other wiki syntax. Here's a sample table:
{|
!first column name
!second column name
|-
|first row, first column
|first row, second column
|-
|second row, first column
|second row, second column
|-
|third row, first column
|third row, second column
|}

Here's what that table's wiki syntax looks like:
<pre>
{|
!first column name
!second column name
|-
|first row, first column
|first row, second column
|-
|second row, first column
|second row, second column
|-
|third row, first column
|third row, second column
|}
</pre>

The <nowiki>{|</nowiki> announces the start of the table and the <nowiki>|}</nowiki> ends the table.

The <nowiki>!</nowiki> indicates column name (optional).

The <nowiki>|-</nowiki> indicates the start of a row. The | is a column in that row.

You can also add style tags to create custom styles for tables. If you're creating a new table, it's often easiest to just copy over the code from an existing table.

''PRACTICE: Copy the table that appears on the [[LDSTech Conference live session streams|live session streams]] page and embed it onto your [[Special:MyPage|user page]]. Change the column names. Then remove the table.

==View user contributions==
You can view a list of all your contributions by clicking the ''My Contributions'' link near the login area. This shows you all the edits you've made to the wiki.

You can also view contribution links from other users as well. When you view someone's user page (for example, [[user:Aebrown]], click the ''User Contributions'' link in the footer. This shows a list of just that user's contributions.

When you view the page history, you can also see a list of the user's contributions by clicking the ''contribs'' link next to the username. This can give you a quick idea about the user's credibility and authority to make edits to a page.

''PRACTICE: Go to a [[Special:Random|Random]] page on the wiki and look at the history of the page. Look at the list of contributions made by the last user to edit the page. Try and see if you can e-mail the user.''

==Get involved==
Now that you've completed the wiki editing tutorial, it's time to get involved. The [[LDSTech:Community Portal]] lists current needs for the wiki. There's a link to the Community Portal in the site's footer. You can see various efforts to adding or maintaining content.

''PRACTICE: Browse the Community Portal and find a task that interests you.''

[[category:LDSTech Administration]]

Template:Ldsorgapps

2014-08-23T02:02:23Z

Aebrown: Add LDS Maps

<div class="sidebar2">
<p class="heading">LDS.org Applications</p>
<p class="editsidebar">[{{fullurl:Template:ldsorgapps|action=edit}} Edit]</p>
<div class="sidebar2body">
* [[Calendar|Calendar]]
* [[Directory|Directory]]
* [[Lesson Schedules|Lesson Schedules]]
* [[LDS Maps|Maps]]
* [[Newsletter|Newsletter]]
* [[Notes on LDS.org|Notes]]
</div>
</div>
<noinclude>
== Documentation ==
Use this template to include an index for [[:Category:LDS.org applications|LDS.org application]] help topics within the wiki. This index will appear in the top right corner of the article page.

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{ldsorgapps}}</nowiki>'''.
[[Category:Index box templates|ldsorgapps]]
</noinclude>
[[Category:LDS.org applications]]

Notes on ChurchofJesusChrist.org

2014-08-23T01:45:58Z

Aebrown: Add nav box

{{ldsorgapps}}
Click here for the [https://www.lds.org/help/support/applications/notes-on-ldsorg?lang=eng official help content].

To see current discussions about Notes, visit the [https://tech.lds.org/forum/viewforum.php?f=19 Notes and Journal, and Online Scriptures] Forum.

== Notes tutorials ==

Submitted by members of the LDSTech community. Add your Notes tutorial to the table below:

{|class="ldstechtable sortable"
!Title
!Date
!Format
!Creator
|-
| [https://www.youtube.com/watch?v=EvOQdUE2CCA Introduction to My Study Notebook]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=4qxUR6GOHds Highlight a Passage]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=l2pq_Q9WHkY About Tags]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=BEMsLXqfqBw Add a Journal Entry]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=R4rpWlSHnlc Mark Content from an iPhone]
| 2011-JUL-18
| YouTube Video
| LDSTech
|}

[[Category:Notes on LDS.org]]

Template:Ldsorgapps

2014-08-23T01:44:04Z

Aebrown: Created page with "<div class="sidebar2"> <p class="heading">LDS.org Applications</p> <p class="editsidebar">[{{fullurl:Template:ldsorgapps|action=edit}} Edit]</p> <div class="sidebar2body"> * [..."

<div class="sidebar2">
<p class="heading">LDS.org Applications</p>
<p class="editsidebar">[{{fullurl:Template:ldsorgapps|action=edit}} Edit]</p>
<div class="sidebar2body">
* [[Calendar|Calendar]]
* [[Directory|Directory]]
* [[Lesson Schedules|Lesson Schedules]]
* [[Newsletter|Newsletter]]
* [[Notes on LDS.org|Notes]]
</div>
</div>
<noinclude>
== Documentation ==
Use this template to include an index for [[:Category:LDS.org applications|LDS.org application]] help topics within the wiki. This index will appear in the top right corner of the article page.

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{ldsorgapps}}</nowiki>'''.
[[Category:Index box templates|ldsorgapps]]
</noinclude>
[[Category:LDS.org applications]]

Notes on ChurchofJesusChrist.org

2014-08-23T01:38:33Z

Aebrown: Fix link

Click here for the [https://www.lds.org/help/support/applications/notes-on-ldsorg?lang=eng official help content].

To see current discussions about Notes, visit the [https://tech.lds.org/forum/viewforum.php?f=19 Notes and Journal, and Online Scriptures] Forum.

== Notes tutorials ==

Submitted by members of the LDSTech community. Add your Notes tutorial to the table below:

{|class="ldstechtable sortable"
!Title
!Date
!Format
!Creator
|-
| [https://www.youtube.com/watch?v=EvOQdUE2CCA Introduction to My Study Notebook]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=4qxUR6GOHds Highlight a Passage]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=l2pq_Q9WHkY About Tags]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=BEMsLXqfqBw Add a Journal Entry]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=R4rpWlSHnlc Mark Content from an iPhone]
| 2011-JUL-18
| YouTube Video
| LDSTech
|}

[[Category:Notes on LDS.org]]

Notes on ChurchofJesusChrist.org

2014-08-23T01:37:01Z

Aebrown: Add videos

Click here for the [https://www.lds.org/help/support/applications/directory?lang=eng official help content].

To see current discussions about Notes, visit the [https://tech.lds.org/forum/viewforum.php?f=19 Notes and Journal, and Online Scriptures] Forum.

== Notes tutorials ==

Submitted by members of the LDSTech community. Add your Notes tutorial to the table below:

{|class="ldstechtable sortable"
!Title
!Date
!Format
!Creator
|-
| [https://www.youtube.com/watch?v=EvOQdUE2CCA Introduction to My Study Notebook]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=4qxUR6GOHds Highlight a Passage]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=l2pq_Q9WHkY About Tags]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=BEMsLXqfqBw Add a Journal Entry]
| 2011-JUL-17
| YouTube Video
| LDSTech
|-
| [https://www.youtube.com/watch?v=R4rpWlSHnlc Mark Content from an iPhone]
| 2011-JUL-18
| YouTube Video
| LDSTech
|}

[[Category:Notes on LDS.org]]

Notes on ChurchofJesusChrist.org

2014-08-23T01:24:34Z

Aebrown:

My Study Notebook

2014-08-23T01:20:13Z

Aebrown: Aebrown moved page My Study Notebook to Notes on LDS.org: New official title for this feature

#REDIRECT [[Notes on LDS.org]]

Notes on ChurchofJesusChrist.org

2014-08-23T01:20:13Z

Aebrown: Aebrown moved page My Study Notebook to Notes on LDS.org: New official title for this feature

Help material for My Study Notebook has moved here: [https://ue.ldschurch.org/ldsapphelp/notesandjournal https://ue.ldschurch.org/ldsapphelp/notesandjournal].

User talk:Tacybee

2014-08-14T01:30:35Z

Aebrown:

== Forgot my pin ==
I forgot my pin to access LDS Tools on my Android phone. What can I do? -- [[User:Tacybee|Tacybee]] 12:05, 13 August 2014‎

: Please don't post questions in the main namespace of the wiki. You're much better off asking questions on the LDSTech Forum. In this case, please post your question in the [https://tech.lds.org/forum/viewforum.php?f=116 Android LDS Tools forum]. Many more people will see your question there. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 19:30, 13 August 2014 (MDT)

User talk:Tacybee

2014-08-14T01:25:37Z

Aebrown: Aebrown moved page Fogot my pin to User talk:Tacybee: Questions don't belong in main namespace

I forgot my pin to access LDS Tools on my Android phone. What can I do?

LDSTech2014 contest

2014-05-09T09:56:35Z

Aebrown: Fix second-level bullets

[[image:Contest_announce_page.png|400px|right]]New for 2014, the LDSTech-sponsored '''Gospel Games & Apps Development Contest''' culminates at the LDSTech Conference 2014.

LDSTech encourages developers of all levels and abilities to join in this contest to '''Create*Something*Worthy'''. From "name that tune" to "where are we?" to "scripture golf", if you have an idea for a gospel or Church related software application, now is the time to make it happen!

==Categories and awards==
{{ldstechconference2014}}
[[image:game_quiet_time.png|230px|left]]Games and Apps may be developed for Apple, Android, Windows, or online platforms in the following categories:
* Preschool
* Primary
* Teen
* Family
* Gospel Learning and Life

Awards, prizes, and recognition will be offered for each category, plus additional awards for teen, senior, and first time creators. And of course, there's the personal satisfaction you'll receive from your accomplishment!

==[[apps ideas|Starter ideas]]==
Since the gospel is infinite, so are the possibilities for gospel-related applications and games. See the '''[[apps ideas|idea and wish list page]]''' for specific starter ideas (or to add ideas for apps you'd like to see).
* Be creative!
* Find ideas from existing popular apps and improve them -- '''''"create something worthy"'''''. [[image:early_learning.png|300px|right]]
* What kinds of games and apps could help you, your children, your grandchildren, or others:
** have gospel-oriented fun?
** strengthen testimonies?
** develop personally?
** enjoy graphic-violence-free leisure and play time?
** serve more effectively?
** connect with gospel and Church themes rather than worldly themes?

==Rules==

* Timeline:
** The App must not be commercially available prior to May 1, 2014, although it may be a “significant” upgrade to a version available prior to 5/1/2014.
** You must submit the [[file:2014_Game_Contest_Application|Contest Application form]] (contest registration form) between 6/1/2014 and 10/1/2014.
** The App must be publicly available on commercial sites (iStore, Google Play, Windows Store) or other online locations by 10/10/2014 (allow sufficient time for "store" approvals).
** You must submit the [[file:2014_Game_Contest_Submission|Submission Form]] between 6/1/2014 and 10/10/2014.
* The App may not utilize, share, or transmit any Church membership data.
* You must follow copyright and licensing restrictions on all third party intellectual property.
* The App must not contain any inappropriate content, malware, etc.
* You are not required to attend the [[LDSTech Conference 2014|LDSTech Conference]], but it would be great to do. You'll need to [[LDSTech Conference 2014 registration|register to attend]]. Rooms will be available if you'd like to demonstrate your creation.
* A free version must be available, or 25 free/evaluation copies must be available from October 10 through October 17, for judging and demonstrating at the LDSTech Conference.
* The App must include a disclaimer of any ownership by or affiliation with the Church of Jesus Christ of Latter-day Saints.
* '''Note that you remain the owner of anything you create; you are not transferring ownership nor licensing any rights to The Church of Jesus Christ of Latter-day Saints.'''

==Contact Information==

Direct all questions, application forms, and submission forms to '''gameappcontest@ldschurch.org'''.

Visit the official Facebook and Twitter pages.

File:Banner.png

2014-04-30T01:07:50Z

Aebrown: Aebrown uploaded a new version of "File:Banner.png": Reverted to version as of 11:30, 25 January 2014

A banner graphic taken running Gospel Library for Windows 8.1

User:Juanquisito

2014-03-26T22:18:59Z

Aebrown: Standardize formatting, add link

== Juan Carlos Calderón Cuellar ==
'''Presidente [[Bolivia LDSTech Chapter]]'''

Me apasiona la tecnología, comencé a programar en Basic, Pascal y Delphi. Actualmente trabajo con el lenguaje Java en una compañía de desarrollo de software llamada MNEMO, como desarrollador, líder de equipo y responsable de I+D+i.

Otra de mis pasiones es el manejo de equipos de sonido como consolas y micrófonos, la producción y post-producción de audio y video, soy locutor y DJ en mi tiempo libre.

Una de mis pasiones y sin duda la más importante en mi vida, es mi esposa Claudia, de quien siempre tengo apoyo en lo que hago.

Priesthood Line of Authority

2014-03-20T21:09:48Z

Aebrown: Undo revision 43170 by Kikambif (talk) -- remove personal information

A '''Priesthood Line of Authority''' shows who ordained an individual and who in turn ordained them and so on back to the Lord.

Thousands of ordinances are performed weekly throughout the Church. These ordinances are to be performed by priesthood holders who have been properly ordained and properly authorized by one who has the keys to authorize the ordinance under the direction of the prophet. Therefore, a priesthood authority line traces a priesthood holder's authority from the person ordaining him back to the Lord ([http://scriptures.lds.org/en/dc/42/11#11 D&C 42:11]).

== Definition of Line of Authority ==
The line of authority is traced through the office held at the time of the ordination:<ref>See ''Ensign'', August 1976, [http://www.lds.org/ensign/1976/08/church-policies-and-announcements?lang=eng Priesthood Line of Authority].</ref>

<blockquote>If a priesthood bearer desires to trace his own line of authority, he should pursue his current office in the priesthood — not former offices. Bishops and patriarchs should trace their line of authority as high priests. In completing an authority line, each step should go back through the office held by the person at the time he performed the ordination. It is not appropriate to trace the line of authority in cases of setting apart or for other ordinances.</blockquote>

== How to request a copy of a Priesthood Line of Authority ==
=== Methods of contacting ===
Contact Church headquarters in one of the following ways:

* '''Email''': [mailto:lineofauthority@ldschurch.org?subject=PLA lineofauthority@ldschurch.org] with PLA in the subject line. In return you'll receive a form to fill out and return (this is an automated reply to any message that contains "PLA" in the subject line).

* '''Phone''': 800-453-3860 ext 23500 then choose option 6, then option 3. After the message and tone leave a voice mail message with your fax number or mailing address. The form will be mailed to you.

=== Helpful information ===
Be prepared with as much of the following information as possible (your [[Ward Clerk|ward clerk]] MAY be able to help you with some of this information):

# Full name of the priesthood holder
# Date of birth
# Current ward and stake
# Address and Zip Code
# Elder ordination date
# Who performed the Elder ordination
# Ward and stake where Elder ordination was performed
# High Priest ordination date if applicable
# Who performed the High Priest ordination
# Ward and stake where High Priest ordination was performed
# Any Melchizedek Priesthood ordination performed by the priesthood holder

== See also ==
[[Recording ordinances]]

== References ==
<references />

[[Category:Membership]]

Tech Missionary Opportunities

2014-02-19T19:53:20Z

Aebrown: Make PDF link go straight to page 7

[[File:Banner missionary.jpg|link=https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA]]

=='''Church Service Mission Opportunity of the Week'''==
We are currently looking for two or three individuals to serve as Telephone Inventory Specialists. This position is 15-20 hours a week in the Riverton Office Building and involves working with headquarters departments, facilities managers, stakes, and wards to account for telecommunications services and associated costs. You would be spending a lot of time on the phone talking to people all around the country, as well as working with team members to analyze inventories, maintain contract information, and maintain billing records.
The good news is that you don’t have to be a technical geek—the most important thing is excellent communication skills, both verbal and written. Some basic computer skills will be needed, especially familiarity with Microsoft Word and Microsoft Excel. If this sounds like where you need to be, please fill out the LDSTech Missionary and Service Opportunities form (link below). For further information, click on Opportunity number 12104 below or call Sister Bottorff at 801-240-7373.

=='''International Full-time Missions'''==
Full-time Foreign Technology Specialist Missionary Opportunities have been posted!! Full-time Area Technology Specialist missionaries are being requested world-wide. The current list of open opportunities are on page 7 of the below link.

:'''LDSTech Full-time Technical Missionary'''
:* [https://www.lds.org/bc/content/ldsorg/callings/missionary/senior-missionary/senior-missionary-opportunities.pdf?lang=eng#page=7 '''International Area Technology Specialist''' (ATS) '''see page 7''']

{| class="wikitable"
! ATS Area !! Fluent Language(s) || Updated
|-
| [[Media:Area_Technology_Specialist_Description_-_BRAZIL.12.13.pdf‎|Brazil, São Paulo]] || Portuguese and English || 18 FEB 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Caribbean).pdf‎|Dominican Republic Santo Domingo]] || Spanish and English || 18 FEB 2014
|-
| [[Media:Pacific_Area_Technology_Specialist_Job_Description.pdf‎|Pacific Islands (Samoa, Tonga)]] || English (Island languages helpful) || 18 FEB 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Central_America).pdf‎|Guatemala]] || Spanish and English || 18 FEB 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Japan).Jan_2014.pdf‎|Japan, Tokyo]] || Japanese and English || 18 FEB 2014
|-
| [[Media:Area_Technology_Specialist_Description_(Korea).Jan_2014.pdf‎ |Korea, Seoul]] || Korean and English || 18 FEB 2014
|}

Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Missionary and Service Opportunities form] to let LDSTech know of your interest in serving a mission. Opportunities are for healthy seniors with no dependents who are able to finance their mission based on the area's mission cost.
You may also call 801-240-6226 for further information on ATS Senior Couple full-time foreign missionary opportunities.

== '''Current Church-service missionary opportunities''' ==
If you desire to serve a Church-service mission, you can become a missionary for LDSTech. LDSTech missions are ideal for worthy people who work or have worked in the IT industry. You may be a young or young-at-heart tech expert who is worthy to serve a proselyting mission but cannot. You could also be a couple that is retired or on a leave of absence and looking for an opportunity to serve a mission. This could be an ideal place to serve. Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Missionary and Service Opportunities form] to let LDSTech know of your interest in serving a mission.

The latest Church-Service Missionary opportunities are listed on LDS.org. To view the opportunities, on [http://lds.org LDS.org] go to '''Resources > Missionary > Church-Service Missionaries''', then click '''Browse All Opportunities'''. Or go directly to [http://servicemission.ldschurch.org http://servicemission.ldschurch.org]. In the Select an Interest drop-down box, select '''Information Technology and Computer Science'''.

For convenience, the following list shows the available Church-Service Missionary opportunities. Each of these opportunities links to the [http://servicemission.ldschurch.org http://servicemission.ldschurch.org] site listed above.

:'''QA Automation Engineer for LDSTech'''
:* {{service mission|9835}}

:'''Web Developer for LDSTech'''
:* {{service mission|9996}}

:'''QA Analyst for LDSTech'''
:* {{service mission|10067}}

:'''MS Sharepoint Developer for LDSTech'''
:* {{service mission|10080}}

:'''Website Content Publishing for LDSTech'''
:* {{service mission|10156}}

:'''iOS Developer for LDSTech'''
:* {{service mission|10235}}

:'''Blackberry Developer for LDSTech'''
:* {{service mission|10279}}

:'''Social Service Media for LDSTech'''
:* {{service mission|10399}}

:'''Oracle/SQL Server DBA for LDSTech'''
:* {{service mission|10500}}

:'''Mobile App Developer for LDSTech'''
:* {{service mission|10620}}

:'''ASP, .Net, C# Web Developer for LDSTech'''
:* {{service mission|10837}}

:'''Church History Web Developer for LDSTech'''
:* {{service mission|10838}}

:'''Application Test Engineer for LDSTech'''
:* {{service mission|10839}}

:'''Portfolio Assistant for LDSTech'''
:* {{service mission|11115}}

:'''Product Knowledge Specialist for LDSTech'''
:* {{service mission|11116}}

:'''Product Knowledge Specialist - LUA QA Support for LDSTech'''
:* {{service mission|11175}}

:'''WordPress Developer with LDSTech'''
:* {{service mission|11415}}

:'''Web Application Tester for LDSTech'''
:* {{service mission|11420}}

:''' MH Tech Generalist for LDSTech'''
:* {{service mission|11646}}

:'''MH Tech Language Specialist for LDSTech'''
:* {{service mission|11655}}

:'''English Content Quality Assurance for LDSTech'''
:* {{service mission|11953}}

:'''Telephone Inventory Specialist for LDSTech'''
:* {{service mission|12082}}

:'''PeopleSoft Developer for LDSTech'''
:* {{service mission|12104}}

:'''QA Engineer for LDSTech'''
:* {{service mission|12108}}

:'''LDSTech Mission Coordinator'''
:* {{service mission|12162}}

:'''ADXStudio Developer'''
:* {{service mission|12166}}

:'''CRM Developer for LDSTech'''
:* {{service mission|12170}}

:'''Social Media Specialist for LDSTech'''
:* {{service mission|12284}}

:'''MH Tech Product Speclialist for LDSTech'''
:* {{service mission|12328}}

If you have another IT skill and would still like to serve, there may be opportunities available as well. Please call us at 801-240-7373 or email us at ldstech-mission@ldschurch.org.

== Locations==
Some opportunities allow candidates to work remotely. Check the opportunity description to determine if it can be worked on remotely or if it must be worked on in the [[Riverton Office Building]].

==Time commitments==
Time commitments can be 6, 12, or 18 months. At the end of the term of service, you can extend the missionary commitment to continue serving.

==Skills==
The skills required to serve an LDSTech mission vary based on the opportunity. See the opportunity descriptions for each advertised position. Senior couples with varying technical skills are especially welcome. Many times one person may serve in one role on a project (for example, project leader) while the spouse serves in another role (for example, tester).

==Language requirements==
At this time, an LDSTech mission requires the ability to speak English. We also now have opportunities for those who speak other languages along with English, to help with speical projects.

==Application process==
Please complete the [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dHJoRGVyVlRCX0N2emZzcl91QnlFM3c6MA LDSTech Missionary and Service Opportunities form] to let LDSTech know of your interest in serving a mission. When you fill out this form, LDSTech can help you through the mission process. If you have questions about an LDSTech mission, please send an email to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. If you prove to be a good fit for one of these positions, you will then complete the Church-service missionary application process. This process is described on the [https://www.lds.org/callings/missionary/church-service?lang=eng Church-Service Missionaries page on LDS.org]. In summary, the application process is as follows:

# First, you complete the [https://www.lds.org/bc/content/ldsorg/content/english/service/missionary-service/church-service-missionaries/form/pdf/recommendation-for-church-service-missionary-eng.pdf?lang=eng Recommendation Form for Church-service Missionaries].
# Upon receiving the completed recommendation forms, the bishop certifies your worthiness and concurs with the selected choice for service. He then signs the form and forwards it to the stake president.
# The stake president interviews you for worthiness, signs the recommendation form, and forwards it to the Church Service Missionary Office at Church headquarters for authorization to extend the call. (See Note below)
# The Stake President will received your call letter and will extend the call to the member. The stake president authorizes the bishop to set the new missionary apart.
# Church-service missionaries should then contact the operation where they will be serving. They are supervised and trained under the direction of the operation in which they serve. The stake president and bishop remain the ecclesiastical leaders for the member.

{{Note|To submit your Church-service mission application please ask your stake president for a copy and scan and email to Sister Noni Boyle (boylene@ldschurch.org) and the form will be forwarded to the Church Service Missionary Office. Sister Boyle will alert you when your call has been issued.}}

==Backlogs ==
If you've inquired about a mission or already submitted your papers and haven't heard back from LDSTech yet, please be patient. As we work to manage the numerous inquiries for LDSTech Church-service missions, we have found more interest than we have current opportunities for. This has been a pleasant surprise. More opportunities are being created on a regular basis. We will continue to do our best to match current opportunities with those who have matching skills and availability.

Most importantly, if you feel prompted to serve, don’t wait for us -– reach out and remind us of your desire to serve. When you do, please include a brief description of your availability and technical experience and skills. Many opportunities require service to be done at the Riverton, UT office building. If you have strong interest in one of the following opportunities, please let one of us know.

* Testers
* Software Developers
* Interaction Designers
* Writers
* Project Managers
* Business Analysts

If you are not able to serve at the [[Riverton Office Building]], but are still interested in an LDSTech Church-service mission, please be patient with us as we try to find more opportunities to serve from home. These opportunities will grow over time and we are excited about the growth.

=='''Requesting a Church-service missionary'''==
If you're a '''Church employee''' and would like to request a Church-service missionary for your group or department, send the position details and requirements to [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]. LDSTech administrators will post the details on the [http://servicemission.ldschurch.org LDS.org Church-service missionary opportunity page], this wiki page, and will include it in articles and newsletters to find the right person for the position. You can also fill out the form below.

:'''LDSTech Missionary Opportunity Request'''
:* [https://docs.google.com/a/tech.lds.org/spreadsheet/viewform?usp=drive_web&formkey=dGtaSzZtbWdycXZIVDNJSk9TLURLOHc6MA '''LDSTech Missionary Opportunity Form''']

==Questions and contacts==

If you need more information about Church-service missionary opportunities, contact Elder Craig Chapman, Coordinator for LDSTech missionaries, at [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org] or [mailto:Craig.Chapman@ldschurch.org Craig.Chapman@ldschurch.org].

{{note|LDSTech Contact Information:

Phone: +1-801-240-7373

Email: [mailto:ldstech-mission@ldschurch.org ldstech-mission@ldschurch.org]}}

==Additional reading==
The following articles provide more information about LDSTech Church-service missions.
* [https://tech.lds.org/index.php/ldstech/1-miscellaneous/459-using-a-church-service-missionary-on-your-project Helping out projects as a Church service missionary]
* [https://tech.lds.org/index.php/component/content/article/1-miscellaneous/411-profile-of-a-technology-service-missionary Profile of a technology service missionary]
* [https://tech.lds.org/blog/480-new-church-service-missionary-opportunities-available Church-service missionary opportunities available]