[LegacyUG] Hashtag assignment - generates a temporary Unknown spouse

[Ian Thomas]

I have just begun using hashtags, and it should be useful. Currently, I am 
going to the Treelist,  refreshing the list,  and using the "Add a hashtag to 
the entire tree" - bottom option (button).
That seems to be a rapid and easily-understood way to assign hashtags 
accurately and quickly, and to keep the number to a minimum initially (until I 
know what works best for me).

When I do this, then select the tree, view in Descendant view, and perhaps 
scroll up to earlier ancestors in that tree (the earliest are seldom the "main 
identity" of the trees that have been determined), in some cases I see  a 
spouse (Unknown),  who may have a birth and/or death date - which seems to 
reflect those of a supposed spouse- in the row above.

This sounds complicated but is quite a simple operation. I suspect it is a 
harmless bug.

If I select the Unknown, my display reverts to my starting couple (forget the 
proper term), and the Unknown isn't seen again. If I select another individual 
(row), that individual is displayed and the Unknown artefact disappears.

I suspect it is something to do with indexing.

Another bug that has persisted for months, is that I find that one or more 
recently-added individuals cannot be located in the Index view until I enter 
their given names (or their surnames - it varies); after a few tries, I can 
find the individual.
Again, I think it is an related to indexing - not a problem, since it 
self-corrects after a time. I don't bother with any sort of File Maintenance 
until I'm ready to close Legacy Family Tree (9, Deluxe, latest update always) 
and do the usual backup.

Perhaps these are both related to disk caching - I do find that (outside of 
Legacy), File Explorer operations on my multi-disk system often require an F5 
refresh.

Ian Thomas
Albert Park, Victoria 3206 Australia

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Location standards

[Debbie Jorgenson]

Susan is correct. Thanks for clarifying this.

On Mon, Feb 4, 2019 at 2:37 PM Susan Swindell  wrote:

> Debbie, I'm in DAR, and always used commas when entering locations in the
> applications. Is the "no commas" something new?
>
> On applications submitted to NSDAR the rule was established about 3 or 4
> years ago.  But since you retype everything onto the application it doesn't
> affect how you enter things into Legacy.
>
> --
> Susan
> swind...@value.net
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe
> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
-- 
Debbie Jorgenson
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Location standards

[Susan Swindell]

Debbie, I'm in DAR, and always used commas when entering locations in the 
applications. Is the "no commas" something new? 

On applications submitted to NSDAR the rule was established about 3 or 4 years 
ago. But since you retype everything onto the application it doesn't affect how 
you enter things into Legacy. 
-- 
Susan 
swind...@value.net 
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Location standards

[Sherry H]

Rules depend on whether or not you're planning on joining a lineage society
or uploading your data to FamilySearch. Otherwise, just be consistent for
your own sanity .

FamilySearch has specific requirements at
https://www.familysearch.org/wiki/en/Begin_Your_Genealogy_Quest#Recording_Locations
Recording Locations

   - *To record a location, start from the smallest entity to the largest*
   such as city, county, state, country.


   - For a person born in the USA, an example would be:*Chicago, Cook,
   Illinois, United States*.
   - If a person was not born in a city and you know the county, you might
   record just the county and state: *Cook, Illinois, United States*.
   - If you only know the state, you will record: *Illinois, United States*.

   - If you only know the country you will record: "United States".
   - In other parts of the world, locations may be: City, Province,
   Country. For example: *Chester, Cheshire, England* or *Acapulco,
   Guerrero, Mexico*.

[image: Html7.jpg] 

   - As you type in the location, you will see a menu to select your
   location. This feature is to keep locations in a standard format to
   facilitate matches with similar names with the same associated locations.


   - *Record the location as shown on the earliest record you have of the
   event*. Many times the place where a birth took place is in a different
   county or province today and in some cases even in a different country! For
   example, a person may have been born in a town which is in Poland today,
   but the town may have been part of the Kingdom of Prussia when the event
   took place. Boundary lines change over time in many parts of the United
   States as well as the rest of the world.



Debbie, I'm in DAR, and always used commas when entering locations in the
applications. Is the "no commas" something new?


Sherry




On Mon, Feb 4, 2019 at 10:54 AM Debbie Jorgenson 
wrote:

> I think it is a personal preference and whatever you decide, stick to it.
> I started out typing the word County as I had found in Iowa we have Des
> Moines (city) and Des Moines County, just as an example. Then I was told to
> never type the word County or the abbreviation Co. for county so I went in
> and deleted all the word "County", leaving my locations Des Moines, Polk,
> Iowa, United States. I have since learned that many in my Legacy User's
> Group use the word County in their location places.
>
> The Daughters of the American Revolution, on their applications for
> admittance, instruct applicants to list locations as: Des Moines Polk Co IA
> (no periods of commans and using the abbreviation Co for the word county).
>
> Debbie
>
> On Mon, Feb 4, 2019 at 6:36 AM Pete  wrote:
>
>> I am vacillating on the standardization of Irish Locations and asking for
>> comments/thoughts on using:
>> "County" or "Co." as a prefix to specifying the County portion of the
>> location.  I know the "Standard" using is "County".
>> Does it really make difference?  I want to make sure that all locations
>> are
>> consistant.
>> Pete
>>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Location standards

[Debbie Jorgenson]

I think it is a personal preference and whatever you decide, stick to it. I
started out typing the word County as I had found in Iowa we have Des
Moines (city) and Des Moines County, just as an example. Then I was told to
never type the word County or the abbreviation Co. for county so I went in
and deleted all the word "County", leaving my locations Des Moines, Polk,
Iowa, United States. I have since learned that many in my Legacy User's
Group use the word County in their location places.

The Daughters of the American Revolution, on their applications for
admittance, instruct applicants to list locations as: Des Moines Polk Co IA
(no periods of commans and using the abbreviation Co for the word county).

Debbie

On Mon, Feb 4, 2019 at 6:36 AM Pete  wrote:

> I am vacillating on the standardization of Irish Locations and asking for
> comments/thoughts on using:
> "County" or "Co." as a prefix to specifying the County portion of the
> location.  I know the "Standard" using is "County".
> Does it really make difference?  I want to make sure that all locations are
> consistant.
> Pete
>
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe
> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

[LegacyUG] Location standards

[Pete]

I am vacillating on the standardization of Irish Locations and asking for
comments/thoughts on using:
"County" or "Co." as a prefix to specifying the County portion of the
location.  I know the "Standard" using is "County".
Does it really make difference?  I want to make sure that all locations are
consistant.
Pete


<>-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/