Some CodingTracker sequences need to get post-processed to be parsed and replayed correctly. We store the fixed CodingTracker sequences in a Subversion repository different from our main data repository. If a user updates his or her original CodingTracker sequence, the fixed CodingTracker sequence becomes outdated, because it no longer contains the new changes. I suggest that we write a script to detect the fixed CodingTracker sequences that have become outdated.
Some CodingTracker sequences need to get post-processed to be parsed and replayed correctly. We store the fixed CodingTracker sequences in a Subversion repository different from our main data repository. If a user updates his or her original CodingTracker sequence, the fixed CodingTracker sequence becomes outdated, because it no longer contains the new changes. I suggest that we write a script to detect the fixed CodingTracker sequences that have become outdated.