Talk:Meta:US StructureEdit This Page
From FamilySearch Wiki
US State / County Structure
We need to develop a structure for articles on geographic entities in the United States. Please contribute your ideas, and critiques to this page. Feel free to comment inline below, or in a new section. Please sign your articles with ~~~~.
We need a structure that will allow unique places to be identified and located easily. We need to provide a way so that new and existing users can easily drill down to the county they need and find vital records information. We need to make it easy for new users to know where and how to contribute information to the wiki.
We need to restrict this discussion a bit so we don't spend forever working out every detail. Assertions are proposed as follows:
- All solutions are sub-optimal
- All solutions to this problem are not going to be able to satisfy all of the requirements and possibilities needed. We will have to have trade-offs in some places.
- United States only
- We will restrict this debate to the United States only.
- This is likely the most commonly understood nation for this group.
- This will include oddities in the US like previous governments, tribal lands, unincorporated areas, territories, moving borders and others. If you have other uncommon places, please add them here
- We will NOT include places outside the US, except where those places need to be differentiated from places in the US. For instance, places named 'Washington' outside of the US would need to be differentiated from places in the US.
- Rarer exceptions will not fit the structure
- It is likely that any structure we develop will not work for certain exceptions. We accept that some things may be in weird places, or need unusual navigation to get to.
- Handling of rare exceptions should not be the focus of this structure, but should not be ignored. Points will be awarded to elegant handling of these exceptions.
- Time is HUGE
- All of the entities that fit into this structure have changed over time. The structure needs to be able to differentiate between current, and historical information, as well as information that existed before the entity.
We need a list of problems that we need to address. We also need a list of features we would like in a solution
- Names must be unique to a place. This is enforced by the wikimedia software.
- Names must be human readable. Names show in lots of places on the page. People have to know what they are looking at, and make sense of how the page title relates to the place they are looking for.
- Names should be computer readable. Generally, if names are human readable, they are also computer readable, but this is not always the case.
- Names should include a hierarchy. Hierarchical names facilitate navigation, and also point to higher and lower level places related to the place. For example, the bare name 'Washington' does not indicate whether it is a part of a larger state, or a county, nor does the name indicate if it is a link to a smaller place like a city, or a larger place like a state.
- Names should be accessible by the search function. It does no good to name a place a cool name, then prevent users from finding it because the search engine can't.
- Names should allow for smaller divisions. Currently, we are looking at states and counties, but we may add cities, wards, districts, neighborhoods, families or other smaller organizations.
- Names should allow for dates. Looking for records in NY in 1770 is very different than looking in 1970. This structure should allow that.
- Names should be easy to differentiate. A user should not have to look to the 70th character of a name to decide if it is a state, or county.
- Names should show in the search page approximately ranked such that a users intended result is very near the top. A search for 'Washington DC' should show the district article in the first few articles listed. If it shows further down, or on additional pages, users will have a hard time finding it.
- Name structure should be easy for people to remember. It should be possible for an experienced editor to manually enter a link to an article without having to search the wiki first.
- Should Nots
- Names should not ignore places outside the US. Eventually we WILL have to build a structure for the whole world.
- Names should not show in the search box if they are not relevant to the search entered. Getting a bunch of search results named 'Not Washington DC' is not going to help you find 'Washington DC'. Additionally, including the entire hierarchy in the name of the page may result in getting lots of detailed articles (county and city level) when looking at a much higher lever (federal)
- Names should not contain abbreviations or acronyms. Shorter names means fewer characters to differentiate names, and may confuse users.
- Names should not contain redundant information. Names like 'Utah County, County, Utah State, State' are hard to read, and difficult to type and search for.
There are a number of issues that do not fit nicely into the 'State, County, City' hirearchy. Please add your exceptions and ideas here.
- Colonial and pre-incorporation records
- Where should colonial records appear. Should there be a link called 'New York, 1400-1770'. What would you put in the 'Utah, 1400-1770' article? What do you do for lands that were Dutch, French or Mexican that are now part of the US?
- Indian lands, tribes and records
- Should these be under the federal level, or linked from each state? Should these be by tribe? What do you do if a tribe, or land goes away, or moves?
- Cross-state and cross-county cities
- Which state or county do you put them in? How would a user find the city, or where to look for the city?
- Ellis Island
- Does Ellis Island go at the federal level, or as part of New York State, or New York City, or New Jersey?
Solution 1 The Earl
- Entities are named in descending order of specificity.
- Entities are separated by commas and spaces.
- Most specific entities include their organizational type at the county level and lower.
- Abbreviations are used for all but the two most specific entities.
- Time will always be the most specific entity.
- Articles will exist in the Main namespace, with portals in the Portal namespace. Portals would summarize main articles, and provide easy navigation up and down the structure.
- Entities will link to all included entities, and their immediate parent. This would most likely be inside of navigational structures, and only occasionally in the article itself.
- Time articles will be linked from their current political structure
- US Tribal lands and Ellis Island will exist under the federal structure, and be linked from other (state, county, etc.) articles
- Boundary movements and changes will be noted on their current political entity, and linked from there.
- Cross-state and Cross county entities would be found through search
- Categories would specifically be created to help with non-hierarchical navigation (ie, Category:Vital Records)
- It would be hard to find the city you are looking for without knowing the county it resides in.
- This would be mitigated by the ease of searching for the city, and links to major cities from the state page.
- It would be hard to find date specific information across a number of entities.
- This would be mitigated by entering date information in addition to the entity name in the search box.
- This would not work well with 'Exact Match' searches.
- This would not be mitigated, as search is an integral part of navigating this structure.
|United States of America||Main article on the United States of America.|
|Portal:United States of America||Portal article on the United States of America containing links to Ellis Island, Tribal and all state articles.|
|Ellis Island, United States of America||Main article on the Ellis Island.|
|Utah, United States of America||Main article on the state of Utah. Includes navigation links to Provo city article.|
|Utah County, Utah, USA||Main article on Utah County, state of Utah. Contains links to all cities in Utah County.|
|Provo City, Utah, UT, USA||Main article on the city of Provo, Utah County. Includes links to districts, wards, and families in Provo City.|
|1560-1770, New York, USA||Specific article on New York State records between 1560 and 1770. Included in Category:1500-1800 records.|
|1560-1770, New York, NY, NY, USA||Specific article on New York City records between 1560 and 1770. Included in Category:1500-1800 records.|
|1500 New York||
Ritcheymt, I have pulled some of your comments up to here. It is getting hard for me to follow some of the discussion below, and it seems we agree on most things.
The portal for NYC should probably be called “New York, New York.” The one for the county should probably be called “New York County, New York.” Articles about both should be categorized under both the county and the city categories. Ritcheymt 00:30, 16 March 2008 (MDT) (LOL - Note that it was a half hour after midnight when I wrote that example. Clearly I was suffering from sleep deprivation: There is no New York County, New York. I was thinking of Kings County, which wouldn't help with this ambiguation argument at all. Ritcheymt 23:31, 26 March 2008 (MDT))
- We are mostly in agreement on this. I would place NYC at "New York City, New York, NY, USA" and NY County at "New York County, New York, USA". I am not clear on what categories should exist, nor which articles should be in them. I am not as familiar with categorization on a wiki, and would mostly defer to your opinion on them. It seems you have a clear plan for them. I would explicitly use them where non-hierarchical navigation was needed. The Earl 08:37, 17 March 2008 (MDT)
No, Utah content is not relevant to someone doing a search for U.S. content. Wikipedia handles disambiguation nicely without the use of slashes in titles. See my earlier comment about disambiguation pages. Ritcheymt 00:30, 16 March 2008 (MDT)
- Ok. I think we agree to the extent that 'Utah content should not show in a search for USA above US Federal content.' I also agree that slashes are ugly. The Earl 08:37, 17 March 2008 (MDT)
Not to say that Wikipedia is perfect, but I think it’s prudent to examine the model of another site that has some years of experience. Following Wikipedia’s naming conventions, a page for a town might be named either “Rockville, Montgomery County, Maryland” or “Rockville, Maryland.” I think this works well. To require or advise users to use slashes and underscores in titles is to ask them to do something which is quite unintuitive to them. Therefore, compliance will be low and either we’ll end up with a “standard” that never really becomes standard in practice, or we’ll need an army of people to come in and “move” or rename all the pages our users name without following the standard. So the result is that this “standard” either fails to enhance findability of articles or else it takes a gargantuan amount of work to maintain. I think that’s one reason Wikipedia doesn’t do things this way. Ritcheymt 00:30, 16 March 2008 (MDT)
- Underscores are spaces. They are automagically converted by wikimedia. While I agree with your concerns about slashes, I disagree that the underscore suffers from the same problems. If you look at the Wikipedia page for "Rockville, Maryland", you will see that the actual page URL is "Rockville,_Maryland". This page shows the conversion as well. Search / Edit / Link all handle the space transparently.
- I also share your concerns about maintenance. My hope is that good templates will create the structure, and users will just have to fill in the content. I am not concerned about a page called "How I found records in Utah county, Utah", but that you can find Utah county, and link to the article from there. The Earl 08:37, 17 March 2008 (MDT)
When you say “navigate” what do you mean? I can imagine a naming convention helping users search, but don’t see how it would help navigate. Navigation in MediaWiki is normally accomplished through links or through categories. Ritcheymt 00:30, 16 March 2008 (MDT)
- "It should be possible for an experienced editor to manually enter a link to an article without having to search the wiki first."
- That is basically what I have in mind when I say "navigate". The portal pages should link up and down the structure, allowing link navigation of the structure. Portal pages should also link to the main (and or sub) articles for their page. That requirement is really just a re-statement of the requirements that the convention be human readable and predictable.
- Again, I am not as familiar with categories, so my corresponding statement to yours would be: "Navigation is normally accomplished through links or search". That may explain some of our differences. The Earl 08:37, 17 March 2008 (MDT)
How do encyclopedias determine which families to include? And to the extent that this site will have pages on towns and counties which an encyclopedia will not have, how would you keep the community from creating millions of pages on families that are prominent in one-stoplight towns? Also, could you explain the language about “public?” Ritcheymt 00:30, 16 March 2008 (MDT)
- Mostly, I do not want to omit information on founders or people of other historic prominence. I cannot imagine an article about Utah that did not include the names of Jim Bridger, or Brigham Young. I do not think that the page should include a history of them and their families. Since external links to families are allowed, I think it prudent to include a place for families so that they don't end up in strange places on the wiki. As family articles specifically are out of scope, I am willing to concede this point, I just worry that ignoring them now will cause problems in the future. The structure would not enforce the policy, nor should it. We might need a discussion solely on allowed / disallowed family content. I do not want to derail discussion on a structure by arguing about families. The Earl 08:37, 17 March 2008 (MDT)
The best way is to attend usergroup meetings, but really, our core team of employees meets often during the week to make course corrections. Some we decide upon verbally, so you won't find documentation on every decision we make, as with this one. Ritcheymt 00:47, 16 March 2008 (MDT)
- This needs to be discussed. I will try to find a place for it. The Earl 08:37, 17 March 2008 (MDT)
I have a pretty gelled idea of what I think the structure should be. It falls mostly in line with what you propose above. I was hoping to get more of the meta-information up sooner, so that we could make sure that everyone's concerns were addressed before I posted a proposed structure. I found that even when writing the requirements above, I tended to tailor them to my solution, which artificially supports my structure. My old structure (IMO) is enough to throw darts at, and has enough holes to invite them :). I will post my proposed structure today (3/17) or tomorrow so that it isn't a surprise at Wed meeting. I will be at the meeting 3/19, and will be more than willing to participate in that discussion. Thanks The Earl 08:37, 17 March 2008 (MDT)
In navigating through the US portal, I have come up with a suggested structure for the US.
I am most interested in building a resource for people looking for vital record repositories in locations in the US. I think this is an important resource, as it is very easy to verify its accuracy, and imminently useful to new and potentially new users. Working in the US gives me a chance to try this in a well understood environment. It is hoped that the lessons I learn here can help those looking to build a similar resource for other areas of the world.
So I propose that we make it simplicity itself to get to a given county in a given state in the US, and post the contact info for local FHCs, vital record offices, and allow locals to post contact info if they are willing to help with the footwork. Links to local research lines, or public prominent families could be available here as well.
Structure as follows:
Main US article, may be a redirect to United_States. Country codes could be used Wiki-wide
Articles under the US. This would be used for things like Social Security death index, Federal database searches, and similar. Ellis Island article may exist here, or under NY state article. May include sub-pages from main US article like US/List_Of_States.
Main state articles. Examples would be /US/Utah, /US/New_York
Articles related to the given state, similar to what would be under the US. Examples: US/New_York/State_Vital_Records, US/New_York/State_Attractions.
County level articles.
Additional levels may be needed for large cities, or public prominent family histories, but these would be added as-needed.
Corresponding Template and Portal sections would be needed as well. It is hoped that with a proper template system, very little work would be needed to build out and maintain this area. Additionally, the portals would allow easy navigation and summary of the main articles.
US Portal Page (existing). Redirect from Portal:US
Individual state portal pages (existing would be moved here). State portal sub-pages would be put under here.
County portal pages
Template for US States
Template for US County
It is anticipated that this 'gazetteer' would be a small part of the wiki, but a great resouce for people looking to start family history. Additionally, basing the structure on the country code would allow other country structures to mirror this one, with minor modifications if needed.
Thanks The Earl 17:50, 7 March 2008 (MST)
I'm having trouble understanding the proposal.
- Is the proposal that we should link to all state portals from the United States portal, link to all a state's county and city portals from the state portal, link to all a county's cities and townships from the county portal, etc.? If so, I strongly agree. A bunch of people want to do this; we just haven't had enough bodies to get it done. Ritcheymt 10:34, 12 March 2008 (MDT)
- Yes, and thanks The Earl 07:41, 10 March 2008 (MDT)
- Is the proposal that we should separate a country's portal pages from its main article page? We tried something like that when we were still using Plone and it was counterintuitive to the users. Since each place had multiple "main pages," users didn't know where to find the information they needed regarding a place. It felt like the user experience of Wikipedia's Portal:India page vs. their India page. Ritcheymt 10:34, 12 March 2008 (MDT)
- I would hope that the Portal page would summarize the main article, and link to the main article. Currently, the portals show a few content boxes, while the main article is more free-form. I hope that as long as the portal points to the main page (which is not the case always now) this confusion would be limited The Earl 07:41, 10 March 2008 (MDT)
- Currently some localities have both a portal page and another page taken from the research outline that's mostly text in paragraphs. It is confusing, as you mentioned. Our plan is to consolidate these two pages into one portal page. Ritcheymt 10:34, 12 March 2008 (MDT)
- This seems backwards to me of the way a portal should work. Please explain where I can get more information on "Our plan". Thanks The Earl 11:59, 12 March 2008 (MDT)
- The best way is to attend usergroup meetings, but really, our core team of employees meets often during the week to make course corrections. Some we decide upon verbally, so you won't find documentation on every decision we make, as with this one. Ritcheymt 00:47, 16 March 2008 (MDT)
- Is the proposal that we should create some standards or at least best practices for the naming of a place page? If so, I strongly agree. I think Wikipedia folks have found this useful. For instance, I think I recall some user this past week naming a page about a county "Washington." Well, there are a lot of places named Washington, so this title was ambiguous and will need clarification.
- Agreed, this is the crux of why I propose this structure. The Earl 07:41, 10 March 2008 (MDT)
- Clarification of ambiguous page titles in Wikipedia is handled through disambiguation pages. See Wikipedia's Washington page and their Washington (disambiguation) page. It seems to be a good model, and helps prevent naming conventions that would spam the search engine. Ritcheymt 10:46, 12 March 2008 (MDT)
- I get the disambiguation page, but the articles AFTER the disambiguation page all have other identifying information in them, ie 'Washington,_Arkansas', 'Washington_DC', etc. I think a disambiguation page is needed here as well, I am just proposing a structure for the main articles that the disambiguation would link to. The disambiguation page does not prevent search engine spam at the Wikipedia site, searching on 'Washington' gets you all of those pages, and the disambiguation page. Searching on 'Arkansas' should, IMO return 'Washington,_Arkansas' as well, but in a bit more friendly order, not its current Wikipedia behavior of taking you to the article 'Arkansas'. Currently on Wikipedia, you cannot find 'Washington,_Arkansas' via an 'Arkansas' search, nor through the 'Arkansas' category or article. Thanks The Earl 11:59, 12 March 2008 (MDT)
- Is the proposal that we should use slashes and underscores in article titles? If so, I disagree. We shouldn't use characters that are unintuitive to users because it will break Exact Match searching. Ritcheymt 10:34, 12 March 2008 (MDT)
- Spaces are automagically converted to underscores in wiki links already. I think the search knows how to handle them. Do you have a different character / structure that would work in place of the slash? The Earl 07:41, 10 March 2008 (MDT)
- Not to say that Wikipedia is perfect, but I think it’s prudent to examine the model of another site that has some years of experience. Following Wikipedia’s naming conventions, a page for a town might be named either “Rockville, Montgomery County, Maryland” or “Rockville, Maryland.” I think this works well. To require or advise users to use slashes and underscores in titles is to ask them to do something which is quite unintuitive to them. Therefore, compliance will be low and either we’ll end up with a “standard” that never really becomes standard in practice, or we’ll need an army of people to come in and “move” or rename all the pages our users name without following the standard. So the result is that this “standard” either fails to enhance findability of articles or else it takes a gargantuan amount of work to maintain. I think that’s one reason Wikipedia doesn’t do things this way. Ritcheymt 00:30, 16 March 2008 (MDT)
- Is the proposal that we should follow an article naming convention that would result in an article name of, say, "US/Utah"? I'd disagree with that proposal because anybody doing a search on "US" would see this Utah article in search results. It would spam the search engine. If they were looking for Utah, they would use the term "utah" and if they were looking for United States, they'd use "united states." Ritcheymt 10:34, 12 March 2008 (MDT)
- Is US/Utah not relevant to 'US'? Where would you look for 'New York'? See my comments below on this. The Earl 07:41, 10 March 2008 (MDT)
- No, Utah content is not relevant to someone doing a search for U.S. content. Wikipedia handles disambiguation nicely without the use of slashes in titles. See my earlier comment about disambiguation pages. Ritcheymt 00:30, 16 March 2008 (MDT)
- Is the proposal that we should use acronyms as country codes in article titles? If so, I disagree because acronyms are intuitive only to the initiated, not the rank and file of users. Even the initiated can find acronyms confusing. For instance, most Americans find several state postal codes confusing even though this system has been in place for decades. Ritcheymt 10:34, 12 March 2008 (MDT)
- Agreed, but I can not think of a better solution. Hopefully the portal / navigation will help the uninitiated find what they need, while a good structure will help more experienced users navigate without walking the tree. The Earl 07:41, 10 March 2008 (MDT)
- When you say “navigate” what do you mean? I can imagine a naming convention helping users search, but don’t see how it would help navigate. Navigation in MediaWiki is normally accomplished through links or through categories. Ritcheymt 00:30, 16 March 2008 (MDT)
- If the proposal is that we should mention, cover, or link to pages about prominent families or families of interest from a place portal, this idea, while exciting, can also lead to big problems. Where does one draw the line regarding how many families are listed for a place? A list of "prominent families" can feel like a private club to those whose families are excluded; how does one define prominence and avoid conflict over who is excluded? A list of "families of interest" of a place could be scores of printed pages long, so how would one keep the pages a reasonable size, and how would these lists be kept from spamming the search engine? These concerns have caused us to place information about families and individuals outside the scope of this site. Information about families and individuals doesn't necessarily have to remain outside the site's scope forever, but to be included, the abovementioned issues need to be addressed first. Ritcheymt 10:34, 12 March 2008 (MDT)
- The word 'public' hides in that statement. The family information included above should be constrained to only the families you would find in an encyclopedia article on the place, ie 'public prominence'. Other families could be linked from the main article, but that would be subject to the policy above. I don't think that families add much to the portal, and would not include any there. The Earl 07:41, 10 March 2008 (MDT)
- 'Public' shows in the bottom description, but did not used to show at the top. I goofed. Thanks The Earl 08:16, 10 March 2008 (MDT)
- How do encyclopedias determine which families to include? And to the extent that this site will have pages on towns and counties which an encyclopedia will not have, how would you keep the community from creating millions of pages on families that are prominent in one-stoplight towns?
Also, could you explain the language about “public?” Ritcheymt 00:30, 16 March 2008 (MDT)
Ritcheymt 15:40, 9 March 2008 (MDT)
The confusion listed above of 'Washington County' is exactly what I hope to address with this structure. We need a way to differentiate places. Currently if you search for 'New York', or look at the New York category you get a list of ~400 articles. Since New York is a city, a state and a county, there is no indication as to which of these the articles above reference. In many cases, the articles mix information about NY County and NY City, since these two places are very close to the same. Some of the articles include information from all three New Yorks. Some of the articles include information on Brooklyn (Kings Co.), but you can only find this information with a keyword search, and the information is spread over a few pages. Already at this early stage, the NY information is getting hard to find, and confused about its identity.
- The portal for NYC should probably be called “New York, New York.” The one for the county should probably be called “New York County, New York.” Articles about both should be categorized under both the county and the city categories. Ritcheymt 00:30, 16 March 2008 (MDT)
Looking for a place called Washington gives us a whole new set of headaches. We end up with LOTS of Washington Couties, a good handful of cities, and even two 'states'. Things get even more interesting if you look up names that the US repeated from overseas.
So if we are going to differentiate between 'Washington Co. Utah', and Washington DC, and Washington Co. elsewhere, we need to name them differently. If we have to put the differentiating information in the name of the page, then why not US/WashingtonDC, US/Washington, US/Utah/Washington, etc? Can you come up with a system that is more intuitive, and prettier? Please do!
I do not think that my solution is perfect, so feel free to poke holes in it. I posted this proposal because I think we need a structure, and we need to agree on one before someone (like me) goes off spamming the wiki.
My hope is that with a good structure, the templates will write the pages for us, and we will just have to fill in the relevant information. I hope that we can do this early with a few page moves, rather than later when we would have to hack and slash to get things into a framework. The Earl 07:41, 10 March 2008 (MDT)
I thought it might be wise to have a 'drill-down' structure.
Example: United States,Utah, Davis
For large cities, add the city after the county name, e. g. Bountiful would follow Davis in the example above. That would take care of the problem of multiple links and would allow users to simply drill down into the content they were looking for. Does that sound doable? JamesAnderson 14:04, 12 March 2008 (MDT)
The layout did not work like it should have on the listing of the levels I was talking about.
United States, Utah, Davis
Or United States, Utah, Davis, Bountiful if the cities level is used for a county.
JamesAnderson 14:08, 12 March 2008 (MDT)
I don't understand your 'Layout didn't work' comment, but I agree with your ideas. I think a better order would be opposite the way you propose. I think I need to back up a bit and explain some of the driving forces behind why my suggestions are as they are. Keep tuned, I hope to get a tight framework built out here. Thanks The Earl 12:46, 13 March 2008 (MDT)
- This page was last modified on 2 January 2010, at 20:59.
- This page has been accessed 1,070 times.
New to the Research Wiki?
In the FamilySearch Research Wiki, you can learn how to do genealogical research or share your knowledge with others.Learn More