It doesn't matter how many fields you have in your locations.  Sorting right to 
left puts the largest entity first, whatever that may be.

I believe that your location examples below somehow got messed up in your 
message.  You have multiple occurrences of Michigan and United States in your 
locations.

Sorting what I believe you have below from right to left would be as follows:

England, London, 195 Sunset Blvd., Roosevelt Cemetery
United States, Michigan, Detroit
United States, Michigan, Wayne County, Detroit
United States, Michigan, Wayne County, Detroit, 123 Apple Street

I don't know why you would have Detroit listed twice, once with Wayne County 
and once without it.

But sorting this way, all of the locations in Detroit, Wayne County, Michigan, 
United States (with or without street numbers and names, cemetery names, or 
anything else) will appear together in the Location List.

It's really a very easy concept.  Try it!  You might like it!  You can always 
change it back if you don't like it.  Keep in mind, this sorting is just for 
the display of the Master Location List, not how the locations are displayed in 
context.

Mary

-----Original Message-----
From: Jerry [mailto:jerrysemailgro...@gmail.com]
Sent: Sunday, March 11, 2012 5:57 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] How to document Locations in Europe 5 Fields vs 4 Fields

I'm trying to understand that thinking, Mary.  But how could that work if, for 
example, you had the following?

Detroit, Michigan, United States
Detroit, Wayne County, Michigan, United States Michigan, United States
123 Apple Street, Detroit, Wayne County, Michigan, United States Wayne County, 
Michigan, United States Roosevelt Cemetery, 195 Sunset Blvd, London, England

You would be ok with United States and England as COUNTRIES, but then moving 
left, it looks like you would have dissimilar entities together like:

SECOND DIVISION FROM RIGHT:
Michigan
Michigan
Michigan
Michigan
Michigan
London

THIRD DIVISION FROM RIGHT:
Detroit
Wayne County
(blank)
Wayne County
Wayne County
195 Sunset Blvd

FOURTH DIVISION FROM RIGHT:
(blank)
Detroit
(blank)
Detroit
Roosevelt Cemetery

FIFTH DIVISION FROM RIGHT:
(blank)
(blank)
(blank)
123 Apple Street
(blank)

So, what part of this am I not understanding, if so?

Thanks,
Jerry Boor - http://www.MerriamFamilyTree.org

On 03/11/2012 11:56 AM, M. Brenzel wrote:
> If you sort your location list right to left, they will sort properly,
> even with different numbers of fields.
>
> Mary
>
> *From:*John Magyari [mailto:jmagy...@gmail.com]
> *Sent:* Sunday, March 11, 2012 8:08 AM
> *To:* LegacyUserGroup@LegacyUsers.com
> *Subject:* Re: [LegacyUG] How to document Locations in Europe 5 Fields
> vs 4 Fields
>
> Thanks for everyone's ideas.
> Some of my Polish time periods use 4 some 5 positions
>
> I decided to force all 5 location positions into 4. Having same
> number of fields helps with sorting.
>
> Ideally if would be nice to specify Number of locations field MAX.Â
> Then if entered with less fields specify which fields to become null.
> ie. MaxPositions = 5, LessPositionOrder if less 2,3if less than MAX
> ie For Me for Poland city, administration, county, state, country
> (1,2,3,4,5) If less fields entered enter Nulls city, county, state,
> country (Null 1 field - admin) city, state, country (Null other 2
> fields -admin, county) city, state (Null other 3 fields) state (Null
> other 4 fields)
>
>
> I will use 4 fields, and in the process converted all locations with
> fewer positions to 4 position system.
>
> john
>
>
>
>
>
>
>
> On 3/11/2012 4:04 AM, Ron Ferguson wrote:
>
> John,
>
> Â
>
> By all means use the American four field standard for American
> locations, but for other countries use their own formats, normally the
> way in which they are written.
>
> Â
>
> Ron Ferguson
>
> http://www.fergys.co.uk/
>
> Â
>
> Â
>
> *From:*John Magyari <mailto:jmagy...@gmail.com>
>
> *Sent:*Thursday, March 08, 2012 7:35 PM
>
> *To:*LegacyUserGroup@LegacyUsers.com
> <mailto:LegacyUserGroup@LegacyUsers.com>
>
> *Subject:*[LegacyUG] How to document Locations in Europe 5 Fields vs 4
> Fields
>
> Â
>
> Typically for US locations i have ****4 FIELDS City, County, State,
> Country
>
> How do others handle European Countries?
>
> For example I have a village in Poland Area
>
> 1900's part of Austria Hungary
>
> Village, District, Province, Country ****4 FIELDS Lipowiec, Sanok
> District, Galicia Province, Austria-Hungary
>
> Same place in 1940's ****4 FIELDS
> Lipowiec, Sanok District, Krosno Voivodeship, Poland
>
> Almost all places in Current Day Poland 1950's through today *****5
> FIELDS City, Gmina, County, Voivodeship, COUNTRY Lipowiec, Dukla
> Gmina, Krosno County <wlmailhtml://wiki/Krosno_County>,
> Subcarpathian Voivodeship
> <wlmailhtml://wiki/Subcarpathian_Voivodeship>,
> Poland
>
> and since 2012 *****5 Fields
> Lipowiec, Jasliska Gmina, Krosno County
> <wlmailhtml://wiki/Krosno_County>, Subcarpathian Voivodeship
> <wlmailhtml://wiki/Subcarpathian_Voivodeship>, Poland
>
> When some locations ideally be 5 FIELDS, do you go back and update
> those with 4 Fields?
>
> With some having 4 some having 5 it's also harder sorting and then
> viewing similar towns over time periods.
>
> thanks,
> john magyari
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree)
> and on our blog (http://news.LegacyFamilyTree.com).
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree)
> and on our blog (http://news.LegacyFamilyTree.com).
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>
>
> Legacy User Group guidelines:
> http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages after Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
> Archived messages from old mail server - before Nov. 21 2009:
> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree)
> and on our blog (http://news.LegacyFamilyTree.com).
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp





Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp


Reply via email to