Wednesday, June 26, 2013

FamilySearch Prepping to Move Source From NFS to Family Tree

An example of an NFS sourceFamilySearch recently told users that they are preparing to move some of the sources from new.FamilySearch.org (NFS) to FamilySearch Family Tree. In an email to source contributors, they said, “If you created sources in new.familysearch.org and do not want to have them transferred to Family Tree, please let us know by clicking on the link below and entering the information requested.”

The option to not migrate sources to Family Tree is provided for people like Heather McPhie. She wrote,

There are some patrons (myself being one of them) who spent hundreds of hours in NFS adding sources, but found that the formatting in FT is so much superior to the NFS formatting that we are working to add those sources again using the FT formatting. There have been a lot of requests to allow patrons to opt in or out of having their sources brought over from NFS. I, for one, do not want my NFS sources brought over since a lot of them are now duplicates. I know others who feel this way, too.

Last month Ron Tanner wrote,

In a few weeks we will be sending out a survey to ask people if they want their NFS sources brought over or not. Those who choose to not move them over, we will not migrate their entered sources. For everyone else we will migrate their entered sources. Essentially the form in nFS was to generate a citation. We will collapse these pieces to create a citation and titles[.] [O]ther information will be in the notes. We will create sources for you (they will appear in your source box) and attach them to the person they are on in nFS.

Terrence Mason suggested that the survey include examples showing how the transferred sources would look so he could make an informed decision. NFS sources have 18 fields (see above illustration). Family Tree has four.

Regardless, many users have voiced their desire to have their sources migrated and will be happy to see it take place.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.