9
edits
FamilySearch Wiki:WikiProject Waypointing: Difference between revisions
FamilySearch Wiki:WikiProject Waypointing (view source)
Revision as of 11:42, 13 May 2011
, 13 May 2011Fixed spelling error
No edit summary |
m (Fixed spelling error) |
||
| Line 17: | Line 17: | ||
There are several limits to what the Waypointing tool can do. First, the Waypointing tool is not designed to describe the anomalies found within projects. For example, if a single page in a book of marriages has a single entry of baptisms, there is a good chance that the waypointer will not find that anomaly. It is expected that as the records are used, patrons will note the anomaly on the Family Search Wiki. Then, when the project is indexed, the anomaly will be identified and described. | There are several limits to what the Waypointing tool can do. First, the Waypointing tool is not designed to describe the anomalies found within projects. For example, if a single page in a book of marriages has a single entry of baptisms, there is a good chance that the waypointer will not find that anomaly. It is expected that as the records are used, patrons will note the anomaly on the Family Search Wiki. Then, when the project is indexed, the anomaly will be identified and described. | ||
A second limit to the process is found in the requirement of a greater level of standardization and simplification of record types and localities. Indexed record types and localities can be linked together, allowing a search for baptisms to bring up indexed documents with record types of Baptisms, Baptisms of Infants, Baptisms of Adults, Baptisms of Slaves, and so on. Because Waypointing creates the links in a browse structure, each unique spelling of a place and each variation of describing the record type creates a different, independent group, and shows up in the final product online. Having groups of Baptisms, Baptisms of Infants, Baptisms of Adults, Baptisms of Slaves, and so on, can complicate a project, and divide it into so many groups that it loses usability. Waypointing seeks to avoid this type of complication by creating standardized spellings of a project’s localities, and a standardized list of record types. This way, any type of Baptism falls under the standardized Baptism record type. Deaths, Burials, | A second limit to the process is found in the requirement of a greater level of standardization and simplification of record types and localities. Indexed record types and localities can be linked together, allowing a search for baptisms to bring up indexed documents with record types of Baptisms, Baptisms of Infants, Baptisms of Adults, Baptisms of Slaves, and so on. Because Waypointing creates the links in a browse structure, each unique spelling of a place and each variation of describing the record type creates a different, independent group, and shows up in the final product online. Having groups of Baptisms, Baptisms of Infants, Baptisms of Adults, Baptisms of Slaves, and so on, can complicate a project, and divide it into so many groups that it loses usability. Waypointing seeks to avoid this type of complication by creating standardized spellings of a project’s localities, and a standardized list of record types. This way, any type of Baptism falls under the standardized Baptism record type. Deaths, Burials, Interments, and so on, become Burials. This applies to other record types and also to localities. | ||
Perhaps the biggest current limit to the process is our inability to correct errors found after publication. The time and resources required to remove the project from the internet, return it to the Waypointing team, fix the problems, and resubmit the project are too great to justify fixing minor errors. There is currently an effort to create a web-based tool for Waypointing to use, which may enable minor published mistakes to be fixed without having to remove the whole project from Record Search. | Perhaps the biggest current limit to the process is our inability to correct errors found after publication. The time and resources required to remove the project from the internet, return it to the Waypointing team, fix the problems, and resubmit the project are too great to justify fixing minor errors. There is currently an effort to create a web-based tool for Waypointing to use, which may enable minor published mistakes to be fixed without having to remove the whole project from Record Search. | ||