Open befriedman opened 1 year ago
also tracking back vis a vis "null" designation - important to note that this is a new emergent bug- it did not occur during the original manual annotations data sets performed by me and by Hannah several years ago- but it has only appeared recently This suggests that something in the original code for annotations or marking cells has changed Can this be traced? I am not sure that suggested fix will work we can try- but note that "nulls' can occur within a single annotation session where setup for marking is unchanged- and where majority of cells are correctly recorded
The created column should have been named 'updated'. It gets updated to the current date every time an annotator works on that session. I have fixed this and added a new column named updated so each name should do as the name suggests. As for the null problem, this will get addressed when the new database modifications are implemented.
duplicate of #126
first issue is duplicate of #150