2 ms·
Right...but the implementation details matter. And not everything that is worth tracking is not necessarily a correction. In terms of corrections, for non-triv
by danso 11y ago
Right...but the implementation details matter. And not everything that is worth tracking is not necessarily a correction.
In terms of corrections, for non-trivial ones, it sometimes takes more than a day to get the true story...and this is sensible, as no one wants to correct the correction. This process is pretty manual.
In terms of changes, as described by the OP, it's not always clear what kind of changes deserve a manually-written line-item description. Fixing grammar and punctuation? Adding a new quote (usually when a new quote is added, an "Update" note is prepended to the story, but for most WordPress using organizations, this is again a manual process)? Rearranging the lede to put a more important, newly discovered fact up higher?
So instead of leaving it to humans to decide which changes are worth manually logging...just let the machine timestamp the changes and show the diffs, allowing the reader to see them in a transparent way. For changes that require no explanation (i.e. the addition of an Oxford comma), let them stand alone. For changes that require some context, such as a new quote, give the option of letting the reporter/editor describe the reason, e.g. "Mr. Smith responded to a reporter's calls at 3 p.m. today".
- Natsu 11y agoIn this case, the edits were so large, I think they would have been better served with an entirely new follow-up story rather than replacing the original like that.