new FamilySearch API

rmrichesjr
Community Moderators
Posts: 1037
Joined: Thu Jan 25, 2007 11:32 am
Location: Dundee, Oregon

new FamilySearch API

Postby rmrichesjr » Mon Feb 26, 2007 4:04 pm

In another thread, a couple of postings have very briefly mentioned that there will be some sort of API for the new FamilySearch in order to provide more efficient access to the new system by programs other than a web browser. I seem to recall mention that an off-line desktop genealogy record manager could use the API for syncing with FamilySearch.

Is there some information about this API that could be shared?

How soon after the main release of the new FamilySearch will the API be available to use?

Is the API going to be documented for use by open-source or personal projects?

What hoops would a developer or individual have to go through to get documentation and permission to use the API?

Thanks.

User avatar
ClarkeGJ
New Member
Posts: 27
Joined: Fri Jan 19, 2007 12:06 pm

FamilySearch API

Postby ClarkeGJ » Tue Feb 27, 2007 9:07 am

FamilySearch API should be released the following release after FamilySearch goes final. The API will include member authentication, read, search, and update all person information. Yes we expect there to be many desktop applications that "sync" with the new FamilySearch using the FamilySearch API. Please contact Gordon Clarke for additional informaiton. clarkegj@ldschurch.org
Gordon Clarke
FamilySearch DevNet manager

User avatar
HaleDN
Church Employee
Church Employee
Posts: 44
Joined: Mon Jan 22, 2007 2:08 pm
Location: Herriman, Utah, USA
Contact:

Postby HaleDN » Tue Feb 27, 2007 9:14 am

Is anyone aware of an existing Open Source project which is similar to PAF? I don't believe that the LDS Church has made an official statement that they will no longer be creating PAF updates, but the unofficial rumors suggest this. If the current PAF isn't going to be updated to use the new Family Search APIs, it will quickly become obsolete once Family Search is released from beta.

Rather than depend on only commercial products to fill this gap, I would love to see an Open Source project (even if it has yet to be created) to fill this gap and utilize the new Family Search API.

russellhltn
Community Administrator
Posts: 20721
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Tue Feb 27, 2007 11:39 am

haledn wrote:Rather than depend on only commercial products to fill this gap, I would love to see an Open Source project (even if it has yet to be created) to fill this gap and utilize the new Family Search API.


Just as a note there are FREE commercial products that do what PAF does and include the LDS ordnances. No doubt they'll be updated to sync of FS when that becomes available.

Something I feel that's being neglected is the research side of things. Something to take in scraps of information, and make some suggestions. Something that can track what has been searched to avoid duplicate searches. This probably should be something that will run on a PDA since I think it's more commonly used and on-hand then a laptop.

rmrichesjr
Community Moderators
Posts: 1037
Joined: Thu Jan 25, 2007 11:32 am
Location: Dundee, Oregon

Postby rmrichesjr » Tue Feb 27, 2007 12:51 pm

gordon wrote:FamilySearch API should be released the following release after FamilySearch goes final. The API will include member authentication, read, search, and update all person information. Yes we expect there to be many desktop applications that "sync" with the new FamilySearch using the FamilySearch API. Please contact Gordon Clarke for additional informaiton. clarkegj@ldschurch.org


Thanks for the info on the API plans. I'll email (if the wind doesn't take out the local power grid).

haledn wrote:Is anyone aware of an existing Open Source project which is similar to PAF? I don't believe that the LDS Church has made an official statement that they will no longer be creating PAF updates, but the unofficial rumors suggest this. If the current PAF isn't going to be updated to use the new Family Search APIs, it will quickly become obsolete once Family Search is released from beta.

Rather than depend on only commercial products to fill this gap, I would love to see an Open Source project (even if it has yet to be created) to fill this gap and utilize the new Family Search API.


One open source program that I like is Gramps. I understand it now runs on that most common operating system as well as on Linux. If it were up to me, I'd use Gramps and not bother with PAF, but my wife didn't want to learn two programs, and PAF is what is available at the FHC, so PAF is what I use so I can maybe help her when she needs assistance.

I saw a posting in another thread in this forum to the effect that the Church is planning to sponsor a project using open-source methods. I believe the term was "desktop record manager" to work with the new FamilySearch. Maybe some of us will be able to help with that project.

User avatar
bhofmann-p40
Member
Posts: 272
Joined: Tue Feb 06, 2007 9:47 am
Location: Tulsa, OK
Contact:

Postby bhofmann-p40 » Thu Mar 01, 2007 11:02 am

gordon wrote:FamilySearch API should be released the following release after FamilySearch goes final. The API will include member authentication, read, search, and update all person information. Yes we expect there to be many desktop applications that "sync" with the new FamilySearch using the FamilySearch API. Please contact Gordon Clarke for additional informaiton. clarkegj@ldschurch.org


I know you asked to contact you for information but I thought your answer to my questions might interest others. I was wondering if you could give a high level overview of the technical specifications of the API? I'm interested in things like programming language, if there will be web services, how comprehensive the API will be, etc.

Thanks.

User avatar
greenwoodkl
Member
Posts: 242
Joined: Sun Jan 21, 2007 1:59 am
Location: Orem, Utah, United States
Contact:

GEDCOM 6.0 part of new FamilySearch?

Postby greenwoodkl » Sat Mar 03, 2007 7:48 pm

I'm just curious if the GEDCOM 6.0 XML Draft Specification has been superseded, absorbed, enveloped, included into the new APIs and structure of the new FamilySearch? Anyone know or can anyone say?

russellhltn
Community Administrator
Posts: 20721
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Sat Mar 03, 2007 11:16 pm

Good question. Last I had heard is that the church had hopped out of the drivers seat on GEDCOM. I forget the exact reason, but it had to do with prioritizing resources.

User avatar
greenwoodkl
Member
Posts: 242
Joined: Sun Jan 21, 2007 1:59 am
Location: Orem, Utah, United States
Contact:

Postby greenwoodkl » Sun Mar 04, 2007 12:10 am

If it's true that the Church has "hopped out of the driver's seat," I haven't heard of anyone else jumping in the open spot. As I understand it, GEDCOM was developed by the church and has become a standard for genealogical programs. If ideas from it have been implemented into the new FamilySearch and its corresponding API, perhaps as the industry tries to be compatible, whatever the FS API is will become a new standard - assuming it's not just an interface but also includes some sort of file format.

User avatar
ClarkeGJ
New Member
Posts: 27
Joined: Fri Jan 19, 2007 12:06 pm

Gedcom 6.0

Postby ClarkeGJ » Mon Mar 05, 2007 12:26 pm

The Church is not currently doing anything with GEDCOM 6.0 (XML) format. However, our yet-to-be-announce FamilySearch API do use a REST approach with XML-based schemas for data exchange.
Gordon Clarke

FamilySearch DevNet manager


Return to “Software Development”

Who is online

Users browsing this forum: No registered users and 1 guest