add support for saving user action logs

[ftyers]

It would be cool to keep a track of how the user is interacting with annotatrix, this could provide interesting data for training models and for investigating how annotators annotate. In the simplest way
you could have an entry for e.g. AnnoTime=1512811353 (unixtime) in each token in the MISC column. Edits could be represented simply by comma separated values, AnnoTime=1512811353,1512811427.

Additional thoughts and suggestions welcome!

[jonorthwash]

Do you think this logging should be done client-side, or server-side (i.e., only when using server mode)?

[ftyers]

If there is a server it can log more stuff, if it's user side it should only log the last change unixtime in the MISC column. I don't think it's a good idea to clog the misc column, but i think having annotime could be an interesting feature, and easy to store.

[jonorthwash]

Oh! I somehow missed that you had in mind keeping that sort of metadata in the conllu. Last edited time certainly could work that way, but I'd be worried about accumulating too much stuff of that sort, depending on what else you have in mind.

[ftyers]

I think in the CoNLL-U it should be completely restricted to just AnnoTime. In the server logging we could have more detailed info.

[jonorthwash]

Agreed. What sorts of things would you have logged by the server?

[ftyers]

Well, I have been thinking about stuff that might be useful to training algorithms... for example:

• Which thing was annotated first
• If relations are changed x was changed to y
• How long it takes to annotate a sentence

I'm sure there is more stuff too.

[gstark0]

@ftyers So, at the client-side, it should add AnnoTime entry to misc column, when token was created, and then, after comma, log every change to that token? Including changing name, creating deprel, making supertoken, splitting token?

[ftyers]

@gstark0 for now I would just add support for updating the AnnoTime for the last changed time later we can decide if we want to log a timestamp every change (it could be a lot of timestamps).

[gstark0]

@ftyers Is this how it should look like -> #209 ? It's just the beginning, I would like to improve it, but I want to make sure that its a good start.