TechWiki - User contributions [en]

Setting Up a New Clerk Computer

2025-06-16T22:59:34Z

Sbradshaw: Added clarification for setup

> [[Meetinghouse Technology]] > [[Computers]]

== '''Overview''' ==
Most new Meetinghouse systems will come with Microsoft Autopilot provisioning enabled. This new technology allows systems to be set up and provisioned over the internet. If your computer does not have the provisioning tool pre-installed, it may be downloaded by [https://liveupdate.churchofjesuschrist.org/auth/churchsupportselfprovision.exe selecting this link]. If you are setting up a system that was purchased before August 2022, please contact your Stake Technology Specialist for help in resetting the computer. Once the system has been reset, you can set it up by starting with step 6 below. Please note that you will need to know your Church Unit Number to complete setup.

== '''Instructions''' ==
'''1. Connect any peripherals (monitor, keyboard, mouse) to the computer. Connect power and a wired connection to the internet if available. If necessary, you will be prompted to join a wireless network during set up.'''

'''2. Turn on the computer.'''

'''3. Windows setup will begin. If wireless internet access will be used, connect to a wireless network when prompted.'''

'''4. If the system has been configured for Autopilot, the following provisioning screen will appear on the display. If the Autopilot Provisioning Screen does not appear, complete the system set up by following Steps 6 and 7.'''

[[File:Autopilot Provisioning Screen.png]]

''Autopilot Provisioning Screen''

'''5. Click the “Continue Anyway” button as soon as it appears. The system will complete some tasks, reboot, and automatically login to an account called ChurchSupport. Skip to Step 8. '''

'''6. Follow steps 6 and 7 if Autopilot does not automatically run:'''

a. Select Region, Keyboard, and any other prompts for preferences. Agree to any licenses.

b. When prompted to sign in with Microsoft:

i. Windows 10: Click “Domain Join Instead” in the lower left corner of the screen.

ii. Windows 11: Click on Set up for work or school, Sign-in Options, then "Domain Join Instead."

c. When prompted, create an account called ChurchSupport.<ins> </ins>

d. Set the password for the new account and when prompted, create, and answer three security questions.

e. When prompted for privacy settings, leave the defaults, and click accept.

f. Select the “Not Now” button when prompted to allow Cortana.

g. The setup will complete, and you will be signed into the device.

'''7. Run ChurchSupportSelfProvision.exe'''

a. Most new clerk computers come ready for provisioning. If the machine was not purchased with the church self provisioning tool on it, it may be downloaded by [https://liveupdate.churchofjesuschrist.org/auth/churchsupportselfprovision.exe selecting this link].

b. Locate the https://liveupdate.churchofjesuschrist.org/auth/churchsupportselfprovision.exe file.

c. Right click on the file and select “Run as Administrator”

d. When prompted, click Yes to launch “ChurchSupportSelfProvision.exe”.

e. The ChurchSupportSelfProvision.exe application will download a few files and reboot the system. The system will then login using the ChurchSupport account created in step 6c. Enter the password for this account and press Enter.

f. Keep the default privacy settings and click Accept. The device will then display the desktop and launch Computer Asset Updater.

'''8. Complete the Computer Asset Updater (Part 1)'''

a. When automatically launched, the Computer Asset Updater will display the following:

[[File:Computer Asset Updater.png]]

''Computer Asset Updater''

b. Click on the “Please Select a Profile” pulldown menu and select the “Clerk Computer” entry.

c. You will then be prompted for elevated rights. Click OK.

d. You will receive another prompt to allow AssetUpdater.exe to run. Click Yes.

e. A new Computer Asset Updater window will appear.

'''9. Complete the Computer Asset Updater (Part 2)'''

a. The new Computer Asset Update will look like the graphic below:

[[File:Post Install Updater part 2.png]]

''Computer Asset Updater, Part 2''

b. Enter your Unit Number. This will be used to create a ward login on this device. If you do not enter your ward number, a randomly generated number will be created for your ward login. Select the appropriate entries for all pull-down menus marked with a red asterisk (*). Click Submit.

c. Multiple screens will open and close before displaying a Post Install wizard.

'''10. Complete the Post Install Wizard'''

a. Select Clerk Computer from the list of entries and click the OK button as shown below:

[[File:Post Install Wizard Popup.png]]

''Post Install Wizard Pop Up''

b. Several screens will open and close and the system will reboot automatically. If a password was set for the ChurchSupport account, type it when prompted – otherwise, press Enter with an empty password field.

c. Progress will be displayed in the Post Install Wizard as applications are installed on the device. Some settings will also be changed at this stage as well. See graphic below:

[[File:Windows Post Install Wizard.png]]

''Windows Post Install Wizard''

d. Do not close any windows or change any settings during this stage. As changes are made to the device, the wizard may move to the background. If desired, it can be moved to the foreground to monitor progress.

e. When complete, the Post Install Wizard will close, and the system will be rebooted.

'''11. On reboot:'''

a. Click on your Unit number in the lower left corner of the display. If you did not enter a ward number in step 9, select the account labeled Unit <random number>.

b. Press the Enter Key. The account has no password at this point.

c. You will be prompted to change the login password, click OK.

i. Enter a new password in the New password box.

ii. Press Tab

iii. Re-enter the password in the Confirm Password box.

iv. Press Enter

d. You will see a confirmation that the password has been changed.

e. Click OK and Accept the default privacy settings.

f. The system will now be ready for use.

[[Category:Meetinghouse Technology]]
[[Category:Computer]]

Global Services Department

2024-02-14T22:15:40Z

Sbradshaw: Made area headings bold so they're easier to see

{{DISPLAYTITLE:Global Services Department- Meetinghouse Support}}

> [[Meetinghouse Technology]]
{{Merge|Merge data from [[Global Service Center]]}}

The Global Services Department-Meetinghouse Support serves as a vital support hub within the Church, offering specialized assistance to technology specialists, clerks, and other unit leaders worldwide. With a focus on information technology (IT) solutions to include support for meetinghouse computers, networks, Church Network Manager (CNM), access points, firewalls, printers, and so on. Meetinghouse Support help others come unto Christ by providing exceptional customer service.

=='''Contacting Meetinghouse Support'''==
[[File:Gsd.png|thumb]]

In the US and Canada, Meetinghouse Support can be reached by calling 1-855-537-4357, for all other areas of the world refer to the table below.

Support numbers are grouped under areas of the world:

* North America
* Africa Southeast
* Africa West
* Asia
* Asia North
* Brazil
* Caribbean
* Central America
* Europe
* Europe East
* Mexico
* Pacific
* Philippines
* South America Northwest
* South America South
{| class="wikitable"
|'''Country'''
|'''Phone Number'''
|'''Meetinghouse Technology'''
|-
| colspan="3" |'''North America'''
|-
|US and Canada (toll free)
|1-855-537-4357
|√
|-
|US local and international
|1-801-240-4357
|√
|-
| colspan="3" |'''Africa Southeast'''
|-
|Kenya
|0800-22-01-12
|√
|-
|Réunion Island
|0800-99-0087-
|√
|-
|South Africa
|0800-991-457
|√
|-
|Zimbabwe
|0089-866-226-2299
|√
|-
| colspan="3" |'''Africa West'''
|-
|Ghana
|80012950
|√
|-
|Nigeria
|0800 537 248 724
|√
|-
|Sierra Leone
|1101-866-226-6234
|√
|-
| colspan="3" |'''Asia'''
|-
|Cambodia
|888-898-8144
|√
|-
|China North
|10800-852-1523
|√
|-
|China South
|10800-152-1523
|√
|-
|Hong Kong
|001-800-8674-0310
|√
|-
|India
|000-800-100-1131
|√
|-
|Indonesia
|001-803-1008-3464
|√
|-
|Malaysia
|00-800-8680-2360
|√
|-
|Pakistan
|877-901-8143
|√
|-
|Singapore
|800 852 6868
|√
|-
|Taiwan
|00-800-8678-1060
|√
|-
|Thailand
|001-800-8671-7040
|√
|-
| colspan="3" |'''Asia North'''
|-
|Guam
|1-866-678-2763
|√
|-
|Japan
|0120-895600
|√
|-
|Korea
|080-577-0880
|√
|-
| colspan="3" |'''Brazil'''
|-
|Brazil
|0800-891-4253
|√
|-
| colspan="3" |'''Caribbean'''
|-
|Barbados
|1-866-683-4116
|√
|-
|Dominica
|1-800-732-3664
|√
|-
|Dominican Republic
|1-866-799-7251
|√
|-
|Guadeloupe
|0800-99-00-11
|√
|-
|Puerto Rico
|1-855-537-4357
|√
|-
|Saint Kitts and Nevis
|1-866-683-4117
|√
|-
| colspan="3" |'''Central America'''
|-
|Belize
|0800-572-4687
|√
|-
|Costa Rica
|0800-0111-1013
|√
|-
|El Salvador
|800-7042
|√
|-
|Guatemala
|1-801-130-0013
|√
|-
|Honduras
|001-866-628-6691
|√
|-
|Nicaragua
|001-800-222-5347
|√
|-
|Panama
|800-7436
|√
|-
| colspan="3" |'''Europe Central'''
|-
|Armenia
|1-801-353-4840
|√
|-
|Austria
|00800-2950-2950
|√
|-
|Belgium
|00800-2950-2950
|√
|-
|Croatia
|0800-223-000
|√
|-
|Czech Republic
|800-142-827
|√
|-
|France
|00800-2950-2950
|√
|-
|Germany
|00800-2950-2950
|√
|-
|Greece
|0800-4414-1893
|√
|-
|Hungary
|(68) 001-8243
|√
|-
|Italy
|00800-2950-2950
|√
|-
|Luxembourg
|(8) 002-5347
|√
|-
|Netherlands
|00800-2950-2950
|√
|-
|Poland
|00800-2950-2950
|√
|-
|Romania
|0800-2950-2950
|√
|-
|Slovenia
|0800-2950-2950
|√
|-
|Spain
|00800-2950-2950
|√
|-
|Switzerland
|00800-2950-2950
|√
|-
| colspan="3" |'''Europe North'''
|-
|Denmark
|00800-2950-2950
|√
|-
|Finland
|00800-2950-2950
|√
|-
|Iceland
|800-8804
|√
|-
|Ireland
|00800-2950-2950
|√
|-
|Norway
|00800-2950-2950
|√
|-
|Portugal
|00800-2950-2950
|√
|-
|Sweden
|00800-2950-2950
|√
|-
|United Kingdom
|0808-169-7931
|√
|-
|Latvia
|800-2234
|√
|-
|Lithuania
|00800-2950-2950
|√
|-
|Estonia
|800-1000-2950
|√
|-
| colspan="3" |'''Europe East'''
|-
|Belarus
|810-800-1000-2950
|√
|-
|Kazakhstan
|810-800-1000-2950
|√
|-
|Russia
|8-800-100-2950
|√
|-
|Ukraine
|0-800-501-232
|√
|-
| colspan="3" |'''Mexico'''
|-
|Mexico
|800 266 0108
|√
|-
| colspan="3" |'''Pacific'''
|-
|American Samoa
|699-4473
|√
|-
|Australia
|0011-800-8680-5650
|√
|-
|Fiji
|1-800-8680-3950
|√
|-
|New Caledonia
|801-353-4835
|√
|-
|New Zealand
|0800 447 016
|√
|-
|Samoa—BlueSky
|800472
|√
|-
|Tahiti
|689 40 505 507
|√
|-
|Tonga—Digicel
|20360
|√
|-
|Tonga—TCC
|800473
|√
|-
| colspan="3" |'''Philippines'''
|-
|Philippine
|1-800-1-312-0028
|√
|-
| colspan="3" |'''South America Northwest'''
|-
|Bolivia
|800-10-0446
|√
|-
|Colombia
|01-800-912-0050
|√
|-
|Ecuador
|866-799-5504
|√
|-
|Peru
|0-800-52-764
|√
|-
|Venezuela
|0800-100-2983
|√
|-
| colspan="3" |'''South America South'''
|-
|Argentina
|0800-444-9783
|√
|-
|Chile
|800-646-783
|√
|-
|Paraguay
|800-537
|√
|-
|Uruguay
|000-411-005-9786
|√
|}

Global Service Center

2022-06-23T17:47:05Z

Sbradshaw: Change mentions of "Global Service Center" to "Global Services Department"

The '''Global Services Department''' (previously the Global Service Center) provides IT support, distribution ordering support, and local unit MLS support services. Please use the following contact for each of these services:

== Contacting the Global Services Department (GSD) ==

Most departments at the [https://www.churchofjesuschrist.org/help/support/meetinghouse-technology/my-calling-as-a-technology-specialist/global-service-department?lang=eng Global Services Department] can be reached by phone at '''1-855-LDS-HELP''' (1-855-537-4357) in the US and Canada.

For direct lines, specific department emails, or if you are located outside the US and Canada, see below:

=== [[Global Service Center - Distribution|Distribution]] ===
Problems with arrival or contents of your order from Distribution Services or https://store.lds.org/
* International local dial phone numbers, refer to this Global Services Department [http://store.lds.org/webapp/wcs/stores/servlet/GlobalServiceCenterView Contact List]
* by phone at '''1-800-537-5971''' (toll free in the US and Canada)
* by phone at '''+1(801)240-3500''' (in the Salt Lake City area, or outside the US and Canada)
* by email at [mailto:gscdistribution@ldschurch.org gscdistribution@ldschurch.org].

=== [[Global Service Center - IT Support|IT Support]] ===
Technical support for Church employees and [[Meetinghouse technology|meetinghouse technologies]]
* by phone at '''1-801-240-HELP''' ( +1(801)240-4357 in the Salt Lake City area, or outside the US and Canada)
* International local dial phone numbers, refer to this Global Services Department [http://store.lds.org/webapp/wcs/stores/servlet/GlobalServiceCenterView?catalogId=10551&langId=-1&storeId=10704 Contact List]
* by email at [mailto:globalservicecenter@ldschurch.org globalservicecenter@ldschurch.org]

=== [[Global Service Center - MLU Support|Member/Leader Unit (MLU) Support]] ===
Local unit clerks and leaders contact for MLS problems and questions
* by phone at '''1-800-537-5932''' (toll free in the US and Canada)
* by phone at '''+1(801)240-3500''' (in the Salt Lake City area, or outside the US and Canada)
* by email at [mailto:mlssupport@ldschurch.org mlssupport@ldschurch.org ]

=== Pacific Area ===

==== Pacific Area MLU support ====
* English: [mailto:gsc-pac-en@ldschurch.org gsc-pac-en@ldschurch.org]
* French (Français): [mailto:gsc-pac-fr@ldschurch.org gsc-pac-fr@ldschurch.org]
* Samoan (Gagana Samoa): [mailto:gsc-pac-sm@ldschurch.org gsc-pac-sm@ldschurch.org]
* Tahitian (Reo Tahiti): [mailto:gsc-pac-ty@ldschurch.org gsc-pac-ty@ldschurch.org]
* Tongan (Faka-Tonga): [mailto:gsc-pac-to@ldschurch.org gsc-pac-to@ldschurch.org]

==== Pacific Area local dial numbers for the Global Services Department ====
* American Samoa: '''+1(684)699-4473''' (Local menu), '''1-800-537-5971''' (North America menu)
* Australia: '''0011-800-8680-5650''' (toll-free)
* Fiji: '''+679-338-8027'''
* French Polynesia (Tahiti): '''+689-505-507'''
* New Caledonia: '''+1(801)353-4835''' (international toll-call)
* New Zealand: '''00-800-8680-5480''' (toll-free) or '''0800-105-311''' (toll-free)
* Samoa: '''800472''' (Blue Sky customer toll-free), '''+685-64-226''' (Digicel and non-Blue Sky customers, per minute rate applies)
* Tonga: '''0800473''' (TCC customer toll-free), '''+676 20-360''' (Digicel and non-TCC Sky customers, per minute rate applies)
* Other Countries: '''+1(801)240-3800''' or see the GSC [http://store.lds.org/webapp/wcs/stores/servlet/GlobalServiceCenterView Contact List] on https://store.lds.org/ .

=== Global Services Department numbers can also be found here: ===
https://www.lds.org/help/support/toll-free-numbers-gsc

http://store.lds.org/webapp/wcs/stores/servlet/GlobalServiceCenterView

[[Category:Global Service Center]]

Gospel Library for eBooks

2022-01-04T16:38:03Z

Sbradshaw: Redirected page to Gospel Library support

#REDIRECT [[Gospel Library support]]

{{MobileGospelLibraryIndex}}
The Gospel Library for ePub is growing. The ePub format will work on Apple's iPad, the Sony Reader, and the Barnes and Noble Nook devices.

== Downloads ==
* http://lds.org/media-library/ebooks - pdfs and e-books of the gospel library
* http://lds.org/mobileapps/ - mobile applications
* http://www.lds.org/music/library/hymns - hymn downloads
* http://feeds.lds.org/Ensign - Ensign RSS feed including pdf and audio
* http://feeds.lds.org/NewEra - New Era RSS feed including pdf and audio

=== ePub Downloads ===
'''Right click on files and save to your computer as an 'epub' file.''' (Example: HolyBible.epub or BookOfMormon.epub). Some browsers may want to rename these files as ZIP files. If your browser saves these files with a zip extension, simply change it to an epub extension. Epub files are basically zip files but they SHOULD NOT be unzipped. Devices that support the epub format include the iPad iBook application, Barnes & Noble Nook, and Sony eReader, and many others.
* http://lds.org/manual/epub

=== Amazon Kindle ===
* [http://www.amazon.com/gp/product/B00BMWE99S/ Holy Bible] - [http://media.ldscdn.org/mobi/lds-scriptures/holy-bible/holy-bible-eng.mobi mobi]
* [http://www.amazon.com/gp/product/B00BMWEEJ8/ Triple Combination] - [http://media.ldscdn.org/mobi/lds-scriptures/triple-combination/triple-combination-eng.mobi mobi]
* [http://www.amazon.com/-/e/B00B8WK1WG Other Publications]

== How to install the Gospel Library ePub books on your iPad==

Installing ePub books on your iPad device is very similar to installing MP3 files on your iPad or iPod device. Follow these instructions.

# Copy the ePub books to your local hard drive. One suggestion is to create a “books” folder in your documents folder and copy them there.
# Open iTunes
# Select the “File -> Add to Library” menu option.
# Navigate to where your books are located on your hard drive and select the books you want to add.
# The books are now added to your iTunes library. You should now have a “books” folder in your “Library” section of iTunes.
# Plug in your iPad device to your computer.
# Once your device is recognized in iTunes, click on your iPad device under the “Devices” section of iTunes.
# Next click on the “Books” in the main part of the iTunes screen. This shows you all of the books that you can synchronize or add to your iPad.
# Find the books you previously added to your iTunes library and make sure that they are “checked”.
# Synchronize your iPad and the books will be transferred to your iPad device.
# Download iBooks from the App store on your iPad. iBooks is a free app.
# The ePub books you've downloaded will be available in iBooks.

== How to install the Gospel Library ePub books on your Barnes & Noble Nook ==

To install the Gospel Library ePub books on your Nook, follow these instructions.
# Download the ePub books from this website to your hard drive. One suggestion is to create a "books" folder in your documents folder and copy them there.
# Plug your nook in to your PC. After a few seconds, you will see a "Nook" device as a hard drive on your machine. For Windows, you will need to go to the "My Computer" section to see it. For Mac, you will see the Nook device on your desktop.
# Drag the ePub books you previously downloaded to your Nook device in the "my documents" folder.
# The files will have a .zip file extension. Rename the files to have a .epub file extension.
# Eject your nook device from your PC. Follow your computer's recommended procedure for ejecting USB devices from your computer to prevent loss of data on the Nook device.
# From the Nook home screen, go to "My Library and then select "View My Documents". The books will be listed on this screen.

[[Kindle|Gospel Library]]== How to install the Gospel Library books on your Amazon Kindle ==
To install the Gospel Library mobi books on your Kindle, follow these instructions.

# Start the web browser on your Kindle and download using the mobi links above

or

# Download the mobi books from this website to your hard drive. One suggestion is to create a "books" folder in your documents folder and copy them there. The files are in a zip-compressed format. Once downloaded, you will need to extract the zip to your hard drive. Once extracted, you can delete the zip file. Once downloaded and extracted, there will be a folder for each book that you downloaded.
# Plug your Kindle in to your PC. After a few seconds you will see a "Kindle" device as a hard drive on your machine. For Windows, you will need to go to the "My Computer" section to see it. For Mac, you will see the Nook device on your desktop.
# Drag the mobi folder of the ebook that you previously downloaded to your Kindle device in the "documents" folder.
# Eject your Kindle device from your PC.
# From the Kindle home screen, you will see the new books listed on the screen.

== How to Install Using Calibre ==
Calibre is a free software tool that allows readers to manage and export e-book files to their devices. Calibre works on Windows, Mac, and Linux.

1. Download [http://calibre-ebook.com/download Calibre]

2. Open the Calibre application.

3. In the top left navigation, click on "Add Books".

4. Navigate to where the e-book file is residing. These can generally be found in the “Downloads” folder. Select your e-books, and click “Open”.

5. Once the e-book is imported to Calibre, the e-book will appear in the Calibre Library.

6. Click the “Save to disk” button in the top, center navigation. Select save location, and click “Choose” to select your device. Calibre will update the e-book to your device.

== Support ==

Some users on Windows have reported that they have a problem changing the file extension when downloading the file. This document explains how to properly change the file extension of a file.

http://www.mediacollege.com/microsoft/windows/extension-change.html

If you can't find the answer to your problem or if you've found a new bug, please email us at [mailto:gospellibrary-epub@ldschurch.org gospellibrary-epub@ldschurch.org].

[[Category:Gospel Library support]]

Gospel Library support

2022-01-04T16:34:05Z

Sbradshaw: Update support links

[https://www.churchofjesuschrist.org/learn/mobile-applications/gospel-library?lang=eng Gospel Library] is the official gospel study app of The Church of Jesus Christ of Latter-day Saints.
[[Image:Gospel_library_4_ios.png|right]]

== Current Gospel Library platforms ==
* [https://www.churchofjesuschrist.org/learn/mobile-applications/gospel-library-support?lang=eng Support for Gospel Library iOS] – iPhone, iPad, iPod touch, macOS.
* [https://www.churchofjesuschrist.org/learn/mobile-applications/gospel-library-support?lang=eng Support for Gospel Library Android] – Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire.
* [[Gospel Library for Windows 10|Support for Gospel Library Windows]] – Windows 10, Windows 11, Windows Mobile, Windows Phone.
* [https://www.lds.org/tools/feedback/?lang=eng&id=11340&note=lds.org:homepage&note=www.lds.org:%22%22 Support for Gospel Library Online] – ChurchofJesusChrist.org in a web browser.

== Older support pages ==
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]

[[Category:Gospel Library]]
[[Category:Gospel Library support]]

Sacred Music Content (Community Project)

2021-12-23T00:43:33Z

Sbradshaw: Updated page to reflect close of volunteer project

'''Sacred Music Content''' was a volunteer project active between 2011 and 2021 that allowed volunteers to help digitize and prepare content to be published in the Sacred Music app and other official Church channels.

The Sacred Music Content project began in 2011. The original purpose of the project was to make English, Spanish, French, and Portuguese hymns and children's songs available in the Sacred Music app (previously LDS Music), which was itself a volunteer project. Since that time, volunteers have digitized thousands of songs in dozens of languages. Music transcribed by volunteers has been published in Sacred Music, Gospel Library, and the Church music website, and more music will be published in the future.

After nearly a decade of volunteer contributions, as of December 2021, the project is now closed to volunteers. This was prompted in part by a need to move music content to a more central content management system, which is only accessible to Church employees.

The primary purposes of the Sacred Music Content project have been accomplished and goals have been surpassed. Church employees responsible for music projects are very grateful for the hours contributed in this small part of the Lord's Vineyard, which has benefited Church members worldwide in a tangible way.

Thank you!

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2020-04-19T19:15:45Z

Sbradshaw: Remove reference to two parts of the project that have been finished

Sacred Music Content (previously LDS Music Content) provides rich music content for Sacred Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with a Church Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.churchofjesuschrist.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need a Church Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.churchofjesuschrist.org/projects Projects] page (log in if necessary).
#(If you've never signed up for a Tech Project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''Sacred Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.churchofjesuschrist.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] or another admin with your Church Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel or another admin can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about Sacred Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from Sacred Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant languages for Church materials: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

If you are an iOS developer, you can help with [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=91 Sacred Music for OS].

There are also several Tech projects for Church apps, including Gospel Library and Sacred Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on Sacred Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Support for Gospel Library Android

2020-03-02T16:29:40Z

Sbradshaw: /* Use the LDSTech forums */

There are a few channels for getting support for the Android (Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire) version of Gospel Library. All feedback is appreciated, and if you have problems or questions about using the app, we want to help.

== Send a message to the support team ==
The primary method of receiving support for Gospel Library is by sending a message to the support team. Gospel Library is supported by a team of service missionaries who work closely with the developers. You can send them a message through the app:
# Open Gospel Library.
# Go to Settings > Send Feedback.
# Fill in the fields of the feedback form, describing the problem you're experiencing.
Sending a message through the app automatically attaches basic information about your device and app installation, which can help the support team and developers figure out what may be causing the problem if there's a bug. If you are unable to contact the Android Gospel Library support team through the app, you can email them directly at [mailto:android-support@churchservicemail.org android-support@churchservicemail.org]. The support team should get back to you within a few days.

== Talk to a member of your ward ==
If you are a new user of the app, or if you are confused about how to use a certain feature, many issues can be resolved by talking to a member of your ward who is experienced with the app. The best training is one-on-one, in person training where you can watch someone use the app and learn from them. If you are experienced with the app yourself, you can offer to help other members learn one-on-one or in a group setting.

== Use the Tech forums ==
The [http://tech.churchofjesuschrist.org/forum/viewforum.php?f=101 Tech forums] are a helpful resource. The developers don't visit the forums frequently, but there are many users of the app who are willing to help, and can answer questions or help you learn how to use the app more effectively. You will need to log in with your Church Account to post. You can also search the forums to see if your question has already been answered.

[[Category:Gospel_Library_for_Android]]
[[Category:Gospel Library support]]

Support for Gospel Library Android

2020-03-02T16:26:17Z

Sbradshaw: Update Android support email address

There are a few channels for getting support for the Android (Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire) version of Gospel Library. All feedback is appreciated, and if you have problems or questions about using the app, we want to help.

== Send a message to the support team ==
The primary method of receiving support for Gospel Library is by sending a message to the support team. Gospel Library is supported by a team of service missionaries who work closely with the developers. You can send them a message through the app:
# Open Gospel Library.
# Go to Settings > Send Feedback.
# Fill in the fields of the feedback form, describing the problem you're experiencing.
Sending a message through the app automatically attaches basic information about your device and app installation, which can help the support team and developers figure out what may be causing the problem if there's a bug. If you are unable to contact the Android Gospel Library support team through the app, you can email them directly at [mailto:android-support@churchservicemail.org android-support@churchservicemail.org]. The support team should get back to you within a few days.

== Talk to a member of your ward ==
If you are a new user of the app, or if you are confused about how to use a certain feature, many issues can be resolved by talking to a member of your ward who is experienced with the app. The best training is one-on-one, in person training where you can watch someone use the app and learn from them. If you are experienced with the app yourself, you can offer to help other members learn one-on-one or in a group setting.

== Use the LDSTech forums ==
The [http://tech.lds.org/forum/viewforum.php?f=101 LDSTech forums] are a great resource. The missionary support team and developers don't visit the forums frequently, but there are many users of the app who are willing to help, and can answer questions or help you learn how to use the app more effectively. You will need to log in with your LDS Account to post. You can also search the forums to see if your question has already been answered.

[[Category:Gospel_Library_for_Android]]
[[Category:Gospel Library support]]

Sacred Music Content (Community Project)

2019-11-18T17:54:22Z

Sbradshaw: /* Related projects */ Remove reference to project that was recently closed

Sacred Music Content (previously LDS Music Content) provides rich music content for Sacred Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with a Church Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.churchofjesuschrist.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (Sacred Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need a Church Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.churchofjesuschrist.org/projects Projects] page (log in if necessary).
#(If you've never signed up for a Tech Project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''Sacred Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.churchofjesuschrist.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] or another admin with your Church Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel or another admin can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about Sacred Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from Sacred Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant languages for Church materials: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

If you are an iOS developer, you can help with [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=91 Sacred Music for OS].

There are also several Tech projects for Church apps, including Gospel Library and Sacred Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on Sacred Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

File:Sacred-music-icon.png

2019-05-23T00:26:23Z

Sbradshaw: Icon for the Sacred Music app

Icon for the Sacred Music app

Sacred Music Content (Community Project)

2019-05-13T18:24:34Z

Sbradshaw: /* How to join the project */

Sacred Music Content (previously LDS Music Content) provides rich music content for Sacred Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with a Church Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.churchofjesuschrist.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (Sacred Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need a Church Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.churchofjesuschrist.org/projects Projects] page (log in if necessary).
#(If you've never signed up for a Tech Project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''Sacred Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.churchofjesuschrist.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] or another admin with your Church Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel or another admin can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about Sacred Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from Sacred Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant languages for Church materials: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.churchofjesuschrist.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for a few of the Church apps, including Sacred Music.

If you are an iOS developer, you can help with [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=91 Sacred Music for OS].

There are also several Tech projects for Church apps, including Gospel Library and Sacred Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on Sacred Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Gospel Library support

2019-04-12T16:42:28Z

Sbradshaw: Update Windows link

[https://www.lds.org/pages/mobileapps?lang=eng Gospel Library] is the gospel study app of The Church of Jesus Christ of Latter-day Saints. Click the links below to get instructions specific to your device.
[[Image:Gospel_library_4_ios.png|right]]

== Current Gospel Library platforms ==
* [[Support for Gospel Library iOS]] – iPhone, iPad, or iPod touch.
* [[Support for Gospel Library Android]] – Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire.
* [[Gospel Library for Windows 10|Support for Gospel Library Windows]] – Windows 10, Windows Mobile, Windows Phone.
* [https://www.lds.org/tools/feedback/?lang=eng&id=11340&note=lds.org:homepage&note=www.lds.org:%22%22 Support for Gospel Library Online] – LDS.org language pages in a web browser.

== Older support pages ==
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]

[[Category:Gospel Library]]
[[Category:Gospel Library support]]

Sacred Music Content (Community Project)

2019-03-26T13:05:30Z

Sbradshaw: Update name of Tech and Church website

Sacred Music Content (previously LDS Music Content) provides rich music content for Sacred Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.churchofjesuschrist.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (Sacred Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.churchofjesuschrist.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an Tech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''Sacred Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.churchofjesuschrist.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about Sacred Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from Sacred Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant languages for Church materials: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.churchofjesuschrist.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for a few of the Church apps, including Sacred Music.

If you are an iOS developer, you can help with [https://tech.churchofjesuschrist.org/projects?controller=projects&view=project&Projectid=91 Sacred Music for OS].

There are also several Tech projects for Church apps, including Gospel Library and Sacred Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on Sacred Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2019-03-26T13:00:21Z

Sbradshaw: Update name of app

Sacred Music Content (previously LDS Music Content) provides rich music content for Sacred Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (Sacred Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''Sacred Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about Sacred Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from Sacred Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for a few of the Church apps, including Sacred Music.

If you are an iOS developer, you can help with [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 Sacred Music for OS].

There are also several LDSTech projects for Church apps, including Gospel Library and Sacred Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on Sacred Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2019-03-26T12:51:38Z

Sbradshaw: Sbradshaw moved page LDS Music Content (Community Project) to Sacred Music Content (Community Project): Name of app changed

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about LDS Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from LDS Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are an iOS developer, you can help with [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 LDS Music for OS].

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2018-06-25T20:38:06Z

Sbradshaw: /* Related projects */

Notes on ChurchofJesusChrist.org

2018-05-29T19:22:51Z

Sbradshaw: Removed outdated content (and broken links)

#REDIRECT [[Gospel Library support]]

Notes on ChurchofJesusChrist.org

2018-05-29T19:18:33Z

Sbradshaw: Added redirect

#REDIRECT [[Gospel Library support]]

{{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]]

Gospel Library support

2018-04-09T22:08:02Z

Sbradshaw:

[https://www.lds.org/pages/mobileapps?lang=eng Gospel Library] is the gospel study app of The Church of Jesus Christ of Latter-day Saints. Click the links below to get instructions specific to your device.
[[Image:Gospel_library_4_ios.png|right]]

== Current Gospel Library platforms ==
* [[Support for Gospel Library iOS]] – iPhone, iPad, or iPod touch.
* [[Support for Gospel Library Android]] – Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire.
* [[Support for Gospel Library Windows]] – Windows 10, Windows Mobile, Windows Phone.
* [https://www.lds.org/tools/feedback/?lang=eng&id=11340&note=lds.org:homepage&note=www.lds.org:%22%22 Support for Gospel Library Online] – LDS.org language pages in a web browser.

== Older support pages ==
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]

[[Category:Gospel Library]]
[[Category:Gospel Library support]]

Gospel Library support

2018-04-09T22:03:18Z

Sbradshaw: /* Older support pages */

[https://www.lds.org/pages/mobileapps?lang=eng Gospel Library] is the gospel study app of The Church of Jesus Christ of Latter-day Saints. Click the links below to get instructions specific to your device.
[[Image:Gospel_library_4_ios.png|right]]

== Current Gospel Library platforms ==
* [[Support for Gospel Library iOS]] – iPhone, iPad, or iPod touch.
* [[Support for Gospel Library Android]] – Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire.
* [[Support for Gospel Library Windows]] – Windows 10, Windows Mobile, Windows Phone.
* [https://www.lds.org/tools/feedback/?lang=eng&id=11340&note=lds.org:homepage&note=www.lds.org:%22%22 Support for Gospel Library Online] – LDS.org language pages in a web browser.

== Older support pages ==
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]

[[Category:Mobile Gospel Library]]
[[Category:Gospel Library support]]

Gospel Library for iOS vision

2018-04-09T21:45:31Z

Sbradshaw: Redirect to Gospel Library support page

#REDIRECT [[Gospel Library support]]

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

== Usability of paper with features of digital ==
None of the benefits of paper should be lost when someone moves to digital.

For example:

* Anybody regardless of skill or education should be able to use the Gospel Library app to browse, read and study.
* Marking up, annotating, bookmarking must be as easy as grabbing a pen, not the result of navigating menus and options.
* Flipping between sections (such as D&C and OT both being used in a Sunday School class) must be as simple as "keeping a thumb" in one while looking at the other and flipping back and forth.

== Synchronized everywhere ==
* All data settings, markings, annotations, notes, bookmarks etc must follow a user wherever they go.
* A user should not ever have to think about "which device" their content is on.
* A user should never have to worry about backing up or losing data.
* A user should be able to read and mark something on an iPhone and pick up their iPad and resume at the same place reading with the same markings.
* The LDS.org website, iOS, Android, WebOS and all other devices should all be synchronized with each other via the same services - data created on one is available on all others without any thought of "syncing" - it just happens.

Examples:
* [http://itunes.apple.com/us/app/kindle/id302584613?mt=8 Kindle Apps] for iOS, Mac, PC, Kindle devices, Blackberry, etc.
* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]
* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]

== Globally distributed and accessible ==
* The app should be available in all countries that the iTunes App Store is available.
* The application and content should be localized to every language the standard works are available in.
* A user should be able to quickly switch content to any language - not just the language of their device - so that (for example) an English speaking user could flip to Spanish to teach someone with.
* Blind users should be able to use iOS VoiceOver to navigate the entire application as well as access audio versions of all content possible (scriptures, talks, videos, etc).

== Support all user contexts ==

The app should be capable of "following" a user to their different use cases in various contexts, such as:

* personal reading
* Sunday School
* Priesthood/RS
* seminary
* family reading
* lesson prep
* teaching/instructor

In a paper-based setting there may be different books, copies of books, bookmarks, etc., used in different settings. This won't generally exist in a digital world.

A person won't have different $300 devices with different LDS.org accounts for different contexts - instead the application must adapt and be flexible to them.

Why?

As a user moves from personal reading to Sunday School to Elder's Quorum to teaching with the missionaries, each setting requires being at different places in the Standard Works, wanting or not wanting markings and annotations and other such preferences.

Also, remembering where to be in each setting is left to the user rather than the device. This is unlike most "dead tree" technologies which will have bookmarks to hold reading places.

A book left on the nightstand at home versus one in the bag for church "remember" where they are and are contextual to an activity.

Thus, to be easy to end users to incorporate in their lives the application should allow "contexts" which remember the location and settings.

=== Examples ===
Personal reading:
* Resume reading at 2 Nephi 26
* dark mode on
* Annotations set to "Personal Reading 2010"

Elder's Quorum:
* Resume reading at General Conference April 2010
* dark mode off
* Annotations set to "Show All"

Teaching with missionaries:
* Resume reading at 3 Nephi 11
* Language set to Spanish
* Annotations set to "Show None"

Preparing a talk or lesson
* Search topical material
* List points to say
* Link to references
* Order talking points and references
* Display ordered set of talking points with live linked references when speaking

=== Context switching ===
Switching between contexts should be as simple as putting down one physical book and picking up another.

The state of these "contexts" must sync between devices to follow a user. Personal reading on an iPad should be able to be resumed on an iPhone.

== Native feel and best in breed design ==

=== Use native UI elements ===
The user interface design and user experience should "feel at home" on the iOS devices - using native user interface elements and following Apple Human Interface Guidelines.

For example, text selection, copy/paste, highlighting, navigation etc should use native UI widgets - custom widgets should not be re-invented. Users are most comfortable using UI elements they are accustomed to and trained with through the use of the other apps and the operating system itself.

=== Design for screen size ===

The iPad is very different from the iPhone/iPod and needs to be designed for accordingly. Taking the iPhone UI and just "blowing it up" to iPad size is not sufficient. Not only does it poorly leverage all that the iPad can offer, but it often results in poor user experience.

For example, the iPhone screen width is perfect for reading and scrolling verses of scriptures. The iPad on the other hand is very wide and may be better suited to columns of text or a thin column of text with contextual footnotes and references in the page gutter.

Another example is that on the iPhone most button nav bars make sense to be at the bottom but on an iPad the top is generally better suited to how an iPad is used and held.

=== Focus on design ===

Functionality and engineering are not enough to make a product great - design means the look and feel down to the last pixel, worrying about things like animates and page transitions, simplifying navigation and feature discovery and polishing every aspect of the user experience.

All of these things drive engineering - not the other way around.

The user experience and design of the application should be thought of first to accomplish the best possible experience for the user and then engineering and development applied to that accomplishment.

=== Apple interface design guidelines ===
* [http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html| iPhone Guidelines]
* [http://developer.apple.com/library/ios/#documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html| iPad Guidelines]

===Examples on iPad===
* [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]
* [http://itunes.apple.com/us/app/instapaper/id288545208?mt=8 Instapaper]
* [http://itunes.apple.com/us/app/reeder-for-ipad/id375661689?mt=8 Reeder for iPad]
* [http://itunes.apple.com/us/app/wikipanion-for-ipad/id364195592?mt=8 Wikipanion for iPad]
* [http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8 Articles for iPad]
* [http://itunes.apple.com/us/app/simplenote/id289429962?mt=8 Simplenote]

* [[Gospel_Library_for_iOS_UI_examples_iPad| Annotated examples of applications on iPad]]

==Other Nice Features==

===Encourage Gospel Study with Schedules===
* Interface with the ward calendars on LDS.org to make it easy to prepare for lessons
* Ability to set up study schedules like [http://www.readthescriptures.com/ ReadTheScriptures.com] and be reminded of schedules via notifications.

===Share the Gospel===
* Easily share passages, talks, scriptures and other media via email, facebook, and other build in applications.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS user interface examples on iPad

2018-04-09T21:44:24Z

Sbradshaw: Redirect to Gospel Library support page

#REDIRECT [[Gospel Library support]]

Return to [[Gospel_Library_for_iOS_design|iOS Design]] page.

==Examples of reader application UIs on iPad==

===[http://itunes.apple.com/us/app/ibooks/id364709193?mt=8| iBooks]===

* Multi-colored hi-lighting
* Standard text-selection controls
* Hi-lighting, color selection and text management built into OS-standard text popup controls
* Navigation bar at top
* Navigation hides/shows with single touch anywhere on screen
* Notes display inline in page gutter, created through same text selection popup controls
* Popover search
* Popover dictionary definitions (compare with what can be done on cross-references, footnotes, etc)
* Pagination information at the bottom is a nice touch that converts the "digital" into a "physical" feel
** Potentially very valuable to display physical page numbers in Gospel Library to correlate location between digital and physical world for settings such as Sunday School where an instructor says "now turn to page xxx" or "let's read the first paragraph of page yy"
* Overall a clean design though the "book" feel of the pages in the background is obviously unnecessary
* Synchronizes annotations (hi-lights, bookmarks, notes) and reading location automatically between devices (iPhone and iPad for example)

[[File:IBooks-1.png|400px]]
[[File:IBooks-2.png|400px]]
[[File:IBooks-3.png|400px]]
[[File:IBooks-4.png|400px]]
[[File:IBooks-5.png|400px]]
[[File:IBooks-6.png|400px]]
[[File:IBooks-7.png|400px]]
[[File:IBooks-8.png|400px]]
[[File:IBooks-9.png|400px]]

===[http://itunes.apple.com/us/app/articles-for-ipad/id364881979?mt=8| Articles for iPad]===

* Beautiful layout and design including typography
* Images are styled nicely to fit the design
* Every article has a 'globe' at the top allowing access to languages the article is in
** This could be very powerful in the Gospel Library so that on any scripture, talk, video or other document it can immediately be accessed in any language.
* Popovers are effectively used for quick navigation within an article or for changing settings
* Navigation bar at top

[[File:Articles-1.png|400px]]
[[File:Articles-2.png|400px]]
[[File:Articles-3.png|400px]]
[[File:Articles-4.png|400px]]

===[http://itunes.apple.com/us/app/inkling/id379351586?mt=8| Inkling]===

* Excellent navigation system for dealing with very large textbooks
** Uses both the top and side bar for navigation
** Sidebar works very well on an iPad with the extra screen real-estate and typical two-handed use of the device
* Sidebar shows context of the current chapter for location in the document and sections
** The sidebar could be potentially useful in the Gospel Library for similar reasons
* Popovers provide rapid access to settings and navigation
* Graphical representation of books and chapters instead of just text
** Could be very powerful in Gospel Library to use iconography instead of just text lists to provide richer visual differentiation of the many types of content
* Annotations (hi-lights and notes) are easy to use and discoverable without documentation since they use OS-standard text selection controls

[[File:Inkling-1.png|400px]]
[[File:Inkling-2.png|400px]]
[[File:Inkling-3.png|400px]]
[[File:Inkling-4.png|400px]]

===[http://itunes.apple.com/us/app/instapaper/id288545208?mt=8| Instapaper]===

* Minimal and highly functional UI
* Navigation bar at top
** Originally had bar at bottom when it migrated from iPhone but moved to top after some user experience demonstrated that on an iPad the top bar is better suited to where hands are held.
* Fast and easy to switch between Light and Dark modes for day/night use.
* The entire UI including navigation lists use the Light/Dark modes, not just the reading view
* OS-standard text selection controls are used to integrate application specific sharing features
* Synchronizes automatically
** Content between devices and web
** Reading location within articles

[[File:Instapaper-1.png|400px]]
[[File:Instapaper-2.png|400px]]
[[File:Instapaper-3.png|400px]]

===[http://itunes.apple.com/us/app/reeder-for-ipad/id375661689?mt=8| Reeder]===

* Uses sidebar navigation effectively so that holding the iPad with two-hands allow effective controls with the thumb.
* Popovers and top navigation are also used similar to the other apps.

[[File:Reeder-1.png|400px]]
[[File:Reeder-2.png|400px]]

===[http://itunes.apple.com/us/app/simplenote/id289429962?mt=8| Simplenote]===

* Top navigation bar and popovers
* Tags are effectively used for allowing articles in multiple "categories" for searching, filtering and navigating
** Could be very effective with Gospel Library for tagging hi-lights, notes etc

[[File:Simplenote-1.png|400px]]
[[File:Simplenote-2.png|400px]]

===[http://itunes.apple.com/us/app/wikipanion-for-ipad/id364195592?mt=8| Wikipanion]===

* Top navigation bar and popovers

[[File:Wikipanion-1.png|400px]]

[[Category:Gospel Library for iOS|user interface examples on iPad]]

Gospel Library for iOS QA

2018-04-09T21:42:23Z

Sbradshaw: Redirect to Gospel Library support page

#REDIRECT [[Gospel Library support]]

Return to [[Gospel_Library_for_iOS|Gospel Library for iOS]] main page.

== Test Cases by Application Section ==

* [[Gospel_Library_for_iOS_QA_reading_and_navigation|Reading & Navigation]]

* [[Gospel_Library_for_iOS_QA_annotation|Annotation (hilighting, notes, syncing)]]

* [[Gospel_Library_for_iOS_QA_cross_reference|Cross Reference]]

* [[Gospel_Library_for_iOS_QA_tagging|Tagging]]

* [[Gospel_Library_for_iOS_QA_search|Search]]

* [[Gospel_Library_for_iOS_QA_bookmarks_history_goto|Bookmarks, History and Go To]]

* [[Gospel_Library_for_iOS_QA_tabs|Tabbed/Saved Pages]]

* [[Gospel_Library_for_iOS_QA_manage_library|Manage Library (downloading/deleting content)]]

* [[Gospel_Library_for_iOS_QA_settings|Settings]]

* [[Gospel_Library_for_iOS_QA_localization|Localization]]

* [[Gospel_Library_for_iOS_QA_upgrading|Upgrading from Previous Release]]

== How to Submit Bug to JIRA ==

====1) Go to JIRA "Bug Creation" Page====

https://tech.lds.org/jira/secure/CreateIssue.jspa?pid=10021&issuetype=1

You will need to be logged in to file a bug. The username/password will typically be the same as your LDS.org username/password.

If you are not able to login [[User:Benjchristensen|contact me]] and I'll help you get setup.

====2) Descriptive Summary====

This field is the title of the issue and will show up in search lists.

Do NOT try and put the entire explanation here, give it a short 1-line summary.

[[File:Descriptive-summary.png]]

====3) Affects Version and Environment====

Please fill in the version of the application you are using.

If you are on a recent beta (such as from TestFlight) also use the "Environment" field to provide details on the exact build number.

[[File:Affects-version.png]]

====4) Fix Version====

Generally this should be left empty unless you really know what it should be or have been told what it should be.

Typically either a developer or a PM will assign bugs/tasks to specific "Fix Versions" as part of scheduling.

====5) Description====

Fill out a detailed description and step-by-step instructions on how to replicate the bug.

[[File:Description.png]]

====6) Finish and Save====

If you have screenshots or crash logs you would like to attach, go ahead and do so.

Click the "Create" button to save the bug.

== Sample Test Case ==

Following is an example test case and template for use on the rest of our test cases.

===Making a Selection===

====Purpose of Test====

To validate that any reading view allows selection of text, that it defaults the selection to the current verse/paragraph and that it can be modified through dragging the beginning or ending markers.

====Pre-Requisites and/or Assumptions====
- Need to be logged in? Doesn't matter.
- Internet Connection Required? Doesn't matter.
- Must be online or offline? Doesn't matter.
- Anything to perform prior to this test case?
- Navigate to any book with a reading view.

====Environment====
- iOS 3.x and later
- iPhone 2nd generation and later
- iPad
- iPod touch 2nd generation and later

====Test Data====
- There is no specific test data needed to perform this test.

====Steps to Test====
- Navigate to book of scripture and open a chapter.
- Press and hold on a verse. It should select the entire verse and display beginning/ending markers at the beginning and end of the verse.
- Drag the beginning marker up and down to change the selection.
- Drag the ending marker up and down to change the selection.
- You should be able to be word specific about what is being selected.
- Click somewhere outside of the selection, it should de-select.
- When a selection is made, it should show a black popup with options saying "Copy | Hilight | Note"
- If you drag a marker to the top or bottom of the screen, the page should scroll and keep selecting text in that direction as it scrolls.

[[Category:Gospel Library for iOS]]

Gospel Library for iOS Accessibility

2018-04-09T21:39:38Z

Sbradshaw: Redirect to Gospel Library support

#REDIRECT [[Gospel Library support]]

This article contains a collection of tips and tricks for users who use Voiceover with the [[Gospel Library for iOS]] application. The information given here will change over time as the application evolves and improves.

[[Category:Gospel Library for iOS]]

Category:Mobile Gospel Library

2018-04-09T21:32:33Z

Sbradshaw: Sbradshaw moved page Category:Mobile Gospel Library to Category:Gospel Library: Use more modern terminology

#REDIRECT [[:Category:Gospel Library]]

Gospel Library support

2018-04-09T21:03:56Z

Sbradshaw: Add LDS.org feedback link

[https://www.lds.org/pages/mobileapps?lang=eng Gospel Library] is the gospel study app of The Church of Jesus Christ of Latter-day Saints. Click the links below to get instructions specific to your device.
[[Image:Gospel_library_4_ios.png|right]]

== Current Gospel Library platforms ==
* [[Support for Gospel Library iOS]] – iPhone, iPad, or iPod touch.
* [[Support for Gospel Library Android]] – Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire.
* [[Support for Gospel Library Windows]] – Windows 10, Windows Mobile, Windows Phone.
* [https://www.lds.org/tools/feedback/?lang=eng&id=11340&note=lds.org:homepage&note=www.lds.org:%22%22 Support for Gospel Library Online] – LDS.org language pages in a web browser.

== Older support pages ==
* [[Gospel Library support - Android|Android]]
* [[Gospel Library support - iPhone|iPhone]]
* [[Gospel Library support - iPad|iPad]]
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]
* [[Gospel Library support - Kindle|Kindle]]

[[Category:Mobile Gospel Library]]
[[Category:Gospel Library support]]

Support for Gospel Library Android

2018-04-09T20:58:33Z

Sbradshaw: Support info for Android Gospel Library

There are a few channels for getting support for the Android (Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire) version of Gospel Library. All feedback is appreciated, and if you have problems or questions about using the app, we want to help.

== Send a message to the support team ==
The primary method of receiving support for Gospel Library is by sending a message to the support team. Gospel Library is supported by a team of service missionaries who work closely with the developers. You can send them a message through the app:
# Open Gospel Library.
# Go to Settings > Send Feedback.
# Fill in the fields of the feedback form, describing the problem you're experiencing.
Sending a message through the app automatically attaches basic information about your device and app installation, which can help the support team and developers figure out what may be causing the problem if there's a bug. If you are unable to contact the Android Gospel Library support team through the app, you can email them directly at [mailto:android-support@ldsmail.net android-support@ldsmail.net]. The support team should get back to you within a few days.

== Talk to a member of your ward ==
If you are a new user of the app, or if you are confused about how to use a certain feature, many issues can be resolved by talking to a member of your ward who is experienced with the app. The best training is one-on-one, in person training where you can watch someone use the app and learn from them. If you are experienced with the app yourself, you can offer to help other members learn one-on-one or in a group setting.

== Use the LDSTech forums ==
The [http://tech.lds.org/forum/viewforum.php?f=101 LDSTech forums] are a great resource. The missionary support team and developers don't visit the forums frequently, but there are many users of the app who are willing to help, and can answer questions or help you learn how to use the app more effectively. You will need to log in with your LDS Account to post. You can also search the forums to see if your question has already been answered.

[[Category:Gospel_Library_for_Android]]
[[Category:Gospel Library support]]

Gospel Library support

2018-04-09T20:27:07Z

Sbradshaw: Working on adding up-to-date support information

[https://www.lds.org/pages/mobileapps?lang=eng Gospel Library] is the gospel study app of The Church of Jesus Christ of Latter-day Saints. Click the links below to get instructions specific to your device.
[[Image:Gospel_library_4_ios.png|right]]

== Current Gospel Library platforms ==
* [[Support for Gospel Library iOS]] – iPhone, iPad, or iPod touch.
* [[Support for Gospel Library Android]] – Google, Samsung, Huawei, LG, Motorola, etc., OR Amazon Kindle Fire.
* [[Support for Gospel Library Windows]] – Windows 10, Windows Mobile, Windows Phone.
* [[Support for Gospel Library Online]] – LDS.org language pages in a web browser.

== Older support pages ==
* [[Gospel Library support - Android|Android]]
* [[Gospel Library support - iPhone|iPhone]]
* [[Gospel Library support - iPad|iPad]]
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]
* [[Gospel Library support - Kindle|Kindle]]

[[Category:Mobile Gospel Library]]
[[Category:Gospel Library support]]

File:Gospel library 4 ios.png

2018-04-09T20:02:12Z

Sbradshaw: Icon for Gospel Library 4. Church owned.

Icon for Gospel Library 4. Church owned.

Gospel Library support

2018-04-09T19:56:57Z

Sbradshaw: Remove outdated links

[https://www.lds.org/pages/mobileapps?lang=eng Gospel Library] is available on various mobile platforms and ebook readers. You can get information and support on the Gospel Library by clicking on one of the platform links below.

== Gospel Library platforms ==
* [[Gospel Library support - Android|Android]]
* [[Gospel Library support - BlackBerry|BlackBerry]]
* [[Gospel Library support - iPhone|iPhone]]
* [[Gospel Library support - iPad|iPad]]
* [[Gospel Library support - webOS|webOS (Palm Pre)]]
* [[Gospel Library support - WinMobile|Windows Mobile]]
* [[Gospel Library for ePub|ePub (iPad iBook, B&N Nook, Sony eReader, etc.)]]
* [[Gospel Library support - Kindle|Kindle]]

For volunteers who are helping to support the various mobile products, you can view the [[Gospel Library volunteer support information]].

[[Category:Mobile Gospel Library]]
[[Category:Gospel Library support]]

File:Standard Callings.pdf

2017-04-25T00:09:50Z

Sbradshaw: Sbradshaw uploaded a new version of File:LCR Standard Callings.pdf

Standard Callings in CDOL, LCR, and MLS.

Sacred Music Content (Community Project)

2017-01-13T03:50:38Z

Sbradshaw: /* Leaving the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about LDS Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page]. This will unsubscribe you from LDS Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2017-01-13T03:50:03Z

Sbradshaw: /* How to join the project */ Added instructions for leaving the project

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Leaving the project ==

If you are no longer able to contribute and don't want to receive emails about LDS Music Content, you can click the "Leave Project" button at the bottom of the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page]. This will remove you from LDS Music Content team emails and remove your access to the Music Content Management System.

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

File:Standard Callings.pdf

2016-07-26T00:09:47Z

Sbradshaw: Sbradshaw uploaded a new version of File:LCR Standard Callings.pdf

Standard Callings in CDOL, LCR, and MLS.

File:Standard Callings.pdf

2016-07-26T00:08:54Z

Sbradshaw: Sbradshaw uploaded a new version of File:LCR Standard Callings.pdf

Standard Callings in CDOL, LCR, and MLS.

File:Standard Callings.pdf

2016-07-26T00:07:59Z

Sbradshaw:

Standard Callings in CDOL, LCR, and MLS.

File:Standard Callings.pdf

2016-07-26T00:07:40Z

Sbradshaw:

Standard Callings in CDOL, LCR, and MLS, as of September 14, 2015.

File:Standard Callings.pdf

2016-07-26T00:07:13Z

Sbradshaw: Sbradshaw uploaded a new version of File:LCR Standard Callings.pdf

Standard Callings in CDOL, LCR, and MLS.

File:Standard Callings.pdf

2016-07-26T00:06:30Z

Sbradshaw: Standard Callings in CDOL, LCR, and MLS.

Standard Callings in CDOL, LCR, and MLS.

Sacred Music Content (Community Project)

2016-04-19T19:35:52Z

Sbradshaw: /* Priority of languages */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as ''Additional Songs for Children'' or music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2016-04-19T19:34:07Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the grey navigation bar below the main navigation). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-09-30T19:01:05Z

Sbradshaw: /* Further reading */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)
* [[Adding languages to MCMS users]] (instructions for admins)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-08-31T23:47:41Z

Sbradshaw: /* Related projects */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

Volunteers at Brigham Young University (BYU) in Provo may be interested in [https://www.facebook.com/vineyardbyu Vineyard at BYU], a group that meets on campus each week to work together on LDS Music Content and related projects.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-06-18T22:40:43Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After joining the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access to your language. Samuel can help you get started and answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-06-18T22:32:13Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After you have joined the project, [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] or another project manager will need to give you editing access to your language. He'll need your LDS Account username and the name of the language you would like to help with. Samuel is also available by email to help you get started and to answer questions about using the MCMS.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-06-18T22:30:41Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After you have joined the project, [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] or another project manager will need to give you editing access to your language. Send him an email with your LDS Account username and the name of the language you would like to help with – also, he can help answer your questions about how to use the MCMS web site.

By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-06-18T22:29:00Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After you have joined the project, [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] or another project manager will need to give you editing access to your language. He will need your LDS Account username and the name of the language you would like to help with. By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-06-18T22:27:09Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After you have joined the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] so he can give you editing access to your language and help you get started. Include your LDS Account username and the name of the language you would like to help with. By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]

Sacred Music Content (Community Project)

2015-06-18T22:25:47Z

Sbradshaw: /* How to join the project */

LDS Music Content provides rich music content for LDS Music, Gospel Library, and the Church music web site. We are looking for volunteers who can read and type in other languages. Anyone with an LDS Account can join and help with the following tasks:

# '''Transcribing content.''' All of the music that is available from the Church in print needs to be typed so it can be made available digitally as well. This is done on the [https://tech.lds.org/mobile/mcms/ Music Content Management System (MCMS)].
# '''QA of transcribed content.''' Every song that is transcribed needs to be quality-checked, to make sure all of the credits, verses, etc. are filled in correctly. Detailed instructions for transcribing and QAing are here: [[Transcribing LDS music content]].
# '''Frontmatter and backmatter.''' The frontmatter and backmatter for each hymnbook need to be prepared by a language speaker who is familiar with HTML code. Detailed instructions are here: [[HTML hymnbook chapters]].
# '''Typing scripture book names.''' Scripture book names in each language need to be collected. This is done on the "Scriptures" tab of the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 Languages (LDS Music)] Google spreadsheet. Detailed instructions are here: [[Scripture book names]].

In order to log in to the Music Content Management System or edit the Languages spreadsheet, you will need to join the project.

== How to join the project ==

You will need an LDS Account, which is the same account used to sign in to other Church web sites.
#Go to the [https://tech.lds.org/projects Projects] page (log in if necessary).
#(If you've never signed up for an LDSTech project before:)
##Follow the link to the ''Individual Contributor License Agreement'' (ICLA). Read and agree.
##Click on ''Profile'' (on the second red bar at the top of the page). Fill out all required fields on your profile (the ones marked with an asterisk*) and press ''Save.''
#On the Projects page, find the project called ''LDS Music Content'' (the list is in alphabetical order). Click on the title.
#Near the top of the page there’s a little black button that says ''Join'' – click it!

After you have joined the project, send an email to [https://tech.lds.org/projects?view=profile&layout=profilepub&username=sbradshaw Samuel Bradshaw] with your LDS Account username and the name of the language you would like to help with, so he can give you editing access. By joining, you will automatically receive read-only access to the MCMS and be added to the mailing list (hosted by Google Groups). Subscription settings can be changed on the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=164 project page].

== Priority of languages ==

Our highest-priority languages for transcription and QA are:
# The “Internet Ten”: English, Spanish, Portuguese, French, German, Italian, Russian, Chinese, Japanese, and Korean.
# Other significant LDS languages: Albanian, Armenian, Bulgarian, Cebuano, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Hungarian, Indonesian, Latvian, Lithuanian, Mongolian, Norwegian, Polish, Romanian, Samoan, Swedish, Tagalog, Thai, Tongan, Ukrainian, and Vietnamese.
# Any other languages with published Church music.

Within each language, the highest-priority collections are first, the hymnbook, next the ''Children’s Songbook,'' if they exist; then any ''Hymns and Children’s Songs'' booklets currently in use, and finally, other collections such as music from Church magazines.

Some languages and collections have already been completed – you can go to the [https://docs.google.com/spreadsheet/ccc?key=0AuWQ-iCrlReTdE9YeVJhdFk0NW4zZlpRZTYtQzN3a2c#gid=4 “Language Progress” tab] of the Languages spreadsheet to check what the current status of each language and collection is.

== Related projects ==

Language speakers may be interested in the [https://tech.lds.org/wiki/Mobile_Translation_(Community_Project) Mobile Translation] project, which provides UI and app store translation for many of the Church apps, including LDS Music and Gospel Library.

If you are a programmer, there are LDS Music app projects for [https://tech.lds.org/projects?controller=projects&view=project&Projectid=91 iOS], [https://tech.lds.org/projects?controller=projects&view=project&Projectid=116 Android], or [https://tech.lds.org/projects?controller=projects&view=project&Projectid=156 Windows 8]. If you do web development, you can help improve the Music Content Management System by joining the [https://tech.lds.org/projects?controller=projects&view=project&Projectid=165 Music CMS] project.

There are also several LDSTech projects for Church apps, including Gospel Library and LDS Music, that allow you to beta test pre-release versions of the apps and send feedback. The complete project list is available by clicking ''Projects'' above.

== Further reading ==
[[Image:LDS_Music_Devices.png|right|300px]]

* [[Transcribing LDS music content]] (instructions for volunteers)
* [[Working on songs in the MCMS]] (instructions for volunteers)
* [[HTML hymnbook chapters]] (instructions for volunteers)
* [[Scripture book names]] (instructions for volunteers)
* [[ISO Language Codes]] (technical reference)
* [[Referring to collections and songs]] (technical reference)
* [[LDS Music external resources]] (technical reference)
* [[LDS Music Content API]] (technical reference)

[[Category:LDS Music]]
[[Category:LDS Music Content]]