Better handle multiple users coding same article

[mchladek]

Currently the model does not keep good track of when a user overwrites the coding done by another user. A better history of article codings by user should be kept. This will be especially important if article codings done by the NLP model are "coded" using a dummy user. We will need to have multiple users for multiple versions of the NLP and will want to keep track of how the different versions coded articles differently.

[meshulam]

Model codings will be stored separately from user codings. Are there specific use cases where we want to store more than the latest user coding for an article? Are you thinking something that looks like a changelog or actually having multiple "active" codings?

[mchladek]

There were a couple use cases we had in mind:

1. We had talked about having articles coded over multiple passes (see Have volunteers tag articles over several passes with each pass being a subset of tags #47). So, for example, one volunteer would only code for categories under "crimes" then another volunteer would code for "agencies" etc. We would want to keep track of who the various users were who coded each article.
2. Allowing users to see a history of what articles they've coded in the event they realized a day or two later they mis-coded something and need to go back and change it. If another user has altered it since then, it wouldn't be in their history. (This is likely a very rare case.)