From the Q&A question about the future of PAF, a new FamilySearch Open-Source program for the desktop is mentioned. I am assuming this will allow people to use thier Family History lines from new FamilySearch off line. With this program being open-source the possibilites for its functions are unlimited. What types of functions would people like to see this new program do?
Quote from Q&A below:
FamilySearch Open-Source Desktop
In the future the Church will announce the opening of a FamilySearch desktop project in order to work with "open source" developers on a desktop application that can read and write data in the new FamilySearch application using the FamilySearch API. This project will have a code base that can be portable for Microsoft Windows, Apple Macintosh, and Linux.
Read the entire Q&A entry
FamilySearch Desktop Program
-
garysturn
- Senior Member
- Posts: 606
- Joined: Thu Feb 15, 2007 11:10 am
- Location: Draper, Utah, USA
- Contact:
FamilySearch Desktop Program
Gary Turner
If you haven't already, please take a moment to review our new Code of Conduct
If you haven't already, please take a moment to review our new Code of Conduct
-
russellhltn
- Community Administrator
- Posts: 34485
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
-
lawrence.sproul
- New Member
- Posts: 8
- Joined: Sun Jan 30, 2011 8:33 am
It is esssential to be able to detect cyclic connections; e.g. a father recorded as his own son.
in most cases, such cyclic connections are a result of an inapropriate merge of two or more records.
It would be nice if the software could suggest the most likely "bad merges" which set up each cycle.
The recomendation function would require a comparison of merged records and may require adjustment of the API for proper functionality.
in most cases, such cyclic connections are a result of an inapropriate merge of two or more records.
It would be nice if the software could suggest the most likely "bad merges" which set up each cycle.
The recomendation function would require a comparison of merged records and may require adjustment of the API for proper functionality.
-
JamesAnderson
- Senior Member
- Posts: 773
- Joined: Tue Jan 23, 2007 2:03 pm
Family Tree will take care of a lot of the 'bad merges', because it doesn't work on the 'combining' model of working with all the multiple entries for a person.
Instead, it will follow a 'wiki' style model, where you change data, and a change log will exist for each person in the tree. So you'll be able to clear out these bad merges where the father is his own son, etc.
Instead, it will follow a 'wiki' style model, where you change data, and a change log will exist for each person in the tree. So you'll be able to clear out these bad merges where the father is his own son, etc.