{"id":305,"date":"2013-06-07T12:54:00","date_gmt":"2013-06-07T17:54:00","guid":{"rendered":"http:\/\/genealogy.julietarr.com\/blog\/my-legacy-family-tree-8-wish-list\/"},"modified":"2013-07-18T19:48:19","modified_gmt":"2013-07-19T00:48:19","slug":"my-legacy-family-tree-8-wish-list","status":"publish","type":"post","link":"https:\/\/genealogy.julietarr.com\/blog\/my-legacy-family-tree-8-wish-list\/","title":{"rendered":"My Legacy Family Tree 8 Wish List"},"content":{"rendered":"

\"Legacy<\/a>I\u2019ve been hearing rumors that a new version of Legacy Family Tree<\/a> will be released later this year.\u00a0 In fact, Geoff Rasmussen will be discussing it at SCGS Jamboree later today in a demo called \u201cWhat\u2019s New in Legacy Family Tree 8.\u201d\u00a0 (Boy, I wish that session was being streamed live!!).\u00a0 While I have no details, I do look forward to the Legacy 8 release.\u00a0 In the meantime, I thought I share a few of my \u201cwish list\u201d items.<\/p>\n

<\/p>\n

First, Legacy has been due for an upgrade for awhile now.\u00a0 Compared to many of the other popular programs, such as Roots Magic and Family Tree Maker, Legacy\u2019s user interface looks a little dated.\u00a0 Personally, I could care less.\u00a0 As long as it does what I need it to do and it\u2019s laid out in a manner that jives with my workflow,\u00a0 I don\u2019t really care about aesthetics.\u00a0 There are a few things I\u2019d like to remain the same, but there are also some things I\u2019d like to see changed improve functionality.\u00a0 Here\u2019s my wish list:<\/p>\n

Keep Some Things the Same!<\/strong><\/p>\n

Although I imagine there will be some cosmetic changes to the UI, I hope that they maintain the integrity of the program.\u00a0 For example, I hope they don\u2019t change anything structurally in the Family view (pictured below).<\/p>\n

\"Legacy<\/p>\n

Out of the other programs I have tried, Legacy\u2019s family view is the best, in my opinion.\u00a0 It\u2019s like having a family group sheet on your screen, and I certainly appreciate that visual.\u00a0 I also like that fact that you can customize what data is displayed for the focus couple, as well as how the children are displayed (I prefer the two-column view).\u00a0 This is also the only program (of those I\u2019ve tried) that displays the family in a top-down manner.\u00a0 The focus couple is in the middle, their parents above, and children below.\u00a0 Other programs seem to be going with the side-view, similar to a pedigree chart, and I have a hard time with that.<\/p>\n

Another thing I don\u2019t want to see changed is the data entry screen for an individual (pictured) below.\u00a0 I like that the vital stats are called out at the top, while all other events are displayed below.\u00a0 I also like the fact that you can change the sort order of the events to sort by date or name.<\/p>\n

\"Legacy<\/p>\n

Data Entry of Location<\/strong><\/p>\n

I really want to see the location field split into two fields that I can see<\/em>. In other words, I\u2019d like to see a field for the \u201cplace\u201d and the \u201clocation\u201d and see<\/em> both fields.<\/p>\n

For example, I want to be able to have a \u201cplace\u201d field in the burial information so I can enter the name of the cemetery, independent of the \u201clocation\u201d (i.e., city, county, state).\u00a0 This way, my master locations remain manageable and I have consistency with the name of the cemetery.<\/p>\n

I would also like this \u201cplace\u201d field to function just as the master locations, where you can add notes to the master \u201cplace\u201d such as address, directions, GPS coordinates, and\/or notes such as previous or other names of the location, and once it\u2019s set up, it can be reused as a master.<\/p>\n

Yes, I realize that there are some options currently available (see image below), but it\u2019s a buried (no pun intended) feature and I cannot tell by looking at the screen in what cemetery this person is buried in unless I make it a master location.\u00a0 I would like the notes to stay, as this is where I enter the plot information.<\/p>\n

\"Legacy<\/p>\n

The same can be said for the other vital events, such as place of birth and death (e.g., name of hospital) and baptism (e.g., name of church).\u00a0 I\u2019d also like to see this option for all event types solely to maintain consistency.\u00a0 Sure, I can enter an event for a funeral, and put the church name in the description field, but because it\u2019s not a master, that church name could be altered each time I enter it whether it be for a funeral, baptism, confirmation, or other church event.\u00a0 And again, any information added to the \u201cplace\u201d field, such as address, would be carried along.\u00a0 A change of this type would require a lot of cleanup, but I\u2019m okay with that.<\/p>\n

Sources<\/strong><\/p>\n

First and foremost, I want to be able to source each piece of an event.\u00a0 For example, if the source I have only gives me a date of birth, but not the location, I want to attach the source to the date piece only, not the entire birth event.<\/p>\n

The other thing I\u2019d like to see with regard to sources is the ability to customize the available templates and create new templates.\u00a0 One of my pet peeves is the way some source templates operate.<\/p>\n

For example, the US census templates want you to specify the state and county in the master source.\u00a0 However, when you are dealing with a ton of places over many years, that list will grow astronomically!\u00a0 So, I choose to have one master source for each year, and then put the city, county, and state in the city field of the source detail.\u00a0 It of course renders my source citation a little differently, but at least it\u2019s consistent and I don\u2019t have an insane amount of sources, by place, for each census.\u00a0 If I were able to customize the source template, I could probably fix that problem.\u00a0 I could also create custom templates for sources where no template exists, which I could then reuse to maintain consistency.<\/p>\n

Either of these changes would require a lot of data cleaning.\u00a0 However, most of us are still cleaning up from the old source system to the SourceWriter system, so, hey, why not.\u00a0 Unfortunately, that\u2019s just they way it works with software sometimes.<\/p>\n

Events Attached to Multiple People<\/strong><\/p>\n

Wouldn\u2019t it be great if you could just enter an event for one person and then add other people and their \u201crole\u201d to that \u201cmaster\u201d event?\u00a0 (Yes, there is a program out there that does this very thing.)\u00a0 It would certainly be great for censuses; add the event to the head of household and attach everyone else to the event (instead of copying\/pasting the event for each person).\u00a0 Then, if you make a change to the event, say you made a typo or found new information, it would update it for everyone attached.<\/p>\n

This would also be great for events such as weddings or funerals, where you can attached those who attended the event.\u00a0 It would also work well for records such as deeds, where you could attached the grantee and grantor, as well as any witnesses (certainly helps with analysis when using the FAN principle).<\/p>\n

Last Words<\/strong><\/p>\n

This isn\u2019t too much to wish for, is it?\u00a0 Guess we\u2019ll find out soon.\u00a0 What about you, do you have a Legacy wish list?\u00a0 Leave a comment and let me know what you\u2019re hoping to see in Legacy 8.<\/p>\n

\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I\u2019ve been hearing rumors that a new version of Legacy Family Tree will be released later this year.\u00a0 In fact, Geoff Rasmussen will be discussing it at SCGS Jamboree later today in a demo called \u201cWhat\u2019s New in Legacy Family Tree 8.\u201d\u00a0 (Boy, I wish […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[25,29],"tags":[365],"class_list":["post-305","post","type-post","status-publish","format-standard","hentry","category-genblog","category-technology-genblog","tag-tools-tech-legacy","cat-25-id","cat-29-id"],"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3HcLI-4V","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/posts\/305","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/comments?post=305"}],"version-history":[{"count":3,"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/posts\/305\/revisions"}],"predecessor-version":[{"id":2719,"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/posts\/305\/revisions\/2719"}],"wp:attachment":[{"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/media?parent=305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/categories?post=305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/genealogy.julietarr.com\/blog\/wp-json\/wp\/v2\/tags?post=305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}