Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
You're welcome, John! Glad it works for you.
At one time, I had been putting the hospital (births) or church (marriages) or
cemetery (burials) in the Address table. However, if you select to print
addresses, the whole address is included, which is extremely redundant in the
book reports. (I may have submitted a suggestion on that, but it was so long
ago, I don't remember.) Then I started putting the hospital, church or
cemetery in as part of the location--which looks great, but ruffles feathers
here. ;) So, if you looked at my database, it is currently a hodge-podge!
One day I will get it cleaned up--isn't that always our plan? ha!
--Paula
From: johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au
To: legacyusergroup@LegacyUsers.com
Sent: Friday, August 1, 2014 8:08 PM
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
Wow, thank you Paula! I
have rediscovered the Address field! I had completely forgotten about it as I
only ever used it a few times, a number of years ago, but did not find it useful
for my purposes. I did not even realise Address could be displayed in book
reports or Family Group Records. As you suggested, I played around with it and
think I can use it to meet my needs- to comment on locations, rather than adding
locations in the Address field. It
does not display in the Family View but I think I can live with
that.
I use another database for
addresses of living cousins, and it is very rare to get an address of ancestors
from hamlets or villages in Europe. Occasionally I get something like “house
18”. Therefore the Address field is freely available for other uses.
I agree with Paula-
software such as Legacy is to be used however one wants or needs. Legacy is very
flexible but all programs have limitations so users may need to “think outside
the box”.
John
From: Paula Ryburn
Sent: Saturday, August 02, 2014 5:24 AM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and
Family Group Records ?
I know there are those on this list who will shoot down this idea
quickly and vehemently, but...
Have
you thought of using the Address field?
I
used to do this to indicate probably or add on the farm... that was awhile
ago, so my memory is fuzzy.
I
have seen many, many threads here discussing the use of locations and
addresses so I won't go into details (you can search the archives) don't
need to hear both sides again. ;)
I'm
not sure it would work for John's Poland/Russia examples, but maybe for Ron's
Salt Lake City examples? Especially if there is a known city used in most
cases you just have a few cases of near to indicate...?
You
would need to try it on a field or two run some reports to see if you like
the format.
This
approach would probably not work for someone who uses the Address table for
addresses. ;) ...or maybe it would?
Legacy
is flexible; I'm just offering up another table/place to be flexible.
--Paula
From: johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au
To: legacyusergroup@LegacyUsers.com
Sent: Wednesday, July 30, 2014
10:43 PM
Subject: Re:
[LegacyUG] Prepositions for locations- Family View and Family Group Records
?
Hi Ron,
I have been doing something
similar to you but I am trying to minimise the number variations of the same
location in the Master Location List e.g.
Sitaniec, Zamość, Crown
Province of Galicia, Habsburg Empire
Sitaniec, Zamość, Lublin,
Duchy of Warsaw
Sitaniec, Zamość, Lublin,
Kingdom of Poland ('Russian Poland')
Sitaniec, Zamość, Lublin,
Republic of Poland
of Sitaniec, Zamość,
Lublin, Kingdom of Poland ('Russian Poland')
of Sitaniec, Zamość,
Lublin, Republic of Poland
I am trying to make my
family history story very readable and presented elegantly without sacrificing
accuracy or details, so I am conscious that my Location Index may be confusing
for readers, especially with modifiers.
I think what I would need
is another field, where you add Individuals’ Information to the Family View (and
Family Group Reports). This could be an optional drop down field (probably
placed below “Christened”) and where you could add your own element e.g.
“Earliest Known Residence” or whatever individual Legacy users may want. I
realize such information could be added as an Event or in notes, but it would
much more convenient for me while researching, or for readers of my family
history, to immediately see accurate details about each
person without having to dig for it.
John
From: Ron Taylor
Sent: Wednesday, July 30, 2014 11:33 PM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and
Family Group Records ?
John,
If
you add the modifiers to the Master Location List and link your individual
records to those modified locations, they should show in the reports and
elsewhere. Look at the examples I gave of Salt Lake City. Those
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
I know there are those on this list who will shoot down this idea quickly and
vehemently, but...
Have you thought of using the Address field?
I used to do this to indicate probably or add on the farm... that was
awhile ago, so my memory is fuzzy.
I have seen many, many threads here discussing the use of locations and
addresses so I won't go into details (you can search the archives) don't
need to hear both sides again. ;)
I'm not sure it would work for John's Poland/Russia examples, but maybe for
Ron's Salt Lake City examples? Especially if there is a known city used in
most cases you just have a few cases of near to indicate...?
You would need to try it on a field or two run some reports to see if you
like the format.
This approach would probably not work for someone who uses the Address table
for addresses. ;) ...or maybe it would?
Legacy is flexible; I'm just offering up another table/place to be flexible.
--Paula
From: johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au
To: legacyusergroup@LegacyUsers.com
Sent: Wednesday, July 30, 2014 10:43 PM
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
Hi Ron,
I have been doing something
similar to you but I am trying to minimise the number variations of the same
location in the Master Location List e.g.
Sitaniec, Zamość, Crown
Province of Galicia, Habsburg Empire
Sitaniec, Zamość, Lublin,
Duchy of Warsaw
Sitaniec, Zamość, Lublin,
Kingdom of Poland ('Russian Poland')
Sitaniec, Zamość, Lublin,
Republic of Poland
of Sitaniec, Zamość,
Lublin, Kingdom of Poland ('Russian Poland')
of Sitaniec, Zamość,
Lublin, Republic of Poland
I am trying to make my
family history story very readable and presented elegantly without sacrificing
accuracy or details, so I am conscious that my Location Index may be confusing
for readers, especially with modifiers.
I think what I would need
is another field, where you add Individuals’ Information to the Family View (and
Family Group Reports). This could be an optional drop down field (probably
placed below “Christened”) and where you could add your own element e.g.
“Earliest Known Residence” or whatever individual Legacy users may want. I
realize such information could be added as an Event or in notes, but it would
much more convenient for me while researching, or for readers of my family
history, to immediately see
accurate details about each person without having to dig for it.
John
From: Ron Taylor
Sent: Wednesday, July 30, 2014 11:33 PM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and
Family Group Records ?
John,
If
you add the modifiers to the Master Location List and link your individual
records to those modified locations, they should show in the reports and
elsewhere. Look at the examples I gave of Salt Lake City. Those are
actual entries in my Master Locations List.
Ron
Taylor
On Wednesday, July 30, 2014 4:30 AM,
johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au
wrote:
It seems that adding prepositions or modifiers at the
end of locations and adding them as new entries to the Master Location List is
the best I can do for my database purposes, at least for now. I eventually want
to include a number of Family Group Records as ‘Family Story’ chapters in a
book. I will have to convert them to a word document, and then add the
prepositions or modifiers before publishing it.
From: Ron Taylor
Sent: Wednesday, July 30, 2014 12:22 AM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and
Family Group Records ?
There is a field in the tblLR (Master Locations Table) called
Preposition which can be set and used in reports as you described. There
is also a file C:\...Documents\Legacy Family
Tree\_AppData\Misc\Preposition_English.lst which is used by the Master Locations
List to sort locations. It does it by removing the words in that file from
the location, putting it on the end of the location name, then sorting the list
so that all locations that are the same will display next to each other and the
preposition tacked onto the end. That is helpful. Some of the
entries in that list are not actually prepositions. In fact, some of
the entries are multiple words. I think a better term for them would be
location modifiers instead of prepositions.
What
would be great but would require some extensive re-writing would be to have an
actual database table of location modifiers. That table could come into
play as a pull down list (similar to Child Status, Event Type, Surname List,
etc.) where you can select the location modifier to be applied to a specific
location field. That would mean that a location modifier key field be
inserted into every table where a link to the tblLR is used. The
preposition field that is in tblLR would only be used for reports when the
location modifier is blank. The main effect
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
Wow, thank you Paula! I have rediscovered the Address field! I had completely
forgotten about it as I only ever used it a few times, a number of years ago,
but did not find it useful for my purposes. I did not even realise Address
could be displayed in book reports or Family Group Records. As you suggested, I
played around with it and think I can use it to meet my needs- to comment on
locations, rather than adding locations in the Address field. It does not
display in the Family View but I think I can live with that.
I use another database for addresses of living cousins, and it is very rare to
get an address of ancestors from hamlets or villages in Europe. Occasionally I
get something like “house 18”. Therefore the Address field is freely available
for other uses.
I agree with Paula- software such as Legacy is to be used however one wants or
needs. Legacy is very flexible but all programs have limitations so users may
need to “think outside the box”.
John
From: Paula Ryburn
Sent: Saturday, August 02, 2014 5:24 AM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
I know there are those on this list who will shoot down this idea quickly and
vehemently, but...
Have you thought of using the Address field?
I used to do this to indicate probably or add on the farm... that was
awhile ago, so my memory is fuzzy.
I have seen many, many threads here discussing the use of locations and
addresses so I won't go into details (you can search the archives) don't
need to hear both sides again. ;)
I'm not sure it would work for John's Poland/Russia examples, but maybe for
Ron's Salt Lake City examples? Especially if there is a known city used in
most cases you just have a few cases of near to indicate...?
You would need to try it on a field or two run some reports to see if you
like the format.
This approach would probably not work for someone who uses the Address table
for addresses. ;) ...or maybe it would?
Legacy is flexible; I'm just offering up another table/place to be flexible.
--Paula
From: johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au
To: legacyusergroup@LegacyUsers.com
Sent: Wednesday, July 30, 2014 10:43 PM
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
Hi Ron,
I have been doing something similar to you but I am trying to minimise the
number variations of the same location in the Master Location List e.g.
Sitaniec, Zamość, Crown Province of Galicia, Habsburg Empire
Sitaniec, Zamość, Lublin, Duchy of Warsaw
Sitaniec, Zamość, Lublin, Kingdom of Poland ('Russian Poland')
Sitaniec, Zamość, Lublin, Republic of Poland
of Sitaniec, Zamość, Lublin, Kingdom of Poland ('Russian Poland')
of Sitaniec, Zamość, Lublin, Republic of Poland
I am trying to make my family history story very readable and presented
elegantly without sacrificing accuracy or details, so I am conscious that my
Location Index may be confusing for readers, especially with modifiers.
I think what I would need is another field, where you add Individuals’
Information to the Family View (and Family Group Reports). This could be an
optional drop down field (probably placed below “Christened”) and where you
could add your own element e.g. “Earliest Known Residence” or whatever
individual Legacy users may want. I realize such information could be added as
an Event or in notes, but it would much more convenient for me while
researching, or for readers of my family history, to immediately see accurate
details about each person without having to dig for it.
John
From: Ron Taylor
Sent: Wednesday, July 30, 2014 11:33 PM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
John,
If you add the modifiers to the Master Location List and link your individual
records to those modified locations, they should show in the reports and
elsewhere. Look at the examples I gave of Salt Lake City. Those are actual
entries in my Master Locations List.
Ron Taylor
On Wednesday, July 30, 2014 4:30 AM, johnbernac...@iprimus.com.au
johnbernac...@iprimus.com.au wrote:
It seems that adding prepositions or modifiers at the end of locations and
adding them as new entries to the Master Location List is the best I can do for
my database purposes, at least for now. I eventually want to include a number
of Family Group Records as ‘Family Story’ chapters in a book. I will have to
convert them to a word document, and then add the prepositions or modifiers
before publishing it.
From: Ron Taylor
Sent: Wednesday, July 30, 2014 12:22 AM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
There is a field in the tblLR (Master Locations Table) called Preposition which
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
It seems that adding prepositions or modifiers at the end of locations and adding them as new entries to the Master Location List is the best I can do for my database purposes, at least for now. I eventually want to include a number of Family Group Records as ‘Family Story’ chapters in a book. I will have to convert them to a word document, and then add the prepositions or modifiers before publishing it. From: Ron Taylor Sent: Wednesday, July 30, 2014 12:22 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ? There is a field in the tblLR (Master Locations Table) called Preposition which can be set and used in reports as you described. There is also a file C:\...Documents\Legacy Family Tree\_AppData\Misc\Preposition_English.lst which is used by the Master Locations List to sort locations. It does it by removing the words in that file from the location, putting it on the end of the location name, then sorting the list so that all locations that are the same will display next to each other and the preposition tacked onto the end. That is helpful. Some of the entries in that list are not actually prepositions. In fact, some of the entries are multiple words. I think a better term for them would be location modifiers instead of prepositions. What would be great but would require some extensive re-writing would be to have an actual database table of location modifiers. That table could come into play as a pull down list (similar to Child Status, Event Type, Surname List, etc.) where you can select the location modifier to be applied to a specific location field. That would mean that a location modifier key field be inserted into every table where a link to the tblLR is used. The preposition field that is in tblLR would only be used for reports when the location modifier is blank. The main effect that a location modifier table would have is eliminating multiple instances of the same location name as the current method allows. Here is an example of a location in the current Master Location List that has multiple entries because of prepositions: Salt Lake City, Salt Lake, Utah Salt Lake City, Salt Lake, Utah, from Salt Lake City, Salt Lake, Utah, near Salt Lake City, Salt Lake, Utah, of Salt Lake City, Salt Lake, Utah, of Salt Lake City, Salt Lake, Utah, probably Salt Lake City, Salt Lake, Utah The above display is achieved by checking the two boxes at the bottom of Sort Location List called Remove common prepositions from locations and Remove leading bracket from bracketed locations and then executing the sort. Notice that the words found in the text file Preposition_English.lst were re-positioned to the end of the location before the sort. Likewise, the bracketed locations had the leading bracket removed before the sort but the trailing bracket was retained so it would display. In either case, you can click Edit to see the actual long or short location with the preposition words where they really are stored in the field. Also, note that I added probably to the Preposition_English.lst file (as well as a few other words) so that it would treated like other prepositions. If there was only one instance of Salt Lake City, Salt Lake, Utah in the Master Locations Table, as well as all other locations, then it would be much easier to manage and maintain. The only thing that would be needed then is a time sensitive lookup for location. Or even better, a conversion of any current location to its time sensitive name. Ron Taylor On Tuesday, July 29, 2014 1:32 AM, johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au wrote: Sometimes I know where ancestors lived but uncertain if they were born in that place. There is an option which allows you to change the location preposition from ‘in’ to something else but it only works for the book reports from the publishing centre. I could mention in the narrative that a person’s place of birth is not certain, but I would like to request suggestions from other Legacy users for a way use a preposition or some other way to easily show that a person was from or lived in a location, which was not necessarily their place of birth. I would like this for the Family View and Family Group Records. Do others find this a problem or am I too neurotic about accuracy or details? John 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
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
John, If you add the modifiers to the Master Location List and link your individual records to those modified locations, they should show in the reports and elsewhere. Look at the examples I gave of Salt Lake City. Those are actual entries in my Master Locations List. Ron Taylor On Wednesday, July 30, 2014 4:30 AM, johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au wrote: It seems that adding prepositions or modifiers at the end of locations and adding them as new entries to the Master Location List is the best I can do for my database purposes, at least for now. I eventually want to include a number of Family Group Records as ‘Family Story’ chapters in a book. I will have to convert them to a word document, and then add the prepositions or modifiers before publishing it. From: Ron Taylor Sent: Wednesday, July 30, 2014 12:22 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ? There is a field in the tblLR (Master Locations Table) called Preposition which can be set and used in reports as you described. There is also a file C:\...Documents\Legacy Family Tree\_AppData\Misc\Preposition_English.lst which is used by the Master Locations List to sort locations. It does it by removing the words in that file from the location, putting it on the end of the location name, then sorting the list so that all locations that are the same will display next to each other and the preposition tacked onto the end. That is helpful. Some of the entries in that list are not actually prepositions. In fact, some of the entries are multiple words. I think a better term for them would be location modifiers instead of prepositions. What would be great but would require some extensive re-writing would be to have an actual database table of location modifiers. That table could come into play as a pull down list (similar to Child Status, Event Type, Surname List, etc.) where you can select the location modifier to be applied to a specific location field. That would mean that a location modifier key field be inserted into every table where a link to the tblLR is used. The preposition field that is in tblLR would only be used for reports when the location modifier is blank. The main effect that a location modifier table would have is eliminating multiple instances of the same location name as the current method allows. Here is an example of a location in the current Master Location List that has multiple entries because of prepositions: Salt Lake City, Salt Lake, Utah Salt Lake City, Salt Lake, Utah, from Salt Lake City, Salt Lake, Utah, near Salt Lake City, Salt Lake, Utah, of Salt Lake City, Salt Lake, Utah, of Salt Lake City, Salt Lake, Utah, probably Salt Lake City, Salt Lake, Utah The above display is achieved by checking the two boxes at the bottom of Sort Location List called Remove common prepositions from locations and Remove leading bracket from bracketed locations and then executing the sort. Notice that the words found in the text file Preposition_English.lst were re-positioned to the end of the location before the sort. Likewise, the bracketed locations had the leading bracket removed before the sort but the trailing bracket was retained so it would display. In either case, you can click Edit to see the actual long or short location with the preposition words where they really are stored in the field. Also, note that I added probably to the Preposition_English.lst file (as well as a few other words) so that it would treated like other prepositions. If there was only one instance of Salt Lake City, Salt Lake, Utah in the Master Locations Table, as well as all other locations, then it would be much easier to manage and maintain. The only thing that would be needed then is a time sensitive lookup for location. Or even better, a conversion of any current location to its time sensitive name. Ron Taylor On Tuesday, July 29, 2014 1:32 AM, johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au wrote: Sometimes I know where ancestors lived but uncertain if they were born in that place. There is an option which allows you to change the location preposition from ‘in’ to something else but it only works for the book reports from the publishing centre. I could mention in the narrative that a person’s place of birth is not certain, but I would like to request suggestions from other Legacy users for a way use a preposition or some other way to easily show that a person was from or lived in a location, which was not necessarily their place of birth. I would like this for the Family View and Family Group Records. Do others find this a problem or am I too neurotic about accuracy or details? John 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
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
Hi Ron,
I have been doing something similar to you but I am trying to minimise the
number variations of the same location in the Master Location List e.g.
Sitaniec, Zamość, Crown Province of Galicia, Habsburg Empire
Sitaniec, Zamość, Lublin, Duchy of Warsaw
Sitaniec, Zamość, Lublin, Kingdom of Poland ('Russian Poland')
Sitaniec, Zamość, Lublin, Republic of Poland
of Sitaniec, Zamość, Lublin, Kingdom of Poland ('Russian Poland')
of Sitaniec, Zamość, Lublin, Republic of Poland
I am trying to make my family history story very readable and presented
elegantly without sacrificing accuracy or details, so I am conscious that my
Location Index may be confusing for readers, especially with modifiers.
I think what I would need is another field, where you add Individuals’
Information to the Family View (and Family Group Reports). This could be an
optional drop down field (probably placed below “Christened”) and where you
could add your own element e.g. “Earliest Known Residence” or whatever
individual Legacy users may want. I realize such information could be added as
an Event or in notes, but it would much more convenient for me while
researching, or for readers of my family history, to immediately see accurate
details about each person without having to dig for it.
John
From: Ron Taylor
Sent: Wednesday, July 30, 2014 11:33 PM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
John,
If you add the modifiers to the Master Location List and link your individual
records to those modified locations, they should show in the reports and
elsewhere. Look at the examples I gave of Salt Lake City. Those are actual
entries in my Master Locations List.
Ron Taylor
On Wednesday, July 30, 2014 4:30 AM, johnbernac...@iprimus.com.au
johnbernac...@iprimus.com.au wrote:
It seems that adding prepositions or modifiers at the end of locations and
adding them as new entries to the Master Location List is the best I can do for
my database purposes, at least for now. I eventually want to include a number
of Family Group Records as ‘Family Story’ chapters in a book. I will have to
convert them to a word document, and then add the prepositions or modifiers
before publishing it.
From: Ron Taylor
Sent: Wednesday, July 30, 2014 12:22 AM
To: legacyusergroup@LegacyUsers.com
Subject: Re: [LegacyUG] Prepositions for locations- Family View and Family
Group Records ?
There is a field in the tblLR (Master Locations Table) called Preposition which
can be set and used in reports as you described. There is also a file
C:\...Documents\Legacy Family Tree\_AppData\Misc\Preposition_English.lst which
is used by the Master Locations List to sort locations. It does it by removing
the words in that file from the location, putting it on the end of the location
name, then sorting the list so that all locations that are the same will
display next to each other and the preposition tacked onto the end. That is
helpful. Some of the entries in that list are not actually prepositions. In
fact, some of the entries are multiple words. I think a better term for them
would be location modifiers instead of prepositions.
What would be great but would require some extensive re-writing would be to
have an actual database table of location modifiers. That table could come
into play as a pull down list (similar to Child Status, Event Type, Surname
List, etc.) where you can select the location modifier to be applied to a
specific location field. That would mean that a location modifier key field be
inserted into every table where a link to the tblLR is used. The preposition
field that is in tblLR would only be used for reports when the location
modifier is blank. The main effect that a location modifier table would have
is eliminating multiple instances of the same location name as the current
method allows. Here is an example of a location in the current Master Location
List that has multiple entries because of prepositions:
Salt Lake City, Salt Lake, Utah
Salt Lake City, Salt Lake, Utah, from
Salt Lake City, Salt Lake, Utah, near
Salt Lake City, Salt Lake, Utah, of
Salt Lake City, Salt Lake, Utah, of
Salt Lake City, Salt Lake, Utah, probably
Salt Lake City, Salt Lake, Utah
The above display is achieved by checking the two boxes at the bottom of Sort
Location List called Remove common prepositions from locations and Remove
leading bracket from bracketed locations and then executing the sort.
Notice that the words found in the text file Preposition_English.lst were
re-positioned to the end of the location before the sort. Likewise, the
bracketed locations had the leading bracket removed before the sort but the
trailing bracket was retained so it would display. In either case, you can
click Edit to see the actual long or short location with the preposition
words where they really are stored in the field.
Also, note
[LegacyUG] Prepositions for locations- Family View and Family Group Records ?
Sometimes I know where ancestors lived but uncertain if they were born in that place. There is an option which allows you to change the location preposition from ‘in’ to something else but it only works for the book reports from the publishing centre. I could mention in the narrative that a person’s place of birth is not certain, but I would like to request suggestions from other Legacy users for a way use a preposition or some other way to easily show that a person was from or lived in a location, which was not necessarily their place of birth. I would like this for the Family View and Family Group Records. Do others find this a problem or am I too neurotic about accuracy or details? John 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
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
There is a field in the tblLR (Master Locations Table) called Preposition which can be set and used in reports as you described. There is also a file C:\...Documents\Legacy Family Tree\_AppData\Misc\Preposition_English.lst which is used by the Master Locations List to sort locations. It does it by removing the words in that file from the location, putting it on the end of the location name, then sorting the list so that all locations that are the same will display next to each other and the preposition tacked onto the end. That is helpful. Some of the entries in that list are not actually prepositions. In fact, some of the entries are multiple words. I think a better term for them would be location modifiers instead of prepositions. What would be great but would require some extensive re-writing would be to have an actual database table of location modifiers. That table could come into play as a pull down list (similar to Child Status, Event Type, Surname List, etc.) where you can select the location modifier to be applied to a specific location field. That would mean that a location modifier key field be inserted into every table where a link to the tblLR is used. The preposition field that is in tblLR would only be used for reports when the location modifier is blank. The main effect that a location modifier table would have is eliminating multiple instances of the same location name as the current method allows. Here is an example of a location in the current Master Location List that has multiple entries because of prepositions: Salt Lake City, Salt Lake, Utah Salt Lake City, Salt Lake, Utah, from Salt Lake City, Salt Lake, Utah, near Salt Lake City, Salt Lake, Utah, of Salt Lake City, Salt Lake, Utah, of Salt Lake City, Salt Lake, Utah, probably Salt Lake City, Salt Lake, Utah The above display is achieved by checking the two boxes at the bottom of Sort Location List called Remove common prepositions from locations and Remove leading bracket from bracketed locations and then executing the sort. Notice that the words found in the text file Preposition_English.lst were re-positioned to the end of the location before the sort. Likewise, the bracketed locations had the leading bracket removed before the sort but the trailing bracket was retained so it would display. In either case, you can click Edit to see the actual long or short location with the preposition words where they really are stored in the field. Also, note that I added probably to the Preposition_English.lst file (as well as a few other words) so that it would treated like other prepositions. If there was only one instance of Salt Lake City, Salt Lake, Utah in the Master Locations Table, as well as all other locations, then it would be much easier to manage and maintain. The only thing that would be needed then is a time sensitive lookup for location. Or even better, a conversion of any current location to its time sensitive name. Ron Taylor On Tuesday, July 29, 2014 1:32 AM, johnbernac...@iprimus.com.au johnbernac...@iprimus.com.au wrote: Sometimes I know where ancestors lived but uncertain if they were born in that place. There is an option which allows you to change the location preposition from ‘in’ to something else but it only works for the book reports from the publishing centre. I could mention in the narrative that a person’s place of birth is not certain, but I would like to request suggestions from other Legacy users for a way use a preposition or some other way to easily show that a person was from or lived in a location, which was not necessarily their place of birth. I would like this for the Family View and Family Group Records. Do others find this a problem or am I too neurotic about accuracy or details? John 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
Re: [LegacyUG] Prepositions for locations- Family View and Family Group Records ?
johnbernac...@iprimus.com.au wrote: Sometimes I know where ancestors lived but uncertain if they were born in that place. There is an option which allows you to change the location preposition from ‘in’ to something else but it only works for the book reports from the publishing centre. I could mention in the narrative that a person’s place of birth is not certain, but I would like to request suggestions from other Legacy users for a way use a preposition or some other way to easily show that a person was from or lived in a location, which was not necessarily their place of birth. I would like this for the Family View and Family Group Records. Do others find this a problem or am I too neurotic about accuracy or details? Neurotic may be a /bit/ over the top. ;) The thing with changing the prep. is, it'll be just as imprecise because of the readers' varying understandings of in, near, at, from, et al. I recall being dressed down for using near back in the dawn of comp-gen; I was told everything happens IN a place; if it's _near_ place A then it's _in_ place B. True enough on a philosophical or geographical level, but people get into the act down at reality-level, as in: No one wants to read a place that goes probably near Rio, Capon District, Hampshire County, then Frederick County, (West) Virginia Hard to sort, y'know? So I tend to stick with record the place as it was at the time of the event and everything else goes into notes somewhere, which turns that place into Frederick County, Virginia which also eludes the issue of, was it Capon District while it was in Frederick Co.? (OTOH, most folks appear to be unencumbered by places that subdivided as often as a lazy amoeba.) Cheryl 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
