Community Moderators
I have an idea for an enhancement or new feature for the Combined Records page in the new FamilySearch. I submitted through email to FamilySearch Support but wanted to mention it in this forum.
I believe this feature would have large returns on a modest developer investment--the returns being in more efficient and accurate separation of records in cases where information about multiple real individuals had been erroneously combined into one record. (I have done at least three separation operations myself, so I think I have some understanding of how it works.) I believe it could be implemented entirely in JavaScript, so the only increase on FamilySearch server load would be a small increase in the size of the page content sent to the browser.
The basic idea would be to add "color" buttons to the left-hand column. They could be done in radio-button or check-box style. When a user clicked to activate a color for a particular row, the corresponding columns would show that color in the upper box for that column. It could also show the color for the box in the middle of the table, but the column header is more important. (I would suggest hiding the color buttons until/unless the user clicks on another button to unhide them.)
The usage case I would propose for this feature is for a user who has an idea of the birth and death dates and parents' names for the two (or perhaps more) real individuals whose records had been combined into one record. For example, one set of dates is from the 1700s, and the other set of dates is from the 1800s. The user would click one color for the 1700 dates and the parents whose dates are consistent with a child in the 1700s. The user would click on a different color for the 1800s dates and the parents whose dates are consistent with a child in the 1800s.
The page would propagate the coloring to the column headers. The user could then readily see which component records are from the 1700s individual, which are from the 1800s individual, which are not conclusive, and which might have an internal conflict (which requires help from FamilySearch Support to resolve). Once the component records are all clearly classifiable as to where they belong, the user would very accurately check to separate out all the records of one color and leave the records of the other color.
For the combined records I have separated, I have manually emulated this coloring operation by printing screen-shots of various parts of the page, trimming the prints, and taping them together to mimic the full scrollable page. Then, with a red and green marker, I have marked the left column, then the middle boxes, then the column headers. I then used the colors to guide me in selecting which records to separate. If this feature were implemented in the page, it would eliminate a great deal of risk of inaccurate separation.
I believe this feature would have large returns on a modest developer investment--the returns being in more efficient and accurate separation of records in cases where information about multiple real individuals had been erroneously combined into one record. (I have done at least three separation operations myself, so I think I have some understanding of how it works.) I believe it could be implemented entirely in JavaScript, so the only increase on FamilySearch server load would be a small increase in the size of the page content sent to the browser.
The basic idea would be to add "color" buttons to the left-hand column. They could be done in radio-button or check-box style. When a user clicked to activate a color for a particular row, the corresponding columns would show that color in the upper box for that column. It could also show the color for the box in the middle of the table, but the column header is more important. (I would suggest hiding the color buttons until/unless the user clicks on another button to unhide them.)
The usage case I would propose for this feature is for a user who has an idea of the birth and death dates and parents' names for the two (or perhaps more) real individuals whose records had been combined into one record. For example, one set of dates is from the 1700s, and the other set of dates is from the 1800s. The user would click one color for the 1700 dates and the parents whose dates are consistent with a child in the 1700s. The user would click on a different color for the 1800s dates and the parents whose dates are consistent with a child in the 1800s.
The page would propagate the coloring to the column headers. The user could then readily see which component records are from the 1700s individual, which are from the 1800s individual, which are not conclusive, and which might have an internal conflict (which requires help from FamilySearch Support to resolve). Once the component records are all clearly classifiable as to where they belong, the user would very accurately check to separate out all the records of one color and leave the records of the other color.
For the combined records I have separated, I have manually emulated this coloring operation by printing screen-shots of various parts of the page, trimming the prints, and taping them together to mimic the full scrollable page. Then, with a red and green marker, I have marked the left column, then the middle boxes, then the column headers. I then used the colors to guide me in selecting which records to separate. If this feature were implemented in the page, it would eliminate a great deal of risk of inaccurate separation.