That's interesting. Does your original task not have a timestamp attached?
I just tried the review command on a text classification dataset. The original blob looks like this.
{
"text": "@Tesco 3/3 on the wrong which I really don\u2019t appreciate. This needs to be investigate and I was simply queuing to pay and the guy pushed in\ud83d\ude21",
"_input_hash": -1341474668,
"_task_hash": 1319679126,
"options": [{
"id": "product",
"text": "\ud83d\udce6 sold product"
}, {
"id": "delivery",
"text": "\ud83d\ude9a delivery"
}],
"_view_id": "choice",
"config": {
"choice_style": "single"
},
"accept": [],
"answer": "ignore",
"_timestamp": 1647886842
}
You'll notice that there's a _timestamp
key attached to the original. When I pass this through review
it looks like this:
{
"text": "Ay @Tesco what\u2019s your policy on bottles of lemonade? 6 bottle max is a bit of a joke am thirsty",
"_input_hash": -1402913396,
"_task_hash": -768177885,
"options": [{
"id": "product",
"text": "\ud83d\udce6 sold product"
}, {
"id": "delivery",
"text": "\ud83d\ude9a delivery"
}],
"_view_id": "review",
"accept": ["product"],
"config": {
"choice_style": "single"
},
"answer": "accept",
"_timestamp": 1650614258,
"_session_id": "tesco-support",
"sessions": ["tesco-support"],
"versions": [{
"text": "Ay @Tesco what\u2019s your policy on bottles of lemonade? 6 bottle max is a bit of a joke am thirsty",
"_input_hash": -1402913396,
"_task_hash": -768177885,
"options": [{
"id": "product",
"text": "\ud83d\udce6 sold product"
}, {
"id": "delivery",
"text": "\ud83d\ude9a delivery"
}],
"_view_id": "choice",
"accept": ["product"],
"config": {
"choice_style": "single"
},
"answer": "accept",
"_timestamp": 1647886847,
"_session_id": "tesco-support",
"sessions": ["tesco-support"],
"default": true
}],
"view_id": "choice"
}
As you can see, the _timestamp
key is also copied inside of the versions
list. How did the original json blob get created? Is there a reason why the _timestamp
key would be missing?