Jump to content


NEreswearcher

Member Since 19 Nov 2017
Offline Last Active Feb 18 2018 03:37 PM
-----

Topics I've Started

Long Term Preservation of Data

18 February 2018 - 12:57 PM

This may not be a topic for this forum and if so we can  move or delete it.

 

I have been wrestling with long term preservation of my genealogical data. I have been working with genealogy since the mid 1980's. Started with Word, Went to Brothers Keeper in early 1990's and about 1995 moved to The Master Genealogist until late 2014 when it went defunct and I switched to Rootsmagic. Every conversion cost me dearly which made me concerned what would happen when I stop this and could someone else pick up the work at a later time. I have no solutions at this time but I have considered the following:

  1. Provide backups to Rootsmagic SQLite database both onsite and offsite.
    1. Good short term solution but if this lies dormant for 20 years who will be able to read that database.
  2. Provide GEDCOM file. (I assume Rootsmagic may go away in the next 20+ years)
    1. The current GEDCOM output from Rootsmagic conforms to the standard but the output is not fully supported by any other software package and on import to something other than Rootsmagic, data is lost.
    2. GEDCOM X may provide a solution if:
      1. The GEDCOM X standard is completed and if it will back up everything.
      2. If Rootsmagic implements the GEDCOM X standard and other programs support the GEDCOM X standard as Rootsmagic has implemented it.
  3. Conclusion: At this time no physical backup will provide recoverability in the long term.
  4.  Print all my data that can be scanned in in future if data is not readable
    1. Print an individual summary and select everyone in a database.
      1. No other option can get everyone without a lot of duplication.
      2. Would require a large effort to reconstitute database.
    2. Print Narrative reports
      1. Ancestor reports would miss many people in my database.
      2. Descendant reports would capture everyone but would require a large number of reports, one for each family line.
      3. Combining into a single report would be problematic in that if I have 100 surnames to print descendant reports for they would all start at  number one. These numbers would need to be edited to accommodate all lines and would be error prone.
    3. Wish: The ability to select as many people as I want and have a combined descendancy report for all lines selected and eliminating duplicates.
  5. SQL to create something like a comma delimited file for every table. Need also the structure and definitions for all tables and fields to later import back into an SQL database
    1. SQL dump command outputs data and structure to a text file of SQL commands.
    2. Will work as long as SQL databases exist and can execute SQL commands.
    3. Relational databases were describe back in 1970 and SQL was accepted as a standard in 1986. While some changes might be required to the text file containing all the SQL it could be edited to adjust for changes.
  6. Export all trees to Ancestry, Familysearch or other and hope they don't go away.
  7. Comments or suggestions would be appreciated.

SQL Help

13 February 2018 - 03:29 PM

This is probably not for this forum but I have been looking at Tom H's site and I see that that address space will be going away. Any relocation or is this the end?


Duplicate Birth, Marriage and Death facts

12 February 2018 - 09:03 AM

I was given an old hand written chart from a distant cousin that extended my family tree on one line back five generations. Of course none of the data was sourced. I created a new separate database to start entering this new data, planning on a merge when I felt satisfied that this was in fact was a proper extension to my family tree. I reached that point and did a merge on separate copies of both databases so that if something went wrong I could just revert to my last correct database.

 

1  Create backup copies of both databases.

2  Did a drag and drop from the new database to my existing database copy specifying to bring the entire new database over.

3  Did a manual merge of the three people that were common between the two databases

 

Everything looked great until i looked at a person who should not have been affected by this merge. I noticed that this person had duplicate Birth, Marriage and Death facts. The only difference was that the place information for each fact was different. On one I used City and state and the duplicate had city, county and state. An easy fix but I can't imagine how I could have created this situation, which is my first question. Could I have done a merge or something in the past that would have created this? I don't think that the current merge had anything to do with these duplicate facts.

 

Second question - Is there a way to find all occurrences of these double facts?

 

I still have not gone beyond the merge and I have all copies of my data intact.


not started / in progress flags

25 January 2018 - 10:40 AM

I am using PH2 and RM7 to rework all my facts to make a better story of my ancestors. I would like to have all my stories in PH2 to have an initial status of not started but have not found a way to do that yet except individually by story. A brand new import leaves my stories in varied states of in progress  or not started etc.


Version 3 availability

17 January 2018 - 11:43 AM

I know a new version is coming out this quarter. Anyone know when?

 

If I buy version 2 will I get a free upgrade to version 3?