Community Typos
Robert Kelbe
Member Posts: 585 ✭✭✭
Allowing users to report typos is a strategic advantage for Logos Bible Software. Many of Logos's older works are scanned with OCR technology and contain many typos. In an ideal world, Logos would correct these errors before publishing these works. However, it is understandable why this never happens and many of us are glad to simply have access to these older works within the Logos ecosystem. The existing "Report Typos" feature is a good idea, because it allows readers to do the work of editing to make the product better for everyone.
However, there are 3 major problems with the existing "Report Typos" feature.
1st, I am not convinced that Logos actually implements the changes, especially with the older works where there are more typos due to the OCR scanning.
2nd, Logos needs to confirm every typo in the printed work, which is time consuming. If the typo is original, they can't change it, and users may think that typos are not being corrected when they are actually original. Or, work will need to be duplicated by the user or the content editors at Logos every time a typo is reported. Logos should have some system for keeping track of typos. My proposal is to make this public-facing using a mechanism akin to "Community Notes".
3rd, since report typos is not available on Mobile where I do most of my reading, I have a backlog of about 200 typos which I tag as a note, but haven't taken the time to report.
My proposal is to bring "Community Notes" to the "Report Typos" feature. Essentially, typos submitted by users would show up as community notes, which could be toggled on and off through a visual filter. Logos could then respond with an official Community Typo note, saying "This has been checked, and it is an original typo". That way users could see whether a typo has been reported, and not spend unneccessary time reporting it. Also, even if the typo happens to be original, they could see what other users think the author was most likely trying to say.
It would be especially nice if this could be added to Mobile as well...
However, there are 3 major problems with the existing "Report Typos" feature.
1st, I am not convinced that Logos actually implements the changes, especially with the older works where there are more typos due to the OCR scanning.
2nd, Logos needs to confirm every typo in the printed work, which is time consuming. If the typo is original, they can't change it, and users may think that typos are not being corrected when they are actually original. Or, work will need to be duplicated by the user or the content editors at Logos every time a typo is reported. Logos should have some system for keeping track of typos. My proposal is to make this public-facing using a mechanism akin to "Community Notes".
3rd, since report typos is not available on Mobile where I do most of my reading, I have a backlog of about 200 typos which I tag as a note, but haven't taken the time to report.
My proposal is to bring "Community Notes" to the "Report Typos" feature. Essentially, typos submitted by users would show up as community notes, which could be toggled on and off through a visual filter. Logos could then respond with an official Community Typo note, saying "This has been checked, and it is an original typo". That way users could see whether a typo has been reported, and not spend unneccessary time reporting it. Also, even if the typo happens to be original, they could see what other users think the author was most likely trying to say.
It would be especially nice if this could be added to Mobile as well...
4
Comments
-
FL have a system of automatic fixes from some publishers which is why some typos would not be getting fixed, but they do need to be more proactive about our submissions.0
