We need a criteria for a "simple verification process"

This criteria will then be applied to possible branches for this verification process. Currently, options are: Django, Wikibase. Or, relational-vs-graph database.

Currently @mailynmailyn will be working on developing a basic verification workflow/pipeline for items from UMIL in a django approach, and I will be working on a Wikibase pipeline for the same.

We'll want to test:
1) ease of use
2) rapidity/how quickly can we do this
3) how easy is it to make a mess
3a)how easy is it to undo said mess
4) metrics?

Any ideas for other steps/things we'll want the verification process to include?

Start by comparing the proposed Django verification workflow/pipeline with the Wikibase pipeline, including the relational-versus-graph database options. Define the criteria for ease of use, speed, cleanup and undoing mistakes, and metrics; done means the project has an agreed evaluation checklist for testing both approaches.

Written by the indexing model from the issue text.