I've been working with small rural community in upstate NY which had lots of data on the many people who have passed through our boundaries (and a lot who started and ended here too). Many large families, highly interlocked, and many small groups and individuals, too. Three hundred years of a community. Some of our holdings has been entered into computers, but much of it is still on paper: some original documents and lots of handwritten "research" notes. From everything I've seen so far, documentation is minimal. I know this isn't strictly genealogy in the traditional sense, but it is clearly useful information that can help researchers at least at the clue level. We need to get it into computers to give it organization and make it accessible.
I think we can use Legacy to provide a structural framework for organizing all of this. With it's ability to run on a network plus the IntelliShare capability seem to make it the uniquely best tool to support a multiple-person volunteer effort. I am seeking input and guidance from anyone who has had experience in this sort of community-wide, and volunteer effort. I'm looking for any insights and recommendations, experiences, and especially insights on where we might find that Legacy doesn't handle something well ... the good, the bad, and the stuff we need to watch out for. -*RcR* Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
<<attachment: image002.gif>>
