TechWiki - User contributions [en]

Membership record number

2013-04-16T14:12:24Z

Eblood66: Undo revision 41353 by Gomeztires (talk)

The '''membership record number''' (MRN) is a unique identifier used primarily to link members of the Church to their individual membership and ordinance records stored centrally at Church headquarters in Salt Lake City, Utah and locally at the various ward, stake or branch offices where the member resides or has last been known to reside.

A membership record number may also be assigned to a [[child of record]] (a child born to members of the Church and who has received a blessing, but who has yet to baptized).

In cases where an identifier such as the MRN is assigned to non-members, the number may be referred to as an administrative number. In such cases the identifier appears on a member´s record, but does not itself refer to a separate membership record for the individual to whom it has been assigned.

== MRN format ==

Membership record numbers currently have the following format: 012-3456-7890. The last digit is a modulus 11 check digit, where the value 10 is represented by the capital letter A.

=== Check digit ===
The last digit of the MRN is a modulus 11 check digit. In the following formula, the notation x<sub>n</sub> means the nth digit, counting from the right (the ones digit). The check digit x<sub>1</sub> is chosen so that the result of the formula in modulus 11 is always 0.<ref>The formula was derived empirically. The formula for the low-order 8 digits is certainly correct, and matches the system used for [http://en.wikipedia.org/wiki/International_Standard_Book_Number#ISBN-10 ISBN-10] check digits. The formula for the high-order 3 digits has been tested against a large data set</ref>

x<sub>1</sub> + 2*x<sub>2</sub> + 3*x<sub>3</sub> + 4*x<sub>4</sub> + 5*x<sub>5</sub> + 6*x<sub>6</sub> + 7*x<sub>7</sub> + 8*x<sub>8</sub>

If any of the first three digits is nonzero, then you also add to the above the sum:

5*(x<sub>8</sub>+x<sub>9</sub>) + 6*x<sub>10</sub> + 7*x<sub>11</sub>

So for the MRN 314-1592-653x the x must be chosen such that

x + 2*3 + 3*5 + 4*6 + 5*2 + 6*9 + 7*5 + 8*1 + 5*(1+4) + 6*1 + 7*3 = x + 204 is equal to 0 in mod 11.

Thus x = 5 (because 5+204=209, and 209 mod 11 is 0) and so 314-1592-6535 is a valid MRN.

== History ==
Since the founding of the Church in 1830 most membership records were maintained in a decentralized manner with local wards in charge of registration and storage. However, in order to improve the quality of records kept and in accordance with received revelation, records were kept both centrally and locally in order to ensure safe-keeping and accuracy of performed ordinances. Further standardization and improvements occurred when the membership record number was adopted on a Church-wide basis in the 1990s.

Since then the MRN has become the primary reference number for individuals and their records in the Church. Since the 2000´s, the MRN has been used as an authentication instrument for various Church e-services and websites.

The original standard MRN was 8 digits (7 digits plus a check digit). When it became clear that Church membership would exceed 10 million, the MRN format was extended to 11 digits (10 digits plus a check digit). All existing 8-digit numbers were given three leading zeroes. The new system will accommodate up to 10 billion unique MRNs.

== See also ==
* [[Membership record]]
* [[Temporary membership record]]

== References ==
<references />

[[Category:Membership]]

Talk:Roles and responsibilities (Directory)

2011-11-14T17:45:56Z

Eblood66: Respond and question about Stake Website Administrators

==More than one kind of administrator==

[https://tech.lds.org/forum/member.php?8813-jdcr256 jdcr256] has verified on the [https://tech.lds.org/forum/showthread.php?8993-ward-website-administrator-rights&p=68834&viewfull=1#post68834 Directory forum] that the ward website administrator does not have the same rights as other directory administrators (specifically they can only administer photos, not profile information). This should be clarified in this documentation. Johnsonth, are you open to community edits on these pages? -- [[User:Eblood66|Eric Blood]] 16:06, 12 November 2011 (UTC)

: This content wouldn't have been moved to the wiki if it weren't open for reasonable edits. So go ahead and edit it if you'd like. In any case, thanks for bringing this up. -- [[User:Aebrown|Aebrown]] 06:33, 13 November 2011 (UTC)

:: That's kind of what I thought but I wasn't sure if there might be some other reason they were moved (temporarily perhaps). In any case, I've added clarification on that issue. However, I think it may still be misleading in another area. Alan, do you know if the Stake callings actually provide the ability to manage photos or edit information? Or do those roles just allow you to see members who have opt-ed out (and maybe youth in other wards)? -- [[User:Eblood66|Eric Blood]] 04:41, 14 November 2011 (UTC)

::: Stake callings in the stake presidency or stake clerk (including assistants) do confer permission to edit profiles. People with such callings also have the ability to see members who have opted out, and also children in other other wards. But they do not have the ability to do anything with photos in any ward.

:::: If website administrators don't have rights to edit profiles then do Stake Website Administrators get any special rights on the Directory at all? Can they view opt-out members or children in other wards? Do you know? -- [[User:Eblood66|Eric Blood]] 17:00, 14 November 2011 (UTC)

::: Because of this, I don't think your recent change to the article to document a new role of "photo-only administrator" helps clarify the issue properly. I would prefer to have three roles: member, administrator, and profile editor (we could talk about the exact wording for this last role title). For the administrator role we would discuss the photo-related functions, and for the profile editor role we would discuss the profile-related functions. We would then note that some callings grant one of those roles and other callings grant both roles. -- [[User:Aebrown|Aebrown]] 12:55, 14 November 2011 (UTC)

:::: I agree. With yet another combination of rights for stake callings, what I added doesn't cover the real situation. And I agree that several roles (with multiple rights per calling in some cases) would be better (probably laid out in an 'access table' format). ''Profile editor'' sounds OK to me too. I'm not too sure about using ''administrator'' for just the photo-related features though. Maybe ''photo manager'' instead? But it sounds like there is another right as well: the right to see children in other wards. Ward level callings do not have special rights in this area. Like all members they can only see the children in their own ward but not in other wards. -- [[User:Eblood66|Eric Blood]] 17:00, 14 November 2011 (UTC)

:::::Thanks for noting the problems on this page. I wasn't aware of all the administrator role nuances, so I had to get some clarification. I updated the page to more accurately reflect the different types of administrators. Does my update make sense? I am hesitant to create a term such as "photo administrator" or "profile only administrator" if those terms aren't reflected in the directory interface anywhere. By the way, I'm glad to see you make direct changes to the page. The philosophy of the wiki is that through successive edits from many people, we get more accurate information. Feel free to make any additional edits that you see needed. By the way, would be interested in assessing all directory help information? It would really benefit from a rigorous review.--[[User:Johnsonth|Tom Johnson]] 17:14, 14 November 2011 (UTC)

:::::: The update does make more sense (although Alan beat me to correcting the rights for the website administrator). I wanted your input before using new terms anyway and this looks good. I still have one concern though. Can you verify that the Stake Website Administrator calling does provide profile edit rights (unlike the ward and district callings)? -- [[User:Eblood66|Eric Blood]] 17:45, 14 November 2011 (UTC)

Talk:Roles and responsibilities (Directory)

2011-11-14T17:00:17Z

Eblood66: /* More than one kind of administrator */ - Respond

Talk:Roles and responsibilities (Directory)

2011-11-14T04:41:49Z

Eblood66:

Talk:Roles and responsibilities (Directory)

2011-11-12T16:06:40Z

Eblood66: Created page with '==More than one kind of administrator== [https://tech.lds.org/forum/member.php?8813-jdcr256 jdcr256] has verified on the [https://tech.lds.org/forum/showthread.php?8993-ward-web…'

Leader and Clerk Resources

2011-01-17T19:33:21Z

Eblood66: Clarified access for assistant executive secretaries and that standard positions are needed

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

== Callings with Leader Portal access ==

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

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

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

== Accessing the Leader Portal ==

To access the Leader Portal:

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

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

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

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

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

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

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

If members have selected to keep their contact information private, leaders will see a visual indicator letting them know the members prefer not to be contacted. For countries outside the European Union, member contact information is shown by default until a member chooses to make it private. For countries inside the European Union, it's the opposite: member contact information is private by default until a member chooses to show it. (This data privacy policy conforms to European Union data privacy directives.)

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

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

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

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

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

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

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

Each application from this Resources menu is described briefly below.

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

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

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

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

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

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

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

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

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

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

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

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

[[File:Callings.png|frame|none|The Organizations menu allows you to see information about callings in your ward or stake.]]
You can select four options to view callings:

* By Organization
* Members with Callings
* Members without Callings
* Out of Unit Callings

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

The following reports are currently available:

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

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

[[Category:Websites]]

Talk:Leader Resources and Clerk Resources

2010-12-05T05:12:08Z

Eblood66: Created page with '== Ward Assistant Executive Secretaries == Unless something has changed very recently there isn't a standard position for a ward assistant executive secretary (although I think …'

== Ward Assistant Executive Secretaries ==

Unless something has changed very recently there isn't a standard position for a ward assistant executive secretary (although I think many wards have them--mine does). As such ward assistant executive secretaries do not have access to the leader portal but the wording on this page implies that they do which may be confusing. I think it should probably be reworded to clarify. In fact it would probably be better to list the exact standardized callings that have access (probably in a bullet list). I'd be willing to take a shot at it but since this page was written by a church employee I thought I'd get feedback first and see if the author would prefer to make the changes. -- [[User:Eblood66|Eric Blood]] 05:12, 5 December 2010 (UTC)

Tech Project FAQs

2009-07-28T20:52:42Z

Eblood66: /* FAQs */

An exciting new direction that the Church is taking is to involve the community in the design and development of various projects. Some of these projects include:

* [[Local_Unit_Website_Project | Local Unit Website Project]].
* [[Home Teaching / Visiting Teaching Application | Home and Visiting Teaching Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications Project]]
* [[IPhone Scriptures Application | iPhone Scriptures Project]]
* [[:Category:Projects|more...]]

We encourage anyone to get involved. Read the FAQs below to learn how you can get involved in helping the Church build great applications.

===FAQs===
Here are answers to some of the most frequently asked questions.

; How do I get involved?
# You need to follow all of the steps found on the [[Requirements for Participation]] page.
# Find a project that is interesting to you. It does not matter if you are a programmer, QA engineer, security expert, technical writer, or UI designer, we need all skill sets and talents.
# Visit the project page on the wiki for the project you are interested in. Most are listed above.
# Each project will have specific needs and many have a step by step process for checking out code, building, with links to our Bug Tracking system so that you can see what needs to be done and volunteer.

; Where can I find out the most urgent projects to help with?
: Check out our [[Current Needs]] wiki page.

; How do I check out code?
: We use subversion as our code management system. Each project has it's own subversion repository. Before you can check out any code, however, you must have an LDSAccount username (see [[Requirements for Participation]] for information about how to get an LDSAccount username). Visit the project page for details on where to find the subversion repository for the project.

; How do I check in code?
: This depends upon the project. Some projects you can request to have commit rights to subversion. Other projects require that you submit code patches to be reviewed before they are applied. See the project wiki page for specifics. If you have any questions, please contact [[User:welchtc | Tom Welch]].

; Is there a testing environment for the various projects?
: Most projects have a test environment that you can utilize. For example, you can see the latest build of the Local Unit Calendar application by visiting http://tech.lds.org/luc. Most projects will automatically look for subversion commits and generate builds to the test environment. See the individual project pages for more information about their test environments.

; Are there any coding or other community standards that must be followed?
: Each project may have their own standards but overall, you can read the currently defined [[Community Development Best Practices | best practices]].

; I'm not a programmer. How can I contribute?
: We always have need for UI designers, QA engineers and testers, technical writers, translators, security experts, project managers, etc. Contact [[User:welchtc | Tom Welch]] with your skills and we will put you on a team best fitting to your skills.

; What do I do if I have a great idea for a new application?
: We love to hear your ideas or even see projects you have created. Please send an email to [[User:welchtc | Tom Welch]] with your idea or project.

; Who do I contact for more information?
: You can contact [[User:welchtc | Tom Welch]] with any questions that you have.

TechWiki talk:Guidelines

2009-06-17T20:56:37Z

Eblood66: /* How to help people with guidelines */

== Template:Need Input==
I just edited this explanation to eliminate the word "parameter" as it seems a little too much like jargon; however, now I'm thinking that the intent here is for programmers (developers? I'm not sure what the right term is) to be reading these guidelines, then perhaps "parameter" is a clear, meaningful word for them. If it is jargon, then the rest of the template section should be written to get rid of it too. [[User:Aprilbosworth|Aprilbosworth]] 03:02, 16 October 2008 (UTC)

:I agree the word "parameter" is pretty technical. I'm not quite sure how else to describe it, since I've dealt with this jargon for quite a few years. I guess it's time to pull out the Thesaraus.

:P.S. Don't forget to sign your name using 4 tildes '~'; I have added your signature to your last post. Thanks. -- [[User:Mkmurray|Mike Murray]] 15:52, 16 October 2008 (UTC)

:Although many participants on the wiki will be developers, we need the involvement of others as well. So reducing jargon is a good idea (except for certain pages involving technical design such as [[Home Teaching / Visiting Teaching Detailed Design]]). I think your rewrite is good and could be extended to the other templates. I don't think we need a term to replace parameter as long as there is an example. --[[User:Eblood66|Eric Blood]] 18:18, 16 October 2008 (UTC)

== Guidelines vs. Manual of Style ==
I propose that this article (or portions of it) should be merged with the [[LDS_Tech:Manual of Style|Manual of Style]] or at least be moved to the LDS_Tech namespace. --[[User:Cottrells|Steve]] 20:28, 16 April 2009 (UTC)

: I certainly agree that the Guidelines should be in the LDS Tech namespace. But I don't like the idea of merging the content with the Manual of Style. As I see it, there is a pretty clear distinction between the articles. The MoS covers specific wording choices, and the Guidelines covers procedures and wiki elements. Articles should cover a specific topic and not be too long. The current organization meets these goals, and merging would violate both principles, in my opinion. -- [[User:Aebrown|Aebrown]] 03:05, 17 April 2009 (UTC)

::I think I was being a little hasty. After further review, I can see the benefit of having these two separate articles. On reflection I think this article would be better placed in the ''Help'' namespace. --[[User:Cottrells|Steve]] 12:26, 17 April 2009 (UTC)

== How to help people with guidelines ==

{{unresolved}}
There are many contributors who are clearly new to wikis, or at least are not familiar with the standard practices. We've tried to collect some helpful guidelines in this article, but clearly some people have never seen these guidelines, or forget what they are, or disagree with them and ignore them. I tend to think most people who don't follow the guidelines are in the first group.

The errors I see most commonly are:
* There are a few users who are extremely quick to click the Save Page button when they are editing. They might make 15 changes in the space of 10 minutes that really clutter up the change log, and some are obvious errors that show that they never used preview to see if it was a good change before saving.
* Mislabeling of changes as a "minor edit." This is to be used only for completely non-controversial changes such as punctuation, formatting, etc. If you are actually adding content, it is not a minor change, even if you are only adding one sentence. I see many "minor edits" that introduce many lines of new content.
* Using title case, contrary to the new capitalization guidelines for titles and section headings.

Given that we value the contributions of all contributors, and we work under the assumption that they want to "do it right" but are just not aware, my questions are:
# How do we help people know about the guidelines? They are mentioned on the Main Page, and on the Help page, but it's easy to miss those places. Is there some other way to make these guidelines visible? If we had a "Wiki Tip of the Week", is there a way we could make that sufficiently prominent to get people's attention?
# When a particular individual is repeatedly doing things outside the guidelines, how can we help the individual? I have tried to e-mail some of these people, but none of them can be e-mailed through the wiki, either because they did not specify an e-mail address in their profile, or they have requested no e-mail. I really doubt that they monitor their User Talk pages, so that's probably not effective, either. Am I missing some way to communicate with them?

I'd appreciate any feedback on this topic. -- [[User:Aebrown|Aebrown]] 15:06, 17 June 2009 (UTC)

:I have been frustrated with the inability to email members in the past as well. Though this is a side issue to the problem at hand, I think it would help enormously to be able to contact every wiki member offline from the wiki via email. Might I suggest we make email addresses and receiving emails mandatory? Is this possible with the software? -- [[User:Mkmurray|Mike Murray]] 15:16, 17 June 2009 (UTC)

:: It's certainly possible, but enforcing those e-mail requirements would require customizations that only Tom (as far as I know) could do. Only Tom could tell if people have not supplied e-mail addresses, but have simply chosen not to receive e-mail. Any changes we would make to these settings would not affect current users, but if they supplied e-mail addresses, then at least Tom could e-mail them and request that they start accepting e-mails. -- [[User:Aebrown|Aebrown]] 18:33, 17 June 2009 (UTC)

:::I think a polite notice on a users talk page, directing them to this article could help. When the user next logs into the site a notice that a message has been left, will be displayed at the top of each page they view. --[[User:Cottrells|Steve]] 19:35, 17 June 2009 (UTC)

:I wonder if it might be possible to change the default skin to provide a short note next to the minor edit checkbox and near the Save Page and Show Preview buttons advising about their use and a pointer to the guidelines page. Of course, that's something only Tom could do as well. -- [[User:Eblood66|Eric Blood]] 20:56, 17 June 2009 (UTC)

Main Page

2009-04-16T02:47:00Z

Eblood66: New colors weren't working in Firefox due to a whitespace issue in the styles

<div style="margin: 10px 0px 0px 0px;">
<div style="background-color: #ddcef2; text-align: center;">
==Welcome to the LDSTech Wiki==
</div>
The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="background-color: #f5faff; margin: 0px 5px 0px 0px; border: 1px solid #a3b0bf;">
<div style="background-color: #cedff2; text-align: center;">
=== Projects ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #cedff2; padding-left: 10px; ">
=====Announcements=====
</div>
* [[General_Announcements#Moving_to_HTTPS_for_key_tools | Change in our URLs]]
* [[General_Announcements#First_Java_Stack_Documentation | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #cedff2; padding-left: 10px; ">

=====Participation & Current Needs=====
</div>
* [[LDS_Tech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs | Current Needs ]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #cedff2; padding-left: 10px; ">

===== Current Projects =====
</div>
* [[Home Teaching / Visiting Teaching Application | Home Teaching / Visiting Teaching Application]]
* [[Church Historical Timeline Application | Church Historical Timeline Application]]
* [[IPhone Scriptures Application | iPhone Scriptures Application]]
</td>
<td><div style="background-color: #cedff2; padding-left: 10px; ">

===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #cedff2; padding-left: 10px; ">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Family Safety | More]]
</td>
</tr>

</table>
</div> 
</td>
<td>
<div style="background-color: #f5fffa; margin: 0px 0px 0px 10px; border: 1px solid #a3bfb1;">
<div style="background-color: #cef2e0; text-align: center;">

=== Clerks ===
</div>
<table width="100%" cellspacing="10" cellpadding="0" border="0">
<tr valign="top">
<td width="50%"><div style="background-color: #cef2e0; padding-left: 10px; ">
=====General=====
</div>
* [[Clerks Overview|Overview]]
* [[Stake Clerk]] / [[Ward Clerk]]
* [[MLS]]
* [[Glossary]]
* '''[[Tip of the Week]]!'''
</td>
<td><div style="background-color: #cef2e0; padding-left: 10px; ">
=====Financial=====
</div>
* [[Financial Clerk]]
* [[Financial Audit]]
* [[Reconciliation]]
* [[:Category:Finance|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #cef2e0; padding-left: 10px; ">
===== Membership =====
</div>
* [[Membership Clerk]]
* [[Membership Records]]
* [[Recording Ordinances]]
* [[Membership Audit]]
* [[:Category:Membership|more...]]
</td>
<td><div style="background-color: #cef2e0; padding-left: 10px; ">
===== Statistical =====
</div>
* [[Statistical Clerk]]
* [[Statistical Reporting]]
* [[Quarterly Report]]
* [[Annual History]]
* [[:Category:Statistical|more...]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #cef2e0; padding-left: 10px; ">
===== Technology =====
</div>
* [[Stake Technology Specialist]]
* [[Meetinghouse Internet]]
* [[Meetinghouse Webcast]]
* [[Satellite Broadcasts]]
* [[Local Unit Website]]
* [[:Category:Technology|more...]]
</td>
<td><div style="background-color: #cef2e0; padding-left: 10px; ">
=====Unit Administration=====
</div>
* [[:Category:Roles|Roles]]
* [[CDOL]]
* [[Maps and Boundaries]]
* [[Meetinghouse Locator]]
* [[Training]]
* [[:Category:Unit Administration|more...]]
</td>
</tr>
<tr>
<td colspan="2">
{{Box
| title=Acknowledgement
| color=green
| content=For many years Kent S. Larsen of New York City, New York, has personally funded and maintained a mailing list, discussion forum, and (more recently) a wiki for LDS clerks. The administrators of the LDSTech wiki wish to thank this pioneer of clerk training and the other long-time contributors to his site for generously donating all of the contents of their wiki (more than 100 pages of information) to the new LDSTech wiki. This contribution is a great blessing to clerks around the world, allowing the new site to “go live” overnight.
}}
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
__NOTOC__
__NOEDITSECTION__

User:Eblood66

2009-04-15T15:00:07Z

Eblood66:

==Eric Blood==

'''Location'''

Spanish Fork, UT

'''Professional'''

Chief Software Architect at InsurQuote (a LexisNexis company)

'''Development Experience'''

Lots and lots of Delphi and Perl. Quite a bit of ASP.NET (C#) and Javascript. Also some web-based Java database work. Many years of software architecture and design work along with a fair amount of project management.

'''Church'''

Currently ward clerk, recently EQ secretary.

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Contact Information
|-
| Email || [mailto:eblood66@gmail.com eblood66@gmail.com]
|-
| Yahoo || ted_the_lizard
|-
| Google Talk || eblood66
|}

Talk:Meetinghouse Computers

2009-03-30T23:13:31Z

Eblood66: Added signatures

This needs to be split into Administrative Computers and Family History Computers. While there may be some similarities, (Windows, Symantec, LANDesk) they are supported and controlled by different departments.) Use the wrong Desktop image and you've got problems.

A 3rd category "Other" (Unofficial FHC, etc) would also be a good idea. [[User:Russellhltn|Russellhltn]] 22:48, 30 March 2009 (UTC)

Please feel free to provide any information that you may have on the subject, the wiki is open to edit. Thank you. [[User:Calebpusey|Calebpusey]] 22:51, 30 March 2009 (UTC)

Remember to [[Guidelines#Sign_your_name|sign comments]] on Talk pages using 4 tildes (~). It helps keep track of the discussion. [[User:Eblood66|Eric Blood]] 23:13, 30 March 2009 (UTC)

Main Page

2009-02-26T02:24:11Z

Eblood66: New Feedback and Suggestions section

__NOTOC__
==Welcome to the LDSTech Wiki==

The purpose of this wiki is for the Church and community members to collaborate on various technology projects sponsored by the Church. We invite all to participate in these projects.

<table width="100%" cellspacing="0" cellpadding="0">
<tr valign="top">
<td width="50%">




<div style="margin: 0px 5px 10px 0px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">
===Announcements===
</div>
<div style="padding: 0px 5px 0px 5px;">
* '''Notice:''' Subversion, the Java repositories, Jira, and this whole Wiki are now accessed via HTTPS instead of HTTP. Please make sure you updated your links to represent this change.
* We have posted the first bit of documentation on the [[LDS Java Stack]]. More to come!
* Many people ask where Subversion is? The Subversion URL is https://tech.lds.org/svn. We have two projects posted there (HT/VT and Timeline).
* We have added Syntax Highlighting to the wiki so that if you paste source code snippits, they will show up with highlights. Read more about the syntax on how to add your source code and get the highlighting working [[metawikipedia:Extension:SyntaxHighlight_GeSHi|here]].
</div>
</div>





<div style="margin: 10px 5px 0px 0px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Current Projects===
</div>
<div style="padding: 0px 5px 0px 5px;">
Currently the Church is asking for help in collaborating on the following projects.

* [[Home Teaching / Visiting Teaching Application]]
* [[Church Historical Timeline Application]]
* [[IPhone Scriptures Application]]

Should you have any questions or suggestions please contact [[User:Welchtc | Tom Welch]]
</div>
</div>


</td>

<td>




<div style="margin: 0px 0px 10px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Requirements for Participation===
</div>
<div style="padding: 0px 5px 0px 5px;">
In order to participate and contribute to any projects that the Church sponsors, each individual must:
# Agree to and fill out the [http://tech.lds.org/index.php?option=com_content&task=view&id=140&Itemid=61 Individual Contributors License Agreement].
# Have an [http://ldsaccount.lds.org LDS Account]. To do so you must know your membership number and confirmation date. '''Note:''' Having an LDS Account is not the same as having a login to the Local Unit Web Sites. Please follow the [http://ldsaccount.lds.org LDS Account link] to get your account. LDS Account is the new unified authentication being deployed to all applications at the Church.
</div>
</div>





<div style="margin: 10px 0px 0px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Current Volunteer Needs===
</div>
<div style="padding: 0px 5px 0px 5px;">
* '''UI and Web designers''' for the [[Home_Teaching_/_Visiting_Teaching_Application#Current_Needs | Home Teaching / Visiting Teaching project]].
* '''QA Engineers''' for the [[Home_Teaching_/_Visiting_Teaching_Application#Current_Needs | Home Teaching / Visiting Teaching project]].

Our new [[LDSTech:Community_Portal|Community Portal]] is the central place for coordinating volunteer efforts. Go there to find ways you can contribute.
</div>
</div>

</td>
</tr>
<tr valign="top">
<td colspan="2">



<div style="margin: 10px 0px 0px 5px; border: 1px solid #D8D7C5;">
<div style="background-color: #F2F3E5; text-align: center;">

===Feedback and Suggestions===
</div>
<div style="padding: 0px 5px 5px 5px;">
Wiki pages are available for tracking feedback and suggestions on certain Church applications. Help improve these applications by adding your own suggestions. Please keep entries brief and concise. If expanded information or discussion is needed, post the information in the appropriate [http://tech.lds.org/forum/forumdisplay.php?f=21 LDS Tech forum] and add a link to the discussion in the wiki page.

* [[MLS: Feedback and Suggestions|MLS (Member and Leader Services)]]
* [[LUWS: Feedback and Suggestions|LUWS (Local Unit Web Sites)]]
* [[Online Scriptures: Feedback and Suggestions|Online Scriptures]]

</div>
</div>

</td>

</tr>
</table>

==New to LDSTech Wiki?==
LDSTech Wiki uses [[wikipedia:MediaWiki|MediaWiki]], a web-based [[wikipedia:wiki|wiki]] software popularly known for its use in [[wikipedia:Main_Page|Wikipedia]]. Consult the [[metawikipedia:Help:Contents|User's Guide]] for information on using wiki software. Here are some quick tips to help you get going.

* '''Searching for Articles''': To search for an article or some content within the wiki, type in your search phrase in the search box (where it says "wiki search..."). Then you can either press the '''Go''' or '''Search''' button to perform your search. The '''Go''' button will first search for an article with the exact name as you typed in. Then it will find all articles with the words you typed in. The '''Search''' button searches all articles for any of the words you typed in.
* '''Creating Articles''': To create an article, simple type in the search box the name of the article and press the '''Go''' button. A search will be performed with the exact article name as the one you typed in. If an article with the exact name is not found, there will be a link on the search results page that will allow you to create the article.
* '''Editing Articles''': To edit an article, simply press the '''Edit''' tab at the top of the article. You edit articles using "[[wikipedia:Wikitext|wikitext]]". [[metawikipedia:Help:Formatting|Here]] is a quick reference of formatting commands for your convenience.
* '''Discussing Articles''': If you want to discuss an article,click the '''Discussions''' tab at the top of an article and type in your comments.
* '''Red vs Blue Hyperlinks''': Red links are links to articles within the wiki that have not been created yet. Simply click on the link and you can then create the article. Blue links are links to wiki articles already created or links to external sites.

Template:OutOfDate

2008-11-19T04:24:39Z

Eblood66: New page: {| style="margin: 0 10%; border-collapse: collapse; background: #FBFBFB; border: 1px solid #aaa; border-left: 10px solid #F29626;" |- | | style="padding: 0.25em 0.5em; width: 100%;" | This...

{| style="margin: 0 10%; border-collapse: collapse; background: #FBFBFB; border: 1px solid #aaa; border-left: 10px solid #F29626;"
|-
|
| style="padding: 0.25em 0.5em; width: 100%;" | This section contains information that may be <b>out-of-date</b> due to later decisions or developments.<br/>{{{1|}}}
|}

<includeonly>{{{category|[[Category:OutOfDate]]}}}</includeonly><noinclude>
== Documentation ==
Apply this template to a discussion in a Talk Page to indicate that there is information in the discussion that may no longer be valid because of later changes or decisions in the project. In may also be used in documentation pages where out-of-date information cannot be deleted or modified.

=== Usage ===
Simply insert the template at the top of a Talk Page discussion by typing '''<nowiki>{{OutOfDate}}</nowiki>'''. In general you should supply a short description of what information is out-of-date and why it is invalid, e.g., '''<nowiki>{{OutOfDate|Feature X has been removed from the project requirements}}</nowiki>'''.

[[Category:Templates|OutOfDate]]
</noinclude>

TechWiki talk:Guidelines

2008-10-16T18:18:17Z

Eblood66: /* Template:Need Input */

User:Eblood66

2008-09-20T22:39:35Z

Eblood66: New page: ==Eric Blood== '''Location''' Spanish Fork, UT '''Professional''' Chief Software Architect at InsurQuote (a LexisNexis company) '''Development Experience''' Lots and lots of Delphi ...