theodi / collaborative-data-patterns-catalogue

Website for the catalogue of service design patterns for collaboratively maintained data projects
Other
8 stars 1 forks source link

[PATTERN] Machine Editing #9

Open ldodds opened 4 years ago

ldodds commented 4 years ago

Name

Machine Editing (or Bot Edits, or Bot Editing)

Problem

There are repeated patterns of contributions, including both updates and fixing of errors, that need to be made consistently across the dataset. But handling these manually is labour intensive.

Context

Correcting typos, flagging up or fixing invalid data, or synchronising data with other sources are examples of common maintenance tasks. These can be a burden to contributors and can often be automated given the right tools.

Solution

Allow automated changes to the dataset to be made by external applications or "bots",

Allow machines/bots for applications to push data directly into your database. Develop, publish and adhere to a ‘bot policy’ to set rules around the use of bots, and to mitigate any harmful impacts.

Discussion

Bots are tools that can make amendments to databases without requiring a human to authorise a decision. Typically, bots can create entries, add statements, labels and descriptions to existing entries.

Attributable Contributions can help people identify automated edits.

Bots might not be allowed to edit data, but could be used to Flag For Review.

While bots can be hugely beneficial in terms of speed and volume of edits, they can be disruptive and damaging if the design or operation is not fit for purpose.

If you allow bots to access your database, you should develop a ‘bot policy’ that will to ensure that developers follow best practices. The policy might involve applying Escalating Blocking to limit damage.

Related Patterns

Examples