The combined record would be too large - WHAT?

Discussions about using and improving the new FamilySearch online application.
BradJackman-p40
New Member
Posts: 30
Joined: Fri Jan 25, 2008 10:09 am
Location: Salt Lake City, UT

The combined record would be too large - WHAT?

#1

Post by BradJackman-p40 »

Apparently lots of people are getting this error since the updates made during the shut-down at the end of June: "The following records could not be combined for the these reasons: The combined record would be too large"

Whoever thought up that one needs to be fired. Dump all the old, abandoned databases into one pile, mess it up real well, make the members sort it out, but only let them combine records if Grandpa Jones is in there less than 89 times.

Wasn't the whole point of this mess to reduce duplication (Even internal estimates are showing that duplication is currently at 30% in NFS)? And now someone sets an arbitrary number of individuals that can be combined, and we're not allowed to go over that? Do you realize the implications? This dooms NFS to the same fate as all the other dead LDS databases. I guess I'll just have to wait 10 years for this system to die a sad, hopeless death, and see what someone comes up with as "the next big thing that's going to eliminate duplication and save genealogy forever", like I did with the Ancestral File, Pedigree Resource File, TempleReady, IGI, etc... The track record for LDS databases is pretty bad. Nobody's changed their thinking enough to fix it. They just apply the same theories to the data using new coding languages.

Come on people. Geesh.
User avatar
garysturn
Senior Member
Posts: 606
Joined: Thu Feb 15, 2007 11:10 am
Location: Draper, Utah, USA
Contact:

To many records to combine

#2

Post by garysturn »

I have had the same error message several times. I am hopping this is just a temporary solution while they address the problems they are having from large files. I have some ancestors I can not even view without long delays because of the large numbers of names in the folders. This same problem of large numbers of records in folders is what has slowed the rollout of the system to more Temple districts. Maybe we need to give them a little time to work out these problems. I am sure it is one of their highest priorities. I am also sure they would like feedback if someone has some suggestions that thy feel will be helpful. There is a system in place inside the nFS help center to submit feedback to the programmers.
Gary Turner
If you haven't already, please take a moment to review our new
Code of Conduct
lfalin-p40
New Member
Posts: 9
Joined: Sun Feb 17, 2008 4:07 pm
Contact:

#3

Post by lfalin-p40 »

Or maybe you could patiently wait for the fix while you contemplate the fact that no one is perfect.
User avatar
ClarkeGJ
New Member
Posts: 27
Joined: Fri Jan 19, 2007 12:06 pm

Too Large

#4

Post by ClarkeGJ »

This is a temporary measure. The limits will be raised or removed after we complete necessary data reorganization.
Gordon Clarke
FamilySearch DevNet manager
User avatar
mkmurray
Senior Member
Posts: 3266
Joined: Tue Jan 23, 2007 9:56 pm
Location: Utah
Contact:

#5

Post by mkmurray »

lfalin wrote:Or maybe you could patiently wait for the fix while you contemplate the fact that no one is perfect.
BradJackman and Scion have some very valid concerns, both with the NFS software and how us moderators approach the concerns of other users on this forum. This thread has kicked up much discussion between us moderators and hopefully there will be some good change out of all of this.

As for a "fix" to NFS, I don't think much attention would have been given to this issue if were not for this thread...
User avatar
mkmurray
Senior Member
Posts: 3266
Joined: Tue Jan 23, 2007 9:56 pm
Location: Utah
Contact:

#6

Post by mkmurray »

mkmurray wrote:BradJackman and Scion have some very valid concerns, both with the NFS software and how us moderators approach the concerns of other users on this forum. This thread has kicked up much discussion between us moderators and hopefully there will be some good change out of all of this.

As for a "fix" to NFS, I don't think much attention would have been given to this issue if were not for this thread...
However, I should caution all (including us moderators) to have patience and be civil with each other (including us moderators). ;)
lfalin-p40
New Member
Posts: 9
Joined: Sun Feb 17, 2008 4:07 pm
Contact:

#7

Post by lfalin-p40 »

I agree that the concern is valid, calling for people to be fired seemed a bit extreme though.
User avatar
mkmurray
Senior Member
Posts: 3266
Joined: Tue Jan 23, 2007 9:56 pm
Location: Utah
Contact:

#8

Post by mkmurray »

lfalin wrote:I agree that the concern is valid, calling for people to be fired seemed a bit extreme though.
Yes...that is one of quite a few comments from everyone here that prompted me to ask everyone to be more civil.
BradJackman-p40
New Member
Posts: 30
Joined: Fri Jan 25, 2008 10:09 am
Location: Salt Lake City, UT

Maybe a little too harsh...

#9

Post by BradJackman-p40 »

I apologize for my harsh words, it just seems like:

a) Everyone is turning a blind eye to issues that will severely damage the genealogical integrity of the Church's new system, believing that every element of NFS is infallible and inspired by God.
b) Nobody is willing to take a hard look at what really needs to be done to fix it
c) Users are being slammed by moderators and "NFS is infallible" supporters when problems are being raised.

I have to deal with the implications of every NFS update, every day, all day. Every change of technique, every lack of function, every IOUS and every false "take me to the temple" button requires me to address these issues over, and over, and over.

Calling for firing was too harsh. I didn't mean it. I do, however, wish NFS people would take a serious look at major overhauls, instead of little bandaids like "The combined record would be too large." Even "raising the limit" as Godon Clarke suggested, is absurd. If you can't combine every single duplicate, the whole plan is flawed.

I work with professional genealogists all day long. Every one of them has great suggestions for improvement, but nobody is listening. It's incredibly frustrating.

If this was a piece of commercial software, I'd just move to a competitor, but you're dealing with a product that will be mandatory for use by millions of users, and will be used to judge the Church's level of authenticity in the genealogical field. If NFS fails, people don't just lose their programming jobs - millions of volunteer hours will be lost, millions of Church members will suffer, temple duplication will increase, and the work of the Lord will be hindered.

I see serious problems, and I think I have a unique perspective. If I don't speak up, and get someone to take notice, I'm as much at fault as the programmers who don't understand real genealogy.

So, I'm sorry for coming off uncivil, but it's righteous indignation. I want NFS to succeed so everyone can benefit, but people need to change their way of thinking, and I don't see anyone asking questions, only defending problems.
User avatar
garysturn
Senior Member
Posts: 606
Joined: Thu Feb 15, 2007 11:10 am
Location: Draper, Utah, USA
Contact:

#10

Post by garysturn »

I understand your frustrations. Moderators are just ordinary people just like you, we are not Church employees or programers and we have no more access to the inside than any other member. I have submitted a lot of feedback to nFS over the past year. Much of the feedback is about the very issues you are describing. It does seem like no one is listening sometimes but I know that is not true. I have spoken with some of the programers in person and they are aware of the issues you bring up and they are working on solutions. There are a lot of genealogy people involved in refining this system, not just programmers. The developers want to hear your solutions and they do listen. Go to nFS help center or FamilySearch labs and submit your feedback.
Gary Turner
If you haven't already, please take a moment to review our new
Code of Conduct
Post Reply

Return to “FamilySearch Family Tree Application”