User:RitcheyMT

From FamilySearch Wiki

(Difference between revisions)
(Changed Wahlquist's URL)
Line 35: Line 35:
 
The following are usability issues I think we should address in usability meeting:  
 
The following are usability issues I think we should address in usability meeting:  
  
#[[User:Diltsgd|User:Diltsgd]] reports that Search isn't finding any of the articles he authored in mid-July, namely 3 July - Southern Pacific Railroad; 4 July – Atchison, Topeka, and Santa Fe Railway; 4 July – Texas and Pacific Railroad; 4 July – Butterfield Overland Mail; 6 July – Atlantic and Pacific Railroad; 6 July – Central Pacific Railroad.  
+
<br>
#Search returns false results -- deleted page content. Reported by [[User:Diltsgd|Diltsgd]]. If you use the Search box to hunt for the Butterfield Overland Mail one of the items it will return is Sandbox 17. On 18 June the Sandbox held content related to the Butterfield Overland Mail but now has all content about trails removed. So we are getting a false hit on a page that no longer holds that content, and missing a hit on the page that is most directly about that title.<br>  
+
 
#[[User:Diltsgd|Diltsgd]] reports: From time to time I have noticed that an ampersand (&amp;) symbol appearing in an Internet URL is multiplied many fold in the Wiki. I notice it particularly on footnotes and other places where I will often include a URL address. If the phrase starts out in Rich Text Editor as "Railroad&amp;old" and in Wiki Text "Railroad&amp;old", after awhile (several saves?) it seems to turn into "Railroad&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;old"  
+
{| cellspacing="1" cellpadding="1" border="1" width="99%"
#[[User:Diltsgd|Diltsgd]] reports: Is there anything that can be done to make intermittent behaving Wiki footnotes more stable? The problem is that ALL the note numbers in the text appear as the number [1] and none of the actual words of the notes appear in the footnote area. About 1/3 of the time this problem happens, especially on articles with more than two footnotes. The articles with the most footnotes seem to have the poorest record. I would estimate that out of the last five times I’ve opened the New Sweden page with 90+ footnotes it has actually displayed the footnotes only once. But the problem crops up intermittently on almost every page with footnotes.  
+
|+ Usability concerns in FamilySearch Wiki
#Users are giving me feedback that the red words&nbsp;in search results are confusing them because in a wiki a red link means a page that has not yet been edited. Red=stub. And stub=lame article I wouldn’t select if it showed up in search results. They ask for search terms in search results to appear in a color other than red.  
+
|-
#How-to pages are "all over the place" according to one user, and need to be consolidated under one page. And other users say we need more cross-referencing between them.  
+
| '''Description'''
#Changing the style of headings. Heading 1 currently has bigger text than a page's title. We need to fix the styles site-wide so people can use Heading 1. (Added as a MOS item 16 June 2009.)  
+
| '''Date reported <br>in JIRA'''
#Bug: Look at the list above. On number 10 and 11, the leading 1 doesn't render right in IE7.  
+
| '''JIRA #'''
#Bug: internal links are getting ruined to look like this:&nbsp;&lt;a href="FamilySearch Wiki:WikiProject Linking to Books in the BYU Family History Archives"&gt;linking wiki articles to local histories on BYU Digital Archives&lt;/a&gt;  
+
| '''Date fixed'''
#Insert white space between end of an article and the social bookmarking <span id="fck_dom_range_temp_1244732887093_946" />tool.  
+
|-
#When someone clicks Discussion on a page, they then see a title "Talk:[article title]. This is confusing. The name of the link (Discussion) should match the name of the namespace (Talk).
+
| 1 [[User:Diltsgd|User:Diltsgd]] reports that Search isn't finding any of the articles he authored in mid-July, namely 3 July - Southern Pacific Railroad; 4 July – Atchison, Topeka, and Santa Fe Railway; 4 July – Texas and Pacific Railroad; 4 July – Butterfield Overland Mail; 6 July – Atlantic and Pacific Railroad; 6 July – Central Pacific Railroad.
 +
|
 +
|
 +
|
 +
|-
 +
| 2 Search returns false results -- deleted page content. Reported by [[User:Diltsgd|Diltsgd]]. If you use the Search box to hunt for the Butterfield Overland Mail one of the items it will return is Sandbox 17. On 18 June the Sandbox held content related to the Butterfield Overland Mail but now has all content about trails removed. So we are getting a false hit on a page that no longer holds that content, and missing a hit on the page that is most directly about that title.<br>  
 +
|
 +
|
 +
|
 +
|-
 +
| 3 [[User:Diltsgd|Diltsgd]] reports: From time to time I have noticed that an ampersand (&amp;) symbol appearing in an Internet URL is multiplied many fold in the Wiki. I notice it particularly on footnotes and other places where I will often include a URL address. If the phrase starts out in Rich Text Editor as "Railroad&amp;old" and in Wiki Text "Railroad&amp;old", after awhile (several saves?) it seems to turn into "Railroad&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;old"
 +
|
 +
|
 +
|
 +
|-
 +
| 4 #[[User:Diltsgd|Diltsgd]] reports: Is there anything that can be done to make intermittent behaving Wiki footnotes more stable? The problem is that ALL the note numbers in the text appear as the number [1] and none of the actual words of the notes appear in the footnote area. About 1/3 of the time this problem happens, especially on articles with more than two footnotes. The articles with the most footnotes seem to have the poorest record. I would estimate that out of the last five times I’ve opened the New Sweden page with 90+ footnotes it has actually displayed the footnotes only once. But the problem crops up intermittently on almost every page with footnotes.
 +
|
 +
|
 +
|
 +
|-
 +
| 5 Users are giving me feedback that the red words&nbsp;in search results are confusing them because in a wiki a red link means a page that has not yet been edited. Red=stub. And stub=lame article I wouldn’t select if it showed up in search results. They ask for search terms in search results to appear in a color other than red.  
 +
|
 +
|
 +
|
 +
|-
 +
| 6 How-to pages are "all over the place" according to one user, and need to be consolidated under one page. And other users say we need more cross-referencing between them.
 +
|
 +
|
 +
|
 +
|-
 +
| 7 Changing the style of headings. Heading 1 currently has bigger text than a page's title. We need to fix the styles site-wide so people can use Heading 1. (Added as a MOS item 16 June 2009.)  
 +
|
 +
|
 +
|
 +
|-
 +
| 8 Bug: Look at the list above. On number 10 and 11, the leading 1 doesn't render right in IE7.
 +
|
 +
|
 +
|
 +
|-
 +
| 9 Bug: internal links are getting ruined to look like this:&nbsp;&lt;a href="FamilySearch Wiki:WikiProject Linking to Books in the BYU Family History Archives"&gt;linking wiki articles to local histories on BYU Digital Archives&lt;/a&gt;  
 +
|
 +
|
 +
|
 +
|-
 +
| 9 Insert white space between end of an article and the social bookmarking <span id="fck_dom_range_temp_1244732887093_946" />tool.  
 +
|
 +
|
 +
|
 +
|-
 +
| 9 When someone clicks Discussion on a page, they then see a title "Talk:[article title]. This is confusing. The name of the link (Discussion) should match the name of the namespace (Talk).
 +
|
 +
|
 +
|
 +
|-
 +
| 9
 +
|
 +
|
 +
|
 +
|-
 +
| 9
 +
|
 +
|
 +
|
 +
|}
  
 
::I would agree with Talk vs. Discussion (#11 above). However, I believe that "discussion" would be more clear to most people especially those that are beginners. In other words, I would rather see Discussion than Talk being used. I also believe that the "Page" namespace can be a little intimidating and that "Article" (as Wikipedia uses) is a more friendly name. [[User:Thomas Lerman|Thomas Lerman]] 15:07, 14 July 2009 (UTC)
 
::I would agree with Talk vs. Discussion (#11 above). However, I believe that "discussion" would be more clear to most people especially those that are beginners. In other words, I would rather see Discussion than Talk being used. I also believe that the "Page" namespace can be a little intimidating and that "Article" (as Wikipedia uses) is a more friendly name. [[User:Thomas Lerman|Thomas Lerman]] 15:07, 14 July 2009 (UTC)

Revision as of 19:45, 28 September 2009

Michael Ritchey, the founding manager of FamilySearch Wiki, is a community and content manager of the Community Services team, a workgroup in the Family History Department, Corporation of the President, The Church of Jesus Christ of Latter-day Saints. The Community Services workgroup was assembled in December 2008. Roughly half the team came from the Research Support workgroup who are the founders of FamilySearch Wiki. 

Contents

My favorite report

Here's a report regarding wiki edit output from FHL reference units and individuals.

Good articles

  1. Prussia-Brandenburg Civil Registration details jurisdiction changes that affect which office would have documented vital records of ancestors there. Shows old place names with their modern equivalents, and links to indexes listing streets and their corresponding civil registration offices.

Users from whom I solicit opinions

These are the users who I invite to weigh in on wiki discussions -- particularly governance or Manual of Style issues.

  1. Diltsgd
  2. Dsammy
  3. Alan
  4. Thomas Lerman
  5. Franjensen
  6. Bakerbh
  7. Familyjournals
  8. Jbparker
  9. Baerbel
  10. Sonja
  11. Genguide
  12. CK Whipple (Kara Wahlquist)
  13. Batsondl
  14. Phillip Dunn
  15. Mormor
  16. Hendricksonp
  17. Proarenee

Usability concerns

The following are usability issues I think we should address in usability meeting:


Usability concerns in FamilySearch Wiki
Description Date reported
in JIRA
JIRA # Date fixed
1 User:Diltsgd reports that Search isn't finding any of the articles he authored in mid-July, namely 3 July - Southern Pacific Railroad; 4 July – Atchison, Topeka, and Santa Fe Railway; 4 July – Texas and Pacific Railroad; 4 July – Butterfield Overland Mail; 6 July – Atlantic and Pacific Railroad; 6 July – Central Pacific Railroad.
2 Search returns false results -- deleted page content. Reported by Diltsgd. If you use the Search box to hunt for the Butterfield Overland Mail one of the items it will return is Sandbox 17. On 18 June the Sandbox held content related to the Butterfield Overland Mail but now has all content about trails removed. So we are getting a false hit on a page that no longer holds that content, and missing a hit on the page that is most directly about that title.
3 Diltsgd reports: From time to time I have noticed that an ampersand (&) symbol appearing in an Internet URL is multiplied many fold in the Wiki. I notice it particularly on footnotes and other places where I will often include a URL address. If the phrase starts out in Rich Text Editor as "Railroad&old" and in Wiki Text "Railroad&old", after awhile (several saves?) it seems to turn into "Railroad&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;old"
4 #Diltsgd reports: Is there anything that can be done to make intermittent behaving Wiki footnotes more stable? The problem is that ALL the note numbers in the text appear as the number [1] and none of the actual words of the notes appear in the footnote area. About 1/3 of the time this problem happens, especially on articles with more than two footnotes. The articles with the most footnotes seem to have the poorest record. I would estimate that out of the last five times I’ve opened the New Sweden page with 90+ footnotes it has actually displayed the footnotes only once. But the problem crops up intermittently on almost every page with footnotes.
5 Users are giving me feedback that the red words in search results are confusing them because in a wiki a red link means a page that has not yet been edited. Red=stub. And stub=lame article I wouldn’t select if it showed up in search results. They ask for search terms in search results to appear in a color other than red.
6 How-to pages are "all over the place" according to one user, and need to be consolidated under one page. And other users say we need more cross-referencing between them.
7 Changing the style of headings. Heading 1 currently has bigger text than a page's title. We need to fix the styles site-wide so people can use Heading 1. (Added as a MOS item 16 June 2009.)
8 Bug: Look at the list above. On number 10 and 11, the leading 1 doesn't render right in IE7.
9 Bug: internal links are getting ruined to look like this: <a href="FamilySearch Wiki:WikiProject Linking to Books in the BYU Family History Archives">linking wiki articles to local histories on BYU Digital Archives</a>
9 Insert white space between end of an article and the social bookmarking tool.
9 When someone clicks Discussion on a page, they then see a title "Talk:[article title]. This is confusing. The name of the link (Discussion) should match the name of the namespace (Talk).
9
9
I would agree with Talk vs. Discussion (#11 above). However, I believe that "discussion" would be more clear to most people especially those that are beginners. In other words, I would rather see Discussion than Talk being used. I also believe that the "Page" namespace can be a little intimidating and that "Article" (as Wikipedia uses) is a more friendly name. Thomas Lerman 15:07, 14 July 2009 (UTC)

Projects

New items to prioritize in the backlog

  • 32k limit on page size: What browsers and browser versions choke on editing a >32k page?

Current projects 

Projects within the development sprint of 13 May - 9 June 2009

Sprint Story Project Sub-tasks Hrs.
Est.
Hrs.
Act.
Results
Begin managing U.S./Canada content creation @ the FHL using a disciplined management process.     35 25 Done
Launch project to link wiki pages to local histories on BYU Digital Archives.     6    
Split MOS page into many smaller pages, each about a separate issue     4 2 Done
Reach consensus on format for FamilySearch Wiki talk:Format for Citing and Linking to Works in FHLC, Worldcat (OCLC). (Combined with "Write a MOS guideline on the best way to link book titles, and how not to as well. ISBN? OCLC/WorldCat as 2nd option?"        2 Done
Reach consensus on FamilySearch Wiki talk:Source Citation Formats Chicago/Turabian/Shown Mills issue     4   3 Fail. Most people don't seem to care strongly about this issue.
Enable disambiguation by creating appropriate policy and prodecures and posting them. The policy and procedures should be part of the MOS. (Reach consensus on FamilySearch Wiki talk:Disambiguation.)      8  1.5 Done
Reach consensus on FamilySearch Wiki talk:Consensus (stretch)   4   Fail. It has not been easy to get people to comment.
Reach consensus on "Local Histories" or "History" heading issue     4  2 Done
Namespace discussion     2  2 Done
Test report that will show the number of contributions of of FHL authors. Report would be visible on the Special Pages for SysOps.     1  0.5 Done

Projects within the development sprint of 17 Apr - 12 May 2009

Sprint Story Project Sub-tasks Hrs.
Est.
Hrs.
Act.
Results
Enable other groups' projects in wiki. Enable U.S./Canada missionaries to engage in a wiki project. (Linking wiki articles to local histories on BYU Digital Archives.
  • Define a project on a project page. (Done)
  • Add the table of links to the wiki. Then break it up into smaller chunks to meet the 32k size constraints. (Done)
  • Document step-by-step process.
  • Train the trainers in the process.
  • Give technical support.
10    
Enable other groups' projects in wiki. Enable the U.S. Census project.
  • Engage David in scrum process.
  • Assign each employee a sub-project.
  • Have employees create a project page
  • Establish weekly progress tracking of all sub-projects.
5    
Enable other groups' projects in wiki. Enable the U.S. Vital Records project.
  • Assign each employee a sub-project.
  • Have employees create a project page.
  • Establish weekly progress tracking of all sub-projects.
5    
Enable other groups' projects in wiki. Enable Dorothy Horan's team in their wiki project.
  • Give support
  • Help them establish project page
  • Enable establishment of wiki mindset
5    
Enable other groups' projects in wiki. Enable APG to ramp up project to list professionals' services


5    
Enable other groups' projects in wiki. Enable someone to fix all the titles that are simply ranges of film numbers (the film-number titles are the result of an early FHL British Reference missionary project)
  • List pages in question
  • Create a new title format
  • Train user(s)
  • Track progress
5    
Enable other groups' projects in wiki. Enable miscellaneous projects and groups.
  • Create project pages.
  • Enable groups to reach objectives.
5    
Prioritize next steps for policy & procedure architecture done by Fran in last sprint. Review the wiki's existing policies and prioritize the order in which we address the gaps.   5    
Create new policy section for "Editing." Move editing policies to the new section and add new policies as needed. Study and add discussions and policies as needed.   18    
Create step by step plan for engaging genealogical societies with timeline and value proposition. Meet, brainstorm, and review value proposition for engaging societies.   5    
Total     68    

 

Projects within the development sprint, 20 Mar 2009 - 14 Apr 2009

Project Results
Launch projects to overhaul 2 U.S. record types at country and state level. Projects are launched, but team leads are scheduled a laughable amount of wiki time to manage them. Michael has worked many hours on trying to win more wiki time for the team leads. If priorities don't change at the FHL or we don't decide to use the community to do these writing projects, deliverables for US/Canada content will remain in jeopardy.
Enable community to work on projects. The community needs a way to see and then volunteer to engage in multiple projects.
  1. Merged and simplified lists of projects on <a href="Community Portal">Community Portal</a>.
  2. Enabled Dorothy Horan's team to work on describing Record Search collections.
  3. Enabled the Authorities team to progress on its integration project by creating <a href="FamilySearch Wiki:WikiProject Integrating Place Standards Database with FamilySearch Wiki">WikiProject Integrating Place Standards Database with FamilySearch Wiki</a>, which tracks issues, solutions, and progress.
  4. <a href="FamilySearch Wiki:Naming Conventions for Project Pages">Created FamilySearch Wiki:Naming Conventions for Project Pages</a> to steer the community into adopting standards that will enhance searchability of project pages by defining which namespace they will be stored in and by clarifying which keywords will be used in naming them.
  5. Enabled US/Canada team leads to work on <a href="FamilySearch Wiki:WikiProject U.S. Vital Records">WikiProject U.S. Vital Records</a> and <a href="FamilySearch Wiki:WikiProject U.S. Country and State Pages about the Census">WikiProject U.S. Country and State Pages about the Census</a>.
  6. Created <a href="FamilySearch Wiki:Sources of Information for a United States Record Type Article">FamilySearch Wiki:Sources of Information for a United States Record Type Article</a> to improve article quality and completeness, track progress, and define specific sub-tasks which allow writers to work on various aspects of revising a common article without tripping over each other.
  7. Enabled APG members to work on <a href="FamilySearch Wiki:WikiProject Professional Genealogists">WikiProject Professional Genealogists</a>.
  8. Obtained data for missionaries to work on <a href="FamilySearch Wiki:WikiProject Linking to Books in the BYU Family History Archives">FamilySearch Wiki:WikiProject Linking to Books in the BYU Family History Archives</a>.
Enable community to vet best practices regarding where to place cemetery information (county vs. town pages).


This task is dependent on adding 1st round of policies and procedures. It was a mistake to think that story could be completed and this one completed afterwards all in one sprint. Experience has taught us that a smarter method is to research something in one sprint, make recommendations for review in the second sprint, review the recommendations in the third sprint, and deploy it in the fourth sprint. This particular item called for a deployment of a solution that had not yet been researched, recommended, or reviewed. Dumb idea.

Add 1st round of policies and procedures. Add to the wiki the 1st round of policies and prodedures that will allow the community to gevern themselves.
  1. Created <a href="FamilySearch Wiki:How Community Governs Wikipedia">FamilySearch Wiki:How Community Governs Wikipedia</a> and added to it incrementally.
  2. Helped solve 2-column rendering problem associated with Fran's great pages on policies such as <a href="User:Franjensen/Policies and Procedures">User:Franjensen/Policies and Procedures</a>.
  3. Like the cemetery information task above, this task called for deployment of a solution that had not yet been researched, recommended, or reviewed.

Other current projects

  1. <a href="FamilySearch Wiki:How Community Governs Wikipedia">FamilySearch Wiki:How Community Governs Wikipedia</a>
  2. Link to all US/Canada <a href="FamilySearch Wiki:WikiProject Linking to Record Search">data sets on Record Search</a>.
  3. Link to all US/Canada histories loaded on the <a href="http://www.lib.byu.edu/fhc/index.php">BYU Digital Archives</a>.
  4. Update all census pages for the U.S. at the country and state level. Add information to these articles from sources on <a href="FamilySearch Wiki:Sources of Information for a United States Record Type Article">FamilySearch Wiki:Sources of Information for a United States Record Type Article</a>.
  5. Update all vital records pages for the U.S. at the country and state level. Add information to these articles from sources on <a href="FamilySearch Wiki:Sources of Information for a United States Record Type Article">FamilySearch Wiki:Sources of Information for a United States Record Type Article</a>.

Past projects

Feb 18 - Mar 17 Sprint

  1. Copy United States Reference Documents from <a href="http://www.familysearch.org">FamilySearch Internet</a> to FamilySearch Wiki.
  2. Copy <a href="Canadian content in FamilySearch Research Guidance and Help">Canada Reference Documents from FamilySearch Internet</a> to FamilySearch Wiki.
  3. Add county creation dates and parent counties tables to all U.S. states. See an example: <a href="Wisconsin County Creation Dates and Parent Counties">Wisconsin County Creation Dates and Parent Counties</a>.

Jan 17-Feb 17 Sprint Organize and enable FHL staff for Maryland barn raising 

See <a href="Maryland Barn Raising Tasks">Maryland Barn Raising Tasks</a>

Item Est. Time Time spent Finished
Plan the 4 barn raisings that follow the MD barn raising 5.0    
Draft value proposition for societies  16.0  0.5   
Strengthen MD portal  8.0     
Run user group  8.0     
Track tasks on Michael's user page  3.0  1.0   
Schedule meetings with U.S./Can employees  4.0  2.0   
Initiate 1-on-1 enabling meetings w/ contributors regularly  20  4.0   
Review content being written during barn raising & publicly recognize authors for it. (include in Did You Know section, for example)  4.0  1.0   
Change wiki e-mail address to @FamilySearch.org   1.0     
Unplanned wiki work  16.0 5.5  
Write a how-to on the best way to link book titles and show it to contributors 4.0    
Help authors delegate tasks 8.0
stretch
   
Train someone to get permissions for record type images, scan & upload them, & place them on pages  2.0
stretch
     
Assign all MD topics to writers  2.0
stretch
   
Vet news & events solutions w/ user group  2.0
stretch 
   
Strengthen county page example  2.0
stretch 
   


Dec 17-Jan 17 sprint

Item Est. Time Started Finished
Meet with Wilma and Diane to address wilma's ideas. 2.0 x
Assign all Md. topics to writers. 2.0 slips to next sprint
Recruit someone to get permissions for record images and scan and upload them and place them on pages. 0.5 x
Train someone how to get permissions for record type images, scan and upload them, and place them on pages. 2.0 slips to next sprint  slips to next sprint
Introduce authors to vetted headings. 1.0
Create pg. re. sources to check for info. for a topic pg. (including FHL favorites) and link to it from project page. 2.0
Speak with authors 2x per week to learn of their obstacles. 5.0
Create Md un-portal. 3.0
Teach authors best practices in citing works studied but not cited. Create <a href="FamilySearch Wiki:Sources Consulted but Not Referenced">FamilySearch Wiki:Sources Consulted but Not Referenced</a>. 1.0

 

Engage helpers and research assistants for Maryland barn raising 

Item Hrs. Planned Started Finished
Build up my user page more like Fran's with links to guideline pages I use. 4.0 x x
Engage someone in linking all Md. topics discussion pages to heading example pages. 1.0 x
Write page on major data sites for U.S. research (this fills dependency for missionary to link wiki to 3rd party data sets) (We might get this from FHL favorites?) 2.0    
Help authors delegate simpler tasks to missionaries. 5.0
Recruit someone to link wiki pages to <a href="FamilySearch Wiki:WikiProject Linking to Record Search">data sets in record search</a> and 3rd party sites. (Dependent on a pg. of U.S. data sites) 1.0    
Recruit someone to <a href="FamilySearch Wiki:WikiProject Linking to Books in the BYU Family History Archives">link wiki pages to digitized books in the BYU Family History Archive</a>. 2.0   
Recruit someone to add to wiki pages the record content bullet lists from <a href="http://www.familysearch.org/eng/search/RG/frameset_rg.asp">Research Guidance</a> and/or <a href="http://productsupport.familysearch.org/supportroot/Eng/Frameset_Products.asp?ReqPg=EntryDetails.asp&entryid=Q100151797800023&version=1&FAQ=FHSourceGuide&Product=FHSG&Color=green&DisplayName=Family+History+SourceGuide">SourceGuide</a> (Pitts, Parkins) 2.0  
Recruit a <a href="FamilySearch Wiki:WikiProject Maryland News and Events">Maryland news and events "reporter"</a> (also have him/her do Did You Know section) (Depends on creation of <a href="Finding Genealogy News and Events within the United States">Finding Genealogy News and Events within the United States</a>) 2.0  

Replacement for portal template

<img src="/en/images/thumb/9/94/Dbase_error.jpg/180px-Dbase_error.jpg" _fck_mw_filename="Dbase error.jpg" _fck_mw_type="thumb" alt="Here's an error" class="fck_mw_frame fck_mw_right" />The place portal pages (those titled "Portal:[place name]" use a MediaWiki template to create and lay out the boxes on the page. This template is problemmatical for two reasons. First, the content of each box on a portal page is actually a sub-page, so none of the content in the sub-pages is considered by search engines to be on the portal page itself. So although a portal's sub-pages may contain a lot of great content, search engines don't attribute any of that content to the portal page itself. That means words within in the sub-pages cannot be used in a search engine to find the portal page. As far as search engines are concerned, then, the Denmark portal page is just an empty shell with some code, not a content-rich page on everything you need to know about Danish research. This problem is common to external search engines like Google as well as the wiki's own search engine. To solve the problem, we need to find a more search-engine-friendly way to lay out boxes in our place pages. Mollie, Fran and Michael have all tried different solutions; have a look and see which ones you like.

  1. Mollie's <a href="England/Test1">England/Test1</a> page
  2. Fran's
  3. Michael's <a href="Pennsylvania">Pennsylvania</a> page

Some projects from 2007

Item Assignee Date done Entrance requirement for Closed Beta (Beta 2) Exit requirement for Beta 2 Requirement for Open Beta?
Implement page reviewing in Plone Michael/Mollie 13 Nov 07 X

Write page on purpose of site Michael/Mollie 16 Nov 07 X

Write page on appropriate types of content Michael 18 Nov 07 X

User acceptance on "done" items. Rsrch Suppt 21 Nov 07 X

Create user list for closed beta Bruce/Amos 28 Nov 07 X

Delete empty "test" articles as per report from Bruce Elder Johnson 30 Nov 07 X

Definitions of disallowed content types Michael 03 Dec 07 X

Review/Delete 148 test/junk pages Elder Johnson 04 Dec 07 X

Manually fix 870 broken links Mollie 05 Dec 07 X

Discover predicters of admin role growth Mollie 05 Dec 07 X

Determine requirements for categories Rsrch Suppt 05 Dec 07 X

Create standards for naming place pages Michael 05 Dec 07 X

Remove the word "Wiki" from portal pages Mollie
07 Dec 07
X

Specify language of 862 articles with no lang. attributed Mollie 10 Dec 07 X

Fix duplicate titles Sister Ackerson 11 Dec 07 X

Remove pull-quote navigation boxes sitewide Bruce 11 Dec 07 X

Fix thousands of misformatted FHLC call numbers Bruce 12 Dec 07 X

Write page on how to categorize Darris 12 Dec 07 X

Increase font sizes for readability David 13 Dec 07
X

Move Edit links from in front of headings (Left justify "edit" links) David 13 Dec 07 X

Identify all how-tos
Anne, Darris, Michael, Mollie
13 Dec 07
X


Delete all Research Topics pages
Mollie
13 Dec 07
X


Fix search result numbers so they are not off to the side of the main article box
David
13 Dec 07
X


Find out how widespread the table migration problem is.


Mollie
14 Dec 07
X


Troubleshoot any loss of formatting from Plone --> MediaWiki that will require hundreds of hours of manual cleanup. Darris, Michael 14 Dec 07, ongoing
X

Prioritize writing order of how-to pages
Michael
17 Dec 07, ongoing
X


Write how-to pages Kay 17 Dec 07, ongoing
X

Define requirements on browse taxonomy for places
Michael 19 Dec 07
X

Fix pages with colons. Fran 19 Dec 07 X

Fix Main Page's country list Michael 19 Dec 07 X

Delete Main Page's topics list
19 Dec 07 X

Minimize # of links in Nav bar Michael 20 Dec 07
X
Add Contact Us link to Nav bar Michael 20 Dec 07
X
Create Contact Us link on Home page Michael 20 Dec 07

X

Fix U.S. states table Mollie 20 Dec 07
X
Write page about renaming pages Kay


X

Write page about how to disambiguate page titles Kay

X

Write page about how to add a new language site Michael

X

Find a searchable home for Private content Michael

X

Check Special Page --> Articles with Most Revisions to identify any necessary cleanup 



X
Skin: Reinstate the create this page link to Search Results screen.


X
Add category for Articles for Deletion


X
Move login link so it is visible without scrolling



X

Need additional search options



X

Write lesson on creating browse taxonomy and categories for places.


X
Define and write lesson on creating browse taxonomy and categories for non-place topics.


X
Write requirements for improving Search


X
Add linked list of record types to each place page


X
Research copyright/copyleft licenses Ransom

X
Requirements for linking using WYSIWYG tool Darris

X
Requirements to simplify adding a page Darris

X
Create Sandbox where new users can test edit tools Bruce

X
Research and list all templates the site needs (disambiguation, stub article, etc.).


X
Research all actions admins should do.


X
Research all bots the site needs.


X
Find extension to allow pasting of tables from other apps.


X
Add a way to recognize top contributors


X
Plan to solicit needed articles



X
Plan on oversight of domains and portals Mollie


X
Moderation Plan: Reviewing new articles in MediaWiki Michael/Mollie


X
Moderation Plan: Image review and copyright Michael/Mollie


X
5 pillars Michael


X
Namespaces



X
Rating content




Moderation Plan: Ranking users



X
Moderation Plan: Research the work volume per role



X
Moderation Plan: Staffing plan per role



X
Moderation Plan: How to populate sections on home pg. & portals (Did You Know, Featured Article, Articles Needed, Popular Discussions, and Featured Training Modules)



X
Moderation Plan: FHL SMEs & content management



X
Moderation Plan: Identify needed content




Moderation Plan: Block & restore content and users




Moderation Plan: Protect and Unprotect pages




Moderation Plan: Edit a protected page




Moderation Plan: Libel or copyright infringement




Moderation Plan: Disambiguation




Moderation Plan: Speedy Deletion




Moderation Plan: Content Redundancy




Plan to recruit, organize, and recognize contributors




Policy on conduct










Useful Tools

Marketing tools

Admin/Sysop/Founder aids

  • <a href="Running a Project">Running a Project</a> gives helpful tips on how to manage a team to write targeted content.

Authoring aids

  • <a href="FamilySearch Wiki:Headings for Articles about Records">Article headings</a> the wiki community has developed for use in articles.
  • <a href="Portal:Contribute">Contributer Portal</a> covers all things relating to authoring on the wiki.
  • <a href="Help:How to add citations">How to add citations</a> shows how to add wiki code that creates endnotes in an article.
  • <a href="Policy:Purpose and Appropriate Topics">Purpose and Appropriate Topics</a> lists the types of articles writers should and shouldn't write on this wiki.
  • <a href="FamilySearch Wiki:Sources Consulted but Not Referenced">FamilySearch Wiki:Sources Consulted but Not Referenced</a>.
  • <a href="http://en.wikipedia.org/wiki/WikiProject_Alternative_Music">Wikipedia:WikiProject Alternative music</a> may give us some ideas about how to create a project page.

Related pages

<a href="User:Ritcheymt/Sandbox">Michael's sandbox</a> | <a href="User:Ritcheymt/Sandbox 2">Michael's sandbox 2</a> | <a href="User:Ritcheymt/sandbox 3">Michael's sandbox 3</a>
<IMG class=FCK__MWTemplate height=1 src="https://wiki.familysearch.org/en/extensions/FCKeditor/fckeditor/editor/images/spacer.gif" width=1 _fckfakelement="true" _fckrealelement="0" _fck_mw_template="true"> 

<a _fcknotitle="true" href="Category:Help">Help</a> <a href="Category:Family_History_Library_Employees">User:Ritcheymt</a>
https://familysearch.org/learn/wiki/en/index.php?title=User:RitcheyMT&diff=216109&oldid=211857
familysearch.org
crawl=CC-MAIN-2014-10
112146
application/http; msgtype=response
sha1:Z3HUTV547HLJ4GG7QM4MV4Z4ESH2MDFL
<urn:uuid:82cb7860-f9d7-4ada-8a2f-2b347e6d73dd>
2014-03-17T16:10:20Z
204.9.224.11
sha1:REEMAGDWDMJQDFGWO7XIOFA2ABNBLGKS
<urn:uuid:37cbc10c-16f2-4e5e-9438-6e227e9f8eb6>
https://familysearch.org/learn/wiki/en/index.php?title=User:RitcheyMT&diff=216109&oldid=211857
response
<urn:uuid:b81e5043-9f73-4dea-b0f9-b60aefea3d9d>
robots: classic
hostname: ip-10-183-142-35.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-10
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for March 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf