nFS: New Family Search and Evidence Hierarchy in Combining Names
Why not make the nFS system do an evidence hierarchy? For each data
entry, there is the "best" source record, then the next best and so
on. If the system operated with a sequential presentation of formats
listing the most primary record available for any given event; also,
added thereto a computer system search to attach that given evidence
to any indexed reproduced online original record sources, (as well
as the ability to recheck these databases over time), the whole
Temple Ordinance Work record system would consistently become fully
acceptable, as well as train submitters in correct record keeping.
Temple Ordinance Work would remain in effect, from oral tradition to
original do***ent, with the printout giving information from the
most primary record. Automatically, the record system could become
self correcting, whenever any name or identity was matched within
the series of various references, by producing in the end, the name,
dates and places noted from the most original "best" primary
sources; attaching thereto the dates and the duplicates of Temple
Ordinance Work done over time. This would stop, once and for all,
excessive errors and weed out all entries submitted from fictitious
data records, made up by individuals trying to corrupt the database,
or by unintentional neglect or ignorance.
I also agree that it takes human reasoning. Modify the process
developed for Name Extraction Programs. . . . "To ensure accuracy,
two transcriptions of each entry are made and compared to find and
resolve discrepancies."
http://www.lightplanet.com/mormons/daily/family_history/name_eom.htm
To ensure accuracy, "highlighted" information should be provided in
summary format to compare and contrast submitted reference evidence
discrepancies, (similar to a Norton Internet Security full system
scan):
I. list of total field items scanned;
II. error "risks" that were detected;
III. "attention required" tab:
(a) requiring attention, and
(b) resolved. Some problems are easily cleared up by novice
submitters, while others may jeopardize the record file, with
attached personal temple ordinance work.
(c) Evidence Hierarchy is mandatory because: "Whenever the evidence
hierarchy is altered, submissions are automatically reviewed by
professional staff personnel at Church headquarters to validate the
assumptions made are in accordance with professional genealogical
standards, before inclusion within the Master Database."
The process suggested is equivalent to an LDS Temple Ordinance Work
"TITLE SEARCH".
http://en.wikipedia.org/wiki/Title_search
Life Browser to include: ALL OF THE ABOVE, and:
(1) Record of all those "who consecrate properties, and receive
inheritances legally from the bishop".
(2) Link reference to members, "their manner of life, their faith,
and works" (Individual and Family Biographies).
(3) Record of the apostates who apostatize after receiving their
inheritances. Church Court link to Priesthood actions, "whose names
are not found written in the book of the law, or that are found to
have apostatized, or to have been cut off from the church, as well
as the lesser priesthood, or the members" . . .
(4) Records received from beyond the veil. This will require, in my
own opinion, the restoration of the Office of Church Patriarch,
within the family of Hyrum Smith, to oversee and expand the full
family history record program, from Adam on down to the last person
to live upon this earth, in a mortal state. The office of Stake
Patriarch would provide the worldwide church channels from which The
House of Israel could be brought down to the present generation,
within the local jurisdiction of the Stake Presidencies of the
Church, by revelation, to worthy Temple recommend holders.
http://www.josephsmithsr.org/do***ents/newspaper/sltrib_20061230.pdf
Respectfully yours,
Tom Tinney, Sr.
Who's Who in America,
Millennium Edition [54th] through 2004
Who's Who In Genealogy and Heraldry, [both editions]
http://www.academic-genealogy.com/
Family Genealogy & History Internet Education Directory
"vctinney@[EMAIL PROTECTED]
" <vctinney@[EMAIL PROTECTED]
>
|
