on rare occasions primary document timestamp prefix differs from that stored in field_value for that document

[smutniak]

utswmed reports it happens 'at least once each semester' but i've seen it on rare occasions elsewhere and have to either manually change the filename or field_value. not sure of the cause yet so this is a placeholder for future investigation

[cstarcher]

@jcross2562 If you have any more information about this that would help us diagnose the problem, please feel free to add it here.

[jcross2562]

I had to go back to my TDL support ticket to remind me what this was about. ;-)

The problem that had been experienced (and which occurs periodically) appears when a student's submission is changed to "Needs Correction" to allow them to upload a corrected file. When the student completes that process, something happens (and exactly what that is unclear) that prevents the file from being uploaded. The action log show an attempt to upload the file, but the file is immediately removed, and this leaves the submission with no file. However, some kind of tombstone does remain because the ALL FILES section shows a row with no file data.

The solution that I have to follow when this happens is (1) delete the "tombstone" and (2) ask the student to try uploading the file again.

The TDL support ticket was #12144 (in case that helps).