FamilySearch Wiki talk:Naming Conventions: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
This page is for vetting ideas regarding the conventions or best practices we should provide to help contributors create clear, unambiguous, intuitive titles.
This page is for vetting ideas regarding the conventions or best practices we should provide to help contributors create clear, unambiguous, intuitive titles.


== System Constraints ==
== System Constraints/Behavior ==


Several constraints of the MediaWiki software that runs this site influence our decisions. They are:
Several constraints of the MediaWiki software that runs this site influence our decisions. They are:
Line 7: Line 7:
# Every title must be unique. The software uses titles as the identifier for each article rather than using some sort of unique identification number. This does not mean that a category and a page cannot have the same title. When a category is created, the string "Category:" is added to the title. Therefore, the system can have a page named "England" and a category named "Category:England."<br>
# Every title must be unique. The software uses titles as the identifier for each article rather than using some sort of unique identification number. This does not mean that a category and a page cannot have the same title. When a category is created, the string "Category:" is added to the title. Therefore, the system can have a page named "England" and a category named "Category:England."<br>
# The Exact Match search, which is the same as Wikipedia's Go search, is case sensitive for all words in the title after the first. So articled titled "Vital Records" and "Vital records" are different to the Exact Match search. For this reason, Wikipedia created a convention whereby all words in a title other than proper nouns must be lowercase. However, Wikipedia uses Go/Exact Match as their search default, where FamilySearch Wiki does not. Therefore, case may not be as big an issue to FamilySearch Wiki.
# The Exact Match search, which is the same as Wikipedia's Go search, is case sensitive for all words in the title after the first. So articled titled "Vital Records" and "Vital records" are different to the Exact Match search. For this reason, Wikipedia created a convention whereby all words in a title other than proper nouns must be lowercase. However, Wikipedia uses Go/Exact Match as their search default, where FamilySearch Wiki does not. Therefore, case may not be as big an issue to FamilySearch Wiki.
<!--{12069793785780} -->
# If there is a page named "Kings County, New York" and a page named "New York," and the user searches on the terms "New York" all the articles whose titles begin with "New York" are listed first in search results and the articles which begin with "Kings County, New York" is listed later. If the Kings County page is named "New York, Kings County," the search results page will have it mixed in with all the articles that begin with the terms "New York."
 
<!--{12070893034530} -->
<!--{12070893034531} -->


== Decisions Needed<br> ==
== Decisions Needed<br> ==
4,497

edits