On Familysearch Who Is Allowed to See a Memory That Has Be Created/uploaded for a Deceased Person

Annotation: FamilySearch informs me that the Pedigree Resource File has not been renamed. I've made that correction to this article. (17 Feb 2015)

Bill Mangum, a product manager at FamilySearch, presented a session at the RootsTech Innovator's Acme titled "FamilySearch Product Road Map." Considering it was an Innovator'southward Summit session, he warned us that there would be some technical content and that the session'southward audience was FamilySearch partners. Mangum is the product manager for the dorsum end. That's the man behind the electric current. More precisely, he's the production manager of the man behind the current.

FamilySearch Family unit Tree

• Nosotros talk nearly Family Tree as being SCOE: source axial open up edit, he said. We want people to specify sources for data in the tree. And we want everyone to contribute. We desire users to provide reasons when they add or modify the tree. Family Tree keeps a log of changes and gives the capability to restore inverse values. Discussions are saved. Information technology is possible to trigger an electronic mail when something changes data. That is called a watch.
  
• The hard function of the model is resolving conflicts. Partners are encouraged to help out in this regard. We've seen conflicts resolved when people add sources, add together a picket, and when changes occur, contacting the person making changes without sources, he said.
  
• Some things are irresolute [in the way partners collaborate with the back end, I presume]. "Rules are really rules and not suggestions." Mangum wouldn't elaborate except to say that they are going to make it harder for people to make unfounded changes.
  
• The desired direction is to make sources more obvious as part of the consummate record.
  
• FamilySearch is calculation Help Panels to the correct side of some pages. A pop out comes out with helpful information and brusk videos. (I wonder about that. If they tin't beget to provide an upward to date transmission, how will they keep up when information technology comes to expensive video clips.)
  
• FamilySearch applies changes to the tree three times a 24-hour interval. Most are backside the curtain and don't touch on users.
  
• Hints are large and are resulting in many, many sources beingness added to the tree.

Backend Conversion

• FamilySearch is changing the backend database from Oracle to a non-SQL database. (Didn't I warn you that some of this would exist technical?)
  
• FamilySearch has more than users on Dominicus than any other twenty-four hour period. Recently, usage has increased so much that weekdays are busier than Sundays used to be. Sunday usage is even heavier. (This makes the website slow.)
  
• As of part of the solution, they accept shutdown new.familysearch.org and moved the resources over to piece of work on speeding up Family unit Tree. To accomplish capacity goals for 2020, they are having to make major changes to the backend. Besides moving away from SQL, they are moving computers to the AWS cloud. (That doesn't mean anything to nearly of you lot, merely it allows them to beg or borrow additional servers when they need to, without using or paying for them at other times.)

User Submitted Genealogies

The User Submitted Genealogies (including Full-blooded Resource File or PRF) department of FamilySearch.org has been an underutilized resource. To notice it, go to Search > Genealogists and scroll to the bottom of the folio. When y'all upload your tree, information technology is "edible but non editable." It is visible to be searched and seen by anyone, but no one can change it. "We are going to preserve it, basically, forever," he said. The correspondent can't edit it online, only can upload a replacement. (This is unlike PRF, in which regular submissions resulted in lots of nearly identical trees.)

A software engineer, chimed in with additional information. (I don't recollect if they identified him past name so I shouldn't mention it. Randy, practice you recall? Oops.) FamilySearch is working towards the goal of being able to preserve person ids when uploading a new version. Also, when you upload your GEDCOM, sources are preserved. Files must be GEDCOM format. GEDCOM X is not supported.

The User Submitted Genealogies user interface is going to be improved over what information technology is at present. Remember, "futures" may or may not happen.

When yous search User Submitted Genealogies, you tin search just the Ancestral File, or PRF, or both. Merely you can't search past submitter. (Randy piped in again: If yous find someone in a tree you wish to focus on, yous can click on the submission number and go a search grade that specifies that submission'southward number.)

Community trees are currently on a separate website, only volition exist moving over to FamilySearch.org.

Identify API

(I'one thousand not going to talk about this, other than to say this is a service FamilySearch provides to the community to handle place names and jurisdictions. It is the same matter you tin see today in Standards Finder in FamilySearch Labs.) The database has about a 1000000 historical places. It handles historical name changes, For case, Allen'southward Campsite, Arizona changed to St. Joseph, Yavapai County, Arizona, which changed to St. Joseph, Apache County, Arizona, which inverse to Joseph Metropolis, Apache County, Arizona.

Mobile

FamilySearch currently has two mobile applications. In the time to come the Tree app will have the power to add together new persons, create and change conclusions, and create and modify relationships. The Memories app will allow tagging and people view.

Memories

The Memories API (application programming interface) will allow partner apps that can upload, read, delete, and attach memories (photos, stories, and documents). Information technology allows citing a document every bit a source. Information technology can read all the memories uploaded by the current user.These are all things that partners haven't been able to exercise. We're going to come across much richer partner apps.

You tin upload in jpg, tif, gif, bmp,and pdf, upwards to 15 MB. (Not every season of every types is supported.) Notice tif support. Yay! And the increment to 15 MB. Yay!

Bulletin Services

FamilySearch is going to complete a little service this yr that volition allow a user to send a message to another user of FamilySearch.org. On a user's contact card you'll be able to click a link to send a bulletin. When they login, they volition see an icon indicating they take new messages. Mangum's personal preference would be that the message is visible to all. The messaging service is not going to be bachelor in the API on initial release. They hope to have this in the first half of this year.

Open ID Connect

This feature isn't really something yous will notice every bit a user, (then I don't know why I'm even mentioning information technology). Information technology volition allow single sign-on. It is coming this twelvemonth.

Ideas for Partners

FamilySearch wants to provide everything users need, but tin can't do everything. Unlike other companies, FamilySearch has a set scope. Partners could do products outside that telescopic, like medical apps, or other relationship oriented products.

thomaspoick1949.blogspot.com

Source: http://www.ancestryinsider.org/2015/02/

Share this post